Ah, OK. So you want to be able to kill off the offending sub-process when the alarm fires? Then you either need to walk the process table, looking for a process whose parent is your script, or start the process in a way which allows you to get the pid and the output.
e.g. run the code under a piped open, something like this (untested):
my $cmd = "your command";
my $pid = open(my $fh, "$cmd|");
$SIG{ALRM} = sub {
print "Alarm fired, killing pid $pid\n";
# Replace with windows-specific code to kill process
kill 15, $pid;
};
die "Can't run command [$cmd] : $!" unless $pid;
# Or do some other processing with $fh
push @result, $_ while (<$fh>);
close $fh
or die "Problem running [$cmd] : $?";
If your child process starts yet more children (and they don't exit when the parent is killed), you'll have to write more elaborate cleanup code.
Dig through the windows-related process modules on CPAN and you should find what you need for the cleanup.
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.