Re^3: Why this daemon can only receive the HUP signal no more than one time?

Based on Re: Can't catch signals after an exec?, change your code

$SIG{HUP} = \&doSigHup;
[download]

to:

use POSIX ();
$sigset=POSIX::SigSet->new();
$action=POSIX::SigAction->new('doSigHup',$sigset,&POSIX::SA_NODEFER);
POSIX::sigaction(&POSIX::SIGHUP, $action);
[download]

Comment on Re^3: Why this daemon can only receive the HUP signal no more than one time? Select or Download Code

Replies are listed 'Best First'.
Re^4: Why this daemon can only receive the HUP signal no more than one time? by Anonymous Monk on Apr 05, 2017 at 17:38 UTC
`$action=POSIX::SigAction->new('doSigHup',$sigset,&POSIX::SA_NODEFER);` Note that you are setting up an "unsafe" signal, as opposed to Safe Signal that original poster was using. Furthermore, the use of `SA_NODEFER` to avoid changes to sigprocmask has the unfortunate side-effect of making your handler re-interruptable from within its own signal handler. Altogether, a particularly nasty concoction that may eventually result in data corruption. I'd rather advise to just clear the blocked signal at program (re)start, after the handler is assigned of course.	[reply] [d/l] [select]

Replies are listed 'Best First'.

Re^4: Why this daemon can only receive the HUP signal no more than one time?
by Anonymous Monk on Apr 05, 2017 at 17:38 UTC

$action=POSIX::SigAction->new('doSigHup',$sigset,&POSIX::SA_NODEFER);

Safe Signal

SA_NODEFER

Altogether, a particularly nasty concoction that may eventually result in data corruption. I'd rather advise to just clear the blocked signal at program (re)start, after the handler is assigned of course.

[reply]
[d/l]
[select]