From owner-freebsd-current  Thu Jul  3 01:17:30 1997
Return-Path: <owner-current>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.5/8.8.5) id BAA27990
          for current-outgoing; Thu, 3 Jul 1997 01:17:30 -0700 (PDT)
Received: from critter.dk.tfs.com ([140.145.230.252])
          by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id BAA27983
          for <current@freebsd.org>; Thu, 3 Jul 1997 01:17:27 -0700 (PDT)
Received: from critter.dk.tfs.com (localhost [127.0.0.1])
	by critter.dk.tfs.com (8.8.6/8.8.5) with ESMTP id JAA03860;
	Thu, 3 Jul 1997 09:26:48 +0200 (CEST)
To: Bruce Evans <bde@zeta.org.au>
cc: ache@nagual.pp.ru, brian@awfulhak.org, current@freebsd.org,
        chuckr@Glue.umd.edu, joerg_wunsch@uriah.heep.sax.de
From: Poul-Henning Kamp <phk@dk.tfs.com>
Subject: Re: ppp & HUP. 
In-reply-to: Your message of "Thu, 03 Jul 1997 13:02:24 +1000."
             <199707030302.NAA26921@godzilla.zeta.org.au> 
Date: Thu, 03 Jul 1997 09:26:47 +0200
Message-ID: <3858.867914807@critter.dk.tfs.com>
Sender: owner-current@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

In message <199707030302.NAA26921@godzilla.zeta.org.au>, Bruce Evans writes:
>>If nobody will explain why this HUP is neded (hanging shells perfectly
>>killed by SIGKILL), I'll remove HUP sending from init.
>
>SIGHUP may have been to allow shells to propagate SIGHUP to children.
>There may still be some problems here for parts of the process tree
>not killed by the death of the controlling process.  Perhaps shells
>do a more complete job of propagating the SIGHUP?

SIGHUP to processes with a controling tty, SIGTERM to the rest ?

--
Poul-Henning Kamp           | phk@FreeBSD.ORG       FreeBSD Core-team.
http://www.freebsd.org/~phk | phk@login.dknet.dk    Private mailbox.
whois: [PHK]                | phk@tfs.com           TRW Financial Systems, Inc.
Power and ignorance is a disgusting cocktail.