The signal handler is that sub{} that you stored in $SIG{ALRM}.
To kill the other script, you'd have to get its pid. Unfortunately I don't know any way to this without any ugly hacks. Maybe someone else does.
So for instance, you can use this temporary file handle hack:
#!/usr/bin/perl
use strict;
use warnings;
use CGI;
use File::Temp;
my $q = new CGI;
print $q->header;
my $tmp = File::Temp->new(UNLINK => 0);
my $tmpnam = $tmp->filename;
eval {
local %SIG;
$SIG{ALRM}=
sub{
$tmp->close;
system("fuser", "-sk", "-TERM", $tmpnam);
unlink $tmpnam;
die "timeout reached, after 20 seconds!\n";
};
alarm 3;
#sleep (60);
system("sleep 10 3>$tmpnam");
alarm 0;
};
alarm 0;
if($@) { print "Error: $@\n"; }
exit(0);
This requires the "fuser" command, which is shipped with most Linux distros.
If this does not make the other script die, then leave out the "-TERM".
I replaced the name of your shell script with "sleep 10", otherwise I can't test it. I also replaced 20 with 3 because I did not want to wait 20 seconds.
-
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.
|