Both of these examples are fine for stuff that doesn't do any
calls to system or exec.
But that's probably exactly what he wanted to do.
The quick answer is: Read perlipc and go on from there.
Long answer: working on that ;-)
Update:
Here's the long answer:
#!/usr/bin/env perl
use strict;
use warnings;
use POSIX qw/:sys_wait_h/;
my $child_pid = undef;
my $status = fork;
die "failed to fork\n" unless defined $status;
if ($status > 0) {
# this is the parent process.
local $SIG{ALRM} = sub { print STDERR "operation timed out for PID $
+status\n"; kill 9, $status };
alarm 10;
my $pid = 0;
do {
$pid = POSIX::waitpid ($status, POSIX::WNOHANG);
} until ($pid > 0);
alarm 0;
} else {
# this is the child process.
system "ssh a_server_could_hang";
}
For any non-portability hit your OS vendor :-(
Kay
In reply to Re: Re: Time out
by janx
in thread Time out
by Ras
-
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.
|