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.
-
Are you posting in the right place? Check out Where do I post X? to know for sure.
-
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big>
<blockquote> <br /> <dd>
<dl> <dt> <em> <font>
<h1> <h2> <h3> <h4>
<h5> <h6> <hr /> <i>
<li> <nbsp> <ol> <p>
<small> <strike> <strong>
<sub> <sup> <table>
<td> <th> <tr> <tt>
<u> <ul>
-
Snippets of code should be wrapped in
<code> tags not
<pre> tags. In fact, <pre>
tags should generally be avoided. If they must
be used, extreme care should be
taken to ensure that their contents do not
have long lines (<70 chars), in order to prevent
horizontal scrolling (and possible janitor
intervention).
-
Want more info? How to link
or How to display code and escape characters
are good places to start.
|