Beefy Boxes and Bandwidth Generously Provided by pair Networks
good chemistry is complicated,
and a little bit messy -LW
 
PerlMonks  

Re: Question On signals in perl

by SimonClinch (Chaplain)
on Aug 01, 2005 at 13:37 UTC ( #479892=note: print w/ replies, xml ) Need Help??


in reply to Question On signals in perl

A signal is notification to the process of a (nominally) asynchronous event. Examples are:

INT - the process has been interrupted e.g. by ctrl/c

HUP - the attached terminal session has disconnected ("been hanged up")

PIPE - a broken pipe has been detected

TERM - synchronous termination has been requested

and so on.

A simple listing of all signal names can be found by:

perl -e 'use Data::Dumper; print Dumper( \%SIG );'
The default signal handler (which generally just terminates the process as soon as it is invoked) can instead be trapped to your own code (sometimes called an AST or asynchronous system trap) by defining a routine reference as the relevant value in the %SIG hash, e.g.
$SIG{ HUP } = \&MyNoHup;
or
$SIG{ PIPE } = sub { warn ( "Broken pipe ignored; traceback follows:\n +" . Devel::trace() ); }
There are some modules which also assist signal handling, including POSIX

One world, one people


Comment on Re: Question On signals in perl
Select or Download Code

Log In?
Username:
Password:

What's my password?
Create A New User
Node Status?
node history
Node Type: note [id://479892]
help
Chatterbox?
and the web crawler heard nothing...

How do I use this? | Other CB clients
Other Users?
Others chanting in the Monastery: (13)
As of 2014-12-18 09:50 GMT
Sections?
Information?
Find Nodes?
Leftovers?
    Voting Booth?

    Is guessing a good strategy for surviving in the IT business?





    Results (48 votes), past polls