You can of course catch the signal and do nothing, or (as here)
just set a variable for you to look at later.
$SIG{HUP} = \&catch;
my $caught = 0;
my $count = 0;
print "I am $$, HUP me\n";
for (0..10)
{
sleep (5); # pretending to do stuff
print "$_\n";
}
die "I was HUPed $caught times" if $caught;
### Subroutines below
sub catch
{
$caught++;
}
You should of course think carefully about ignoring signals,
expecially INT and TERM, since if you get these, someone/something
is trying to tell you something.
But, delaying handling e.g. HUP or USR1 until it is a better
time to handle is OK.
Make sure you document the signal handling well, specially
if it is not expected behaviour. E.g. HUP is often used to mean
"Please reread your config file".
--
Brovnik
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: |
| & | | & |
| < | | < |
| > | | > |
| [ | | [ |
| ] | | ] |
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.