Garrett Wollman wrote:
> > I'm not sure about POSIX, but the manpage of nohup does not mention
> > SIGCHLD. The only signals I see mentioned in revision 1.8 of nohup.1
> > are SIGHUP and SIGQUIT.
>
> That is correct. SIGCHLD is entirely irrelevant to `nohup', as the
> slightest amount of effort on Terry's part would have made clear.
This is the answer I was asking for: is SIGCHLD "special",
and thus treated differently, or is this applicable to all
signals?
I would be alarmed, if we were to treat different signals
differently, which it seems you are advising.
The reason I mentioned "nohup" is that the behaviour you are
specifying, if applied to SIGHUP as well as SIGCHLD, would
break "nohup".
So if "nohup" is intended to continue to function as it has
historically, then this change appears pretty arbitrary; at
the very least, it complicates the signals API domain specific
knowledge required to use the thing, which is annoying, to say
the least.
-- Terry
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
