Re: Global SIG handler: Is this advisable? Is there a better way?

[samtregar]

Are you sure you really want to catch and exit on every signal? That's a weird thing to do with STOP, for example.

Looking at your code I wondered what was in keys(%SIG). The answer was surprising to me - what is all this junk?

$ perl -MData::Dumper -e 'print Dumper([sort keys %SIG])'
$VAR1 = [
          'ABRT',
          'ALRM',
          'BUS',
          'CHLD',
          'CLD',
          'CONT',
          'FPE',
          'HUP',
          'ILL',
          'INT',
          'IO',
          'IOT',
          'KILL',
          'NUM32',
          'NUM33',
          'NUM35',
          'NUM36',
          'NUM37',
          'NUM38',
          'NUM39',
          'NUM40',
          'NUM41',
          'NUM42',
          'NUM43',
          'NUM44',
          'NUM45',
          'NUM46',
          'NUM47',
          'NUM48',
          'NUM49',
          'NUM50',
          'NUM51',
          'NUM52',
          'NUM53',
          'NUM54',
          'NUM55',
          'NUM56',
          'NUM57',
          'NUM58',
          'NUM59',
          'NUM60',
          'NUM61',
          'NUM62',
          'NUM63',
          'PIPE',
          'POLL',
          'PROF',
          'PWR',
          'QUIT',
          'RTMAX',
          'RTMIN',
          'SEGV',
          'STKFLT',
          'STOP',
          'SYS',
          'TERM',
          'TRAP',
          'TSTP',
          'TTIN',
          'TTOU',
          'UNUSED',
          'URG',
          'USR1',
          'USR2',
          'VTALRM',
          'WINCH',
          'XCPU',
          'XFSZ',
          '__WARN__'
        ];

Interestingly, __WARN__ is there but __DIE__ isn't. I serriously doubt you want to trap and exit on warn()!

-sam

[snafu]

Yes, perhaps I may want to block a few of those signals but really, the idea is that I wanted a global (mostly global) way of trapping sigs. I'm not too worried about which signals I'm trapping as much as I am about the method by which I'm trapping.