I recommend using a piping form of open, and capturing the returned PID. Then, in your signal handler, you can kill the PID, to ensure it goes away. Example:

my $pid; eval { local $SIG{ALRM} = sub { die "TIMEOUT" }; alarm 2; $pid = open my $fh, "sleep 30|"; alarm 0; } if ($@ eq "TIMEOUT") { print "kill $pid\n"; kill 1, $pid; } elsif ($@) { die $@; }

Take note that your example code had an error -- the key in %SIG should be ALRM and not ALARM.

Update: apparently Joost posted essentially the same answer, but 10 minutes earlier than I did. Oh well, I guess that can be seen as validation of some sort.

Update: fixed silly syntax error


In reply to Re: Timeout on system command by revdiablo
in thread Timeout on system command by MorgothSauron

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.