From owner-freebsd-hackers Sun Mar 31 12:23:03 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id MAA25378 for hackers-outgoing; Sun, 31 Mar 1996 12:23:03 -0800 (PST) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.211]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id MAA25373 for ; Sun, 31 Mar 1996 12:23:02 -0800 (PST) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id NAA11733; Sun, 31 Mar 1996 13:19:38 -0700 From: Terry Lambert Message-Id: <199603312019.NAA11733@phaeton.artisoft.com> Subject: Re: Help, processes not getting killed when users exit To: joerg_wunsch@uriah.heep.sax.de Date: Sun, 31 Mar 1996 13:19:38 -0700 (MST) Cc: freebsd-hackers@freebsd.org In-Reply-To: <199603302252.XAA05027@uriah.heep.sax.de> from "J Wunsch" at Mar 30, 96 11:52:26 pm X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > > What happens instead on BSD, is that the close of the master causes > > a "revoke". Processes that don't trap read returns for EOF will > > go into a tight loop; those that do, will exit, just like if BSD > > had properly delivered the SIGHUP to the child processes (like > > POSIX implies you shouldn't, and like SunOS, Solaris, HPUX, SCO, > > Linux, BSDI, Ultrix, OSF/1, SVR3, SVR4, and AIX all do...). > > Are you absolutely sure about BSDI and Illtrix? > > It would surprise me for BSDI, and i know it for certain that the old > 4.2BSD-based Illtrix did cause us much more gray hairs with this > symptom. I'm positive for Ultrix 4.2 on a MicroVAX II. BSDI, I'm just guessing because they don't have this problem flooding their lists, and the SIGHUP fix is the correct one. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers.