Subject: Re: CVS commit: src/bin/sh (trap.c:1.32)
To: None <current-users@NetBSD.org>
From: David Young <firstname.lastname@example.org>
Date: 07/14/2005 22:48:03
On Thu, Jul 14, 2005 at 11:24:45PM -0400, Christos Zoulas wrote:
> On Jul 14, 6:42pm, email@example.com (David Young) wrote:
> -- Subject: Re: CVS commit: src/bin/sh (trap.c:1.32)
> | Geoff,
> | This explains why one of my daemons goes away directly after /etc/rc
> | finishes, thanks. (It didn't used to do that!)
> | Christos, maybe that should be "Don't hard ignore signals that were
> | ignored by our environment ..." after a trap is set?
> Can you please explain more what you would like the behavior to be?
> I.e. If a shell script does not trap anything, then it should inherit
> the parents behavior, but if it sets a trap, then what should it do?
If it sets a trap, then it should not block the signal for which it set
a trap. It should continue to block every other signal, if that is the
behavior inherited from the parent.
If it resets a trap, then perhaps it should revert to the behavior
inherited from the parent for that signal.
David Young OJC Technologies
firstname.lastname@example.org Urbana, IL * (217) 278-3933