Date: Sat, 14 Jul 2001 13:05:38 -0400 (EDT) From: Garrett Wollman <wollman@khavrinen.lcs.mit.edu> To: Giorgos Keramidas <keramida@ceid.upatras.gr> Cc: freebsd-current@FreeBSD.ORG Subject: Re: cannot print to remote printer Message-ID: <200107141705.f6EH5c802083@khavrinen.lcs.mit.edu> In-Reply-To: <20010714014914.A7876@hades.hell.gr> References: <lth8zikptx0.wl@hunter.munich.sgi.com> <p05101003b759266483c2@> <p05101003b759266483c2@[128.113.24.47]> <873d83pquy.wl@wilhelm.noname> <20010711214311.C2855@heechee.tobez.org> <200107120645.f6C6jtP45267@uriah.heep.sax.de> <20010712122148.B10960@heechee.tobez.org> <86k81eaqcj.fsf@hades.hell.gr> <200107122117.f6CLHsl43063@khavrinen.lcs.mit.edu> <3B4F3485.DE6DC3E5@mindspring.com> <20010714014914.A7876@hades.hell.gr>
next in thread | previous in thread | raw e-mail | index | archive | help
I wrote: >> > The new POSIX draft, at least, sanctions the automatic reset of >> > SIGCHLD to SIG_DFL upon exec(). Terry Lambert appears to have written: >> How does the "NOHUP" program continue to function in >> light of this reset demand? There is no ``demand'' involved. The behavior of the system when SIGCHLD is set to SIG_IGN has always been entirely implementation-defined. The new specification makes it clear that, in the course of this implementation-defined behavior, implementations are free to reset SIGCHLD to SIG_DFL when a new program is executed. The new specification also makes it clear that the behavior of functions such as system() and pclose() is undefined when SIGCHLD is set to SIG_IGN. (The semantics for SA_NOCLDWAIT are somewhat different.) This change was made because some implementors interpreted the base documents as requiring that SIGCHLD be inherited across exec(), which would then in turn require every program which ever makes use of wait() to explicitly reset SIGCHLD (since the nominal default could not be depended upon). Giorgos Keramidas 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. -GAWollman To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200107141705.f6EH5c802083>