Date: Sun, 31 Mar 1996 13:19:38 -0700 (MST) From: Terry Lambert <terry@lambert.org> To: joerg_wunsch@uriah.heep.sax.de Cc: freebsd-hackers@freebsd.org Subject: Re: Help, processes not getting killed when users exit Message-ID: <199603312019.NAA11733@phaeton.artisoft.com> In-Reply-To: <199603302252.XAA05027@uriah.heep.sax.de> from "J Wunsch" at Mar 30, 96 11:52:26 pm
next in thread | previous in thread | raw e-mail | index | archive | help
> > 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.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199603312019.NAA11733>