I think your problem is (apart from Freudian slips) is that ^C kills the currently running process, subsequently the children are free to go since they are different proccesses. The same thing will happen when anything else kills the parent process too. So you'll want to keep track of your children and then kill them in the signal handler, like so
use strict;
my @children = ();
$SIG{INT} = sub {
kill 15, @children if @children > 0;
print STDERR "children sent TERM signal\n";
exit 1;
};
if(my $pid = fork()) {
push @children, $pid;
print "forked off child $pid\n";
} else {
print "in child process\n";
}
You'll probably want to put some
sleep()s in there to watch it at work, but I'm sure you get the gist of it.
HTH
broquaint
Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
Read Where should I post X? if you're not absolutely sure you're posting in the right place.
Please read these before you post! —
Posts may use any of the Perl Monks Approved HTML tags:
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
| |
For: |
|
Use: |
| & | | & |
| < | | < |
| > | | > |
| [ | | [ |
| ] | | ] |
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.