Why is signal handling so ugly? Surely there's a good reason? Is there a better way to do this? For instance, why do I have to define a SigSet object that I never do anything with? 
my $sigset = POSIX::SigSet->new();
my $restart_action = POSIX::SigAction->new('restart',$sigset,POSIX::SA
+_NODEFER());
my $end_action = POSIX::SigAction->new('end',$sigset,POSIX::SA_NODEFER
+());
POSIX::sigaction(POSIX::SIGQUIT(), $end_action);
POSIX::sigaction(POSIX::SIGHUP(), $restart_action);
POSIX::sigaction(POSIX::SIGPIPE(), $restart_action);
POSIX::sigaction(POSIX::SIGTERM(), $end_action);
POSIX::sigaction(POSIX::SIGINT(), $restart_action);
POSIX::sigaction(POSIX::SIGUSR1(), $end_action);

[download]

In reply to Setting signal handlers by andyford

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.