$pid = open $pipe, "/some/program |";
while (<$pipe>) {
    ... # /some/program's output in $_
}
close $pipe;         # program gets a sigpipe
if (kill 0, $pid) {  # still there?
   kill 15, $pid;
}
[download]

_($_=" "x(1<<5)."?\n".q·/)Oo.  G°\        /
                              /\_¯/(q    /
----------------------------  \__(m.====·.(_("always off the crowd"))."·
");sub _{s./.($e="'Itrs `mnsgdq Gdbj O`qkdq")=~y/"-y/#-z/;$e.e && print}

Oha

To capture it's output, have crontab or whatever starts it redirect to some standard directory with a filename containing the date and time the process started.

As far as stopping it is concerned, don't send a CTRL-C, use a kill -9 <id> where <id> is the process-number of the program.

Signal KILL (9) is last resort and should be used as such. A process killed that way has no chance to clean up resources (e.g. flush buffers, close filehandles).

Signals 1, 2, 3 or 15 should be used, an 9 only when the process is still running after those.

You are correct. But when I saw a program (...) that does not exit itself, I made the unwarranted assumption that the original writer of the program didn't seem particularly interested in cleaning up.

In my scenario, I had a perl script starting up and managing a unix process on a Sun workstation. Anytime I hit ctl-z at my shell prompt (the shell that started the perl script), both the perl script and the background unix process stopped. This is not what I wanted at all.

After much gnashing of teeth and tearing out hair (I should have asked here), I finally figured out that the SIGSTOP was being sent to everyone in my process group. To solve the problem, I needed to create the unix process in its own process group. This is how I learned about the wonders of the perl "setpgrp" command, and process groups in general.

So here is my code:

# Fork a unix process...
my $pid;
if($pid = fork) {
    print STDERR "parent pid=$$ child pid=$pid\n";
}elsif (defined $pid) {
    print STDERR "child pid=$$ pid=$pid\n";
    # Must do setpgrp as child for nohup and job control stuff...
    setpgrp(0, $$);
    exec $unixcmd || die "Bad exec $!";
}
kill 'INT', $pid;
[download]

-Craig

UPDATE:

oha opened my mind, by letting me know that the setpgrp could be done from either the parent or the child process. oha++ Thanks!