Re: trap documentation does not match trap behavior

[Andreas Schwab]

John Gatewood Ham <zappaman@buraphalinux.org> writes:

> Description:
>       The info file says "Trapped signals are reset to their original
>         values in a child process when it is created." but this is not
>         true for me with crond and smartd for the SIGTERM signal.

Signals that are ignored are not reset.  This is consistent with the
general behaviour of signals that are set to SIG_IGN across execve.

>         #!/sbin/bash
>         # this launches a crond that will NOT get the SIGTERM
>         # from killall crond and does not shutdown
>         trap '' TERM
>         /usr/sbin/crond -l8

This will run crond with SIGTERM set to SIG_IGN.

> Fix:
>       Remove that sentence from the documentation?

It's not wrong, just incomplete.  See
<http://www.opengroup.org/onlinepubs/009695399/utilities/trap.html> for
the full details.

Andreas.

-- 
Andreas Schwab, SuSE Labs, schwab@suse.de
SuSE Linux Products GmbH, Maxfeldstraße 5, 90409 Nürnberg, Germany
PGP key fingerprint = 58CA 54C7 6D53 942B 1756  01D3 44D5 214B 8276 4ED5
"And now for something completely different."