From owner-freebsd-current Fri Jul 4 00:38:37 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id AAA13854 for current-outgoing; Fri, 4 Jul 1997 00:38:37 -0700 (PDT) Received: from awfulhak.demon.co.uk (awfulhak.demon.co.uk [158.152.17.1]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id AAA13840 for ; Fri, 4 Jul 1997 00:38:33 -0700 (PDT) Received: from awfulhak.demon.co.uk (localhost [127.0.0.1]) by awfulhak.demon.co.uk (8.8.6/8.8.5) with ESMTP id IAA01082; Fri, 4 Jul 1997 08:30:23 +0100 (BST) Message-Id: <199707040730.IAA01082@awfulhak.demon.co.uk> X-Mailer: exmh version 1.6.9 8/22/96 To: Terry Lambert cc: tom@uniserve.com (Tom), chuckr@glue.umd.edu, ache@nagual.pp.ru, current@FreeBSD.ORG, brian@awfulhak.org, joerg_wunsch@uriah.heep.sax.de Subject: Re: ppp & HUP. In-reply-to: Your message of "Thu, 03 Jul 1997 15:23:12 PDT." <199707032223.PAA09801@phaeton.artisoft.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 04 Jul 1997 08:30:23 +0100 From: Brian Somers Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > > Exactly what processes actually exit upon receiving a HUP? Not many. > > Apparently only some user processes. Daemons NEVER exit, instead they > > thrash the system. Ugh. > > All of them that don't explicitly trap HUP. > > I always though this should have been handled by revoking the tty's > allowing that to HUP to the process group. This would also mean > removing the HUP sending from init. Don't confuse the HUP that's sent to everything that's "on" in /etc/ttys and the HUP that's sent in death() (before TERM & KILL) when the system's coming down. > > Terry Lambert > terry@lambert.org > --- > Any opinions in this posting are my own and not those of my present > or previous employers. -- Brian , Don't _EVER_ lose your sense of humour....