In article <slrndd6hhq.rr.mason@g.primenet.com.au>,
Geoff Wing  <mason@primenet.com.au> wrote:
>Christos Zoulas <christos@netbsd.org> typed:
>: Modified Files:
>: 	src/bin/sh: trap.c
>: Log Message:
>: Don't hard ignore signals that were ignored by our environment, because
>: when we try to set a trap on them it will not work. Also while I am here:
>: 1. don't change the action status if the signal system call failed.
>: 2. don't try to sigignore it if signal failed.
>: 3. clear the signal mask in case our parent blocked it for us.
>
>This means that when /etc/rc finishes, any spawned processes which weren't
>explicitly nohup'd or otherwise will receive a HUP and exit.  Is that
>intended?  OK, so maybe I've just been lazy when throwing in rc.d scripts
>and stuff into rc.local

This was not really intended. On the other hand, /etc/rc is not setting
a trap handler for HUP so hup should remain blocked for everything started
from /etc/rc, except for programs that explicitly enable it. Isn't that
the case?

christos