Re: [Sshguard-users] Spurious sshguard shutdowns at boot time with "sshguard[#]: Got exit signal" logged

[Richard J. <rjt...@sa...>]

On Sun, Feb 15, 2015 at 09:29:28PM -0600, Kevin Zheng wrote:
> Doesn't the default SIGHUP handler terminate the process?

Per signal(3) man page, the SIGHUP default when SIG_DFL is requested is
process termination.  My naive understanding is that SIG_DFL has to be
specifically requested in a signal() call, however.

Not specifying SIGHUP in any signal() call might as a side effect set the
signal mask to block SIGHUP.  But my experience here is way back in time,
so I'm not sure any more.

What I see in practice is SIGHUP having no effect (presumably at boot, but
very definitely when sent manually) after I remove the signal() call
setting its handler.

Hmm, for the nonce, it might be better to explicitly set the handler to
SIG_IGN than just leave it out.  I still want to understand why the SIGHUP
is being sent, and then perhaps see about not sending it if that makes
sense.


Richard