Date: Fri, 13 Jul 2001 10:48:53 -0700 From: Terry Lambert <tlambert2@mindspring.com> To: Garrett Wollman <wollman@khavrinen.lcs.mit.edu> Cc: Giorgos Keramidas <keramida@ceid.upatras.gr>, freebsd-current@FreeBSD.ORG Subject: Re: cannot print to remote printer Message-ID: <3B4F3485.DE6DC3E5@mindspring.com> 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>
next in thread | previous in thread | raw e-mail | index | archive | help
Garrett Wollman wrote: > > I might be wrong in many ways, but... > > > is it then mandatory that you `reset' SIGCHLD to SIG_DFL ? > > Possibly. In the general case (as specified by standards), what > happens to SIGCHLD if it was set to SIG_IGN before exec() is > ill-defined. Some systems will inherit the SIG_IGN setting, which > will then cause any executed program that depends on wait() working > (e.g., shells) to fail. > > The new POSIX draft, at least, sanctions the automatic reset of > SIGCHLD to SIG_DFL upon exec(). How does the "NOHUP" program continue to function in light of this reset demand? -- Terry 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?3B4F3485.DE6DC3E5>