From owner-freebsd-current Tue Dec 15 15:28:02 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA12628 for freebsd-current-outgoing; Tue, 15 Dec 1998 15:28:02 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA12604 for ; Tue, 15 Dec 1998 15:28:00 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.1/8.9.1) id PAA60898; Tue, 15 Dec 1998 15:27:52 -0800 (PST) (envelope-from dillon) Date: Tue, 15 Dec 1998 15:27:52 -0800 (PST) From: Matthew Dillon Message-Id: <199812152327.PAA60898@apollo.backplane.com> To: "John W. DeBoskey" Cc: freebsd-current@FreeBSD.ORG Subject: Re: Inetd 1.42 now blocking all signals in child by default References: <199812152245.RAA21523@bb01f39.unx.sas.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :Hi, : : Well, the good news is I haven't made inetd fail... The bad news :is that by default the SIGCHLD, SIGHUP and, SIGALRM signals are now :being blocked when the fork()/exec() calls are made. : : So... The child process does not receive these signals by default :anymore. This is major behavior modification and definitely causes :some very interesting side effects... :-) Love them Zombies! : : We still need to unblock the signals in the child process after :the fork... The following should do the trick: : :--- inetd.c.orig Mon Dec 14 02:07:34 1998 :+++ inetd.c Tue Dec 15 17:20:02 1998 :@@ -555,6 +555,7 @@ : /* sigsetmask(0L); */ : if (pid == 0) { : if (dofork) { :+ sigsetmask(0L); : if (debug) : warnx("+ closing from %d", maxsock); : for (tmpint = maxsock; tmpint > 2; tmpint--) : : Hey! As always comments, critiques, and hints are most welcome... : :Thanks! :John Yup. Commited... though I'm unblocking just before the exec call. I think it amounts to the same thing. -Matt Matthew Dillon Engineering, HiWay Technologies, Inc. & BEST Internet Communications & God knows what else. (Please include original email in any response) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message