And there another question... If you right about restarting alarm, then proposed second alarm(0) don't fix race condition but make it much more tiny... but size, as mentioned in TPC, doesn't matter when we speak about race conditions. :) 
eval {
  local $SIG{ALRM} = sub {die "alarm here"};
  alarm(5);
  eval {
    long_code();
  };
  # HERE COME FIRST SIGALRM
  alarm(0);
  die if $@; # propagate error
}
# HERE COME SECOND SIGALRM
alarm(0);
die if $@ && $@ !~ /alarm here/;

[download]
On server under high load and alarm(1) instead of alarm(5) there is nothing unusual in my scenario. And second SIGALRM will trigger default handler resulting in killing current process.

In reply to Re^2: second alarm(0) by powerman
in thread second alarm(0) by powerman

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.