I gather from eyepopslikeamosquito's post that a pure-Perl solution that both kills the process on timeout and captures its exit status otherwise is non-trivial.

It is not trivial, but is is not so complex either:

# untested! use POSIX qw(WNOHANG _exit); use Errno qw(ECHILD); local $SIG{CHLD} = sub {}; # this do-nothing sub ends the # select below on SIGCHLD my $pid = fork; if (!$pid) { defined $pid or die "fork failed: $!"; do { exec @cmd }; # warnings friendly! _exit(1); } my $start = time; while (1) { my $rc = waitpid ($pid, WNOHANG); last if $rc == $pid; last if $rc < 0 and $! == ECHILD; select (undef, undef, undef, 1); kill INT => $pid if time > $start + $timeout; }

Using AnyEvent it would be even easier.


In reply to Re^2: Need Function for Timing out shell commands by salva
in thread Need Function for Timing out shell commands by bae11208

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":



  • 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:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.