Yes, indeed!
The daemon will blocked the SIGHUP signal when it execute the SIGHUP handler. And after it relaunch itself in the handler, the SIGHUP remains being blocked, so the SIGHUP sent later is pending.
Put the following code at the head of the scrpit:
my $emptySigSet = POSIX::SigSet->new(); my $oldSigSet = POSIX::SigSet->new(); POSIX::sigprocmask( &POSIX::SIG_BLOCK, $emptySigSet, $oldSigSet ); if ( $oldSigSet->ismember( &POSIX::SIGHUP ) ){ print "SIGHUP is blocking.\n"; }else { print "SIGHUP is not blocking.\n"; }
And replace the old hupMain with the following new one:
sub hupMain { while (1) { print "Running hup main function.\n"; sleep 3; my $pendingSigSet = POSIX::SigSet->new(); POSIX::sigpending( $pendingSigSet ) ; if ( $pendingSigSet->ismember( &POSIX::SIGHUP ) ){ print "Pending signal set contains SIG_HUP\n"; } } }
I can observe the SIGHUP signal is being blocking and pending.
In reply to Re^2: Why this daemon can only receive the HUP signal no more than one time?
by sunshine_august
in thread Why this daemon can only receive the HUP signal no more than one time?
by sunshine_august
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |