Re: Possible bug in wait4(), 2.1.126-129 ?
Brandon S. Allbery KF8NH (allbery@kf8nh.apk.net)
Tue, 24 Nov 1998 19:39:42 -0500
In message <E0zi4LB-0004GG-00@taurus.cus.cam.ac.uk>, Peter Benie writes:
+-----
| #ifdef USE_SIGCHLD
| /* our parent is watching for our death by catching SIGCHLD. we
| * do not care to watch for our children's deaths this way -- we
| * use wait() explictly. so we have to disable the signal (which
| * was inherited from the parent).
| */
| (void) signal(SIGCHLD, SIG_IGN);
| #else
| /* on system-V systems, we are ignoring SIGCLD. we have to stop
| * ignoring it now or the wait() in cron_pclose() won't work.
| * because of this, we have to wait() for our children here, as well.
| */
| (void) signal(SIGCLD, SIG_DFL);
| #endif /*BSD*/
+--->8
So once again someone incorrectly assumed that Linux is BSD when it is in
fact System V (well, POSIX, but that amounts to the same thing). Sigh.
(And I'm slipping; I *should* have recognized the error return, I've seen it
often enough from buggy ports.)
--
brandon s. allbery [os/2][linux][solaris][japh] allbery@kf8nh.apk.net
system administrator [WAY too many hats] allbery@ece.cmu.edu
carnegie mellon / electrical and computer engineering KF8NH
Kiss my bits, Billy-boy.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/