Read from a pipe or die in perl Post: 302416611

10 More Discussions You Might Find Interesting

1. Shell Programming and Scripting

read after pipe problem OSX10.4

I use read often in scripts to filter the right part into a variable like: $ print "abc cde efg" | read k l ; print "k=$k, l=$l" k=, l= This works on linux and unix versions I work with. On OSX 10.4 this doesn't work. I found a workaround but would like to know why the original line...

2. Programming

Problem in read() from a pipe

Hi, Can any one please help me with this. Am struggling hard to get a solution. I am doing telnet through a C program and getting the stdout file descriptor of the remote machine to pipe. read() function is getting data, But whenl it receives SOH character ie. ^A ( Start of heading = Console...

3. Programming

pipe read and write with many forked children

I know how to read and write if i have a forked process with only one child. However what is involved with reading and writing with many forked processes. Say one parent that forks 5 children, and needs to communicate with all 5 in half duplex. int temp, counter=0; do{ pipe(temp); ...

4. Shell Programming and Scripting

perl problem - why isn't 'die' being called?

last week i started learning perl, so have limited skill and knowledge. why isn't 'die' being called and the script exiting before the 'directory created' line? if (! -d "$logdir") { system "mkdir -p $logdir" || die print "\nERROR: release log directory creation failed - $logdir: $!\n";...

5. Shell Programming and Scripting

perl problem - another 'die' issue.

two things. why doesn't the 'die' message get displayed - "Error: release log directory creation failed..."? why does the script name and line number get displayed despite the inclusion of a '\n'. apparently adding a newline prevents this from happening. if (! -d "$logdir") { use...

6. Shell Programming and Scripting

[SOLVED] nawk FS using pipe read variables from file

7. Shell Programming and Scripting

Read pipe data

Hello, I need to read the pipe data as:- cat abc.txt | uuencode abc.txt | mailx -s hi xyz@xyz.com I will override the mailx function so that when mailx is called, it calls my version of maix and in that function I want to read the file which is attached in progional mailx function- abc.txt...

8. Shell Programming and Scripting

While read pipe input issue

Hello, I have an ffmpeg bash script which is working nice and I need to do the same for other sources. To create new scripts and to deal with multiple bash files sounds not logical. It is a bit hard to manage for me.. I wondered if it was possible to make my input file as variable. Then I...

9. Shell Programming and Scripting

UNIX fifo concurrent read from a named pipe

I have created a fifo named pipe in solaris, which writes the content of a file, line by line, into pipe as below: $ mkfifo namepipe $ cat books.txt "how to write unix code" "how to write oracle code" $ cat books.txt >> namepipe & I have a readpipe.sh script which reads the named...

10. UNIX for Beginners Questions & Answers

UNIX Pipe -Exit when there are no bytes to read

Hi All, I'm creating a program which reads millions of bytes from the PIPE and do some processing. As the data is more, the idea is to read the pipe parallely. Sun Solaris 8 See the code below: #!/bin/sh MAXTHREAD=30 awk '{print $1}' metadata.csv > nvpipe & while do ...

LEARN ABOUT DEBIAN

runsv

runsv(8)						      System Manager's Manual							  runsv(8)

NAME

       runsv - starts and monitors a service and optionally an appendant log service

SYNOPSIS

       runsv service

DESCRIPTION

       service must be a directory.

       runsv  switches to the directory service and starts ./run.  If ./run exits and ./finish exists, runsv starts ./finish.  If ./finish doesn't
       exist or ./finish exits, runsv restarts ./run.

       If ./run or ./finish exit immediately, runsv waits a second before starting ./finish or restarting ./run.

       Two arguments are given to ./finish.  The first one is ./run's exit code, or -1 if ./run didn't exit normally.  The second one is the least
       significant  byte  of  the exit status as determined by waitpid(2); for instance it is 0 if ./run exited normally, and the signal number if
       ./run was terminated by a signal.  If runsv cannot start ./run for some reason, the exit code is 111 and the status is 0.

       If the file service/down exists, runsv does not start ./run immediately.  The control interface (see below) can be used to start  the  ser-
       vice and to give other commands to runsv.

       If  the	directory  service/log	exists,  runsv	creates  a pipe, redirects service/run's and service/finish's standard output to the pipe,
       switches to the directory service/log and starts ./run (and ./finish) exactly as described above for the service directory.   The  standard
       input of the log service is redirected to read from the pipe.

       runsv  maintains  status  information in a binary format (compatible to the daemontools' supervise program) in service/supervise/status and
       service/log/supervise/status, and in a human-readable format in service/supervise/stat, service/log/supervise/stat,  service/supervise/pid,
       service/log/supervise/pid.

CONTROL

       The  named pipes service/supervise/control, and (optionally) service/log/supervise/control are provided to give commands to runsv.  You can
       use sv(8) to control the service or just write one of the following characters to the named pipe:

       u      Up.  If the service is not running, start it.  If the service stops, restart it.

       d      Down.  If the service is running, send it a TERM signal, and then a CONT signal.	If ./run  exits,  start  ./finish  if  it  exists.
	      After it stops, do not restart service.

       o      Once.  If the service is not running, start it.  Do not restart it if it stops.

       p      Pause.  If the service is running, send it a STOP signal.

       c      Continue.  If the service is running, send it a CONT signal.

       h      Hangup.  If the service is running, send it a HUP signal.

       a      Alarm.  If the service is running, send it a ALRM signal.

       i      Interrupt.  If the service is running, send it a INT signal.

       q      Quit.  If the service is running, send it a QUIT signal.

       1      User-defined 1.  If the service is running, send it a USR1 signal.

       2      User-defined 2.  If the service is running, send it a USR2 signal.

       t      Terminate.  If the service is running, send it a TERM signal.

       k      Kill.  If the service is running, send it a KILL signal.

       x      Exit.   If  the  service	is running, send it a TERM signal, and then a CONT signal.  Do not restart the service.  If the service is
	      down, and no log service exists, runsv exits.  If the service is down and a log service exists, runsv closes the standard  input	of
	      the log service, and waits for it to terminate.  If the log service is down, runsv exits.  This command is ignored if it is given to
	      service/log/supervise/control.

       Example: to send a TERM signal to the socklog-unix service, either do
	 # sv term /etc/service/socklog-unix
	or
	 # printf t >/etc/service/socklog-unix/supervise/control

       printf(1) usually blocks if no runsv process is running in the service directory.

CUSTOMIZE CONTROL

       For each control character c sent to the control pipe, runsv first checks if service/control/c exists and is executable.  If so, it  starts
       service/control/c  and waits for it to terminate, before interpreting the command.  If the program exits with return code 0, runsv refrains
       from sending the service the corresponding signal.  The command o is always considered as command u.  On command d first  service/control/t
       is  checked,  and then service/control/d.  On command x first service/control/t is checked, and then service/control/x.	The control of the
       optional log service cannot be customized.

SIGNALS

       If runsv receives a TERM signal, it acts as if the character x was written to the control pipe.

EXIT CODES

       runsv exits 111 on an error on startup or if another runsv is running in service.

       runsv exits 0 if it was told to exit.

SEE ALSO

       sv(8), chpst(8), svlogd(8), runit(8), runit-init(8), runsvdir(8), runsvchdir(8), utmpset(8)

       http://smarden.org/runit/

AUTHOR

       Gerrit Pape <pape@smarden.org>

																	  runsv(8)