From owner-freebsd-current  Wed Jul  2 19:09:25 1997
Return-Path: <owner-current>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.5/8.8.5) id TAA08832
          for current-outgoing; Wed, 2 Jul 1997 19:09:25 -0700 (PDT)
Received: from nagual.pp.ru (ache.relcom.ru [194.58.229.133])
          by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id TAA08815
          for <current@freebsd.org>; Wed, 2 Jul 1997 19:09:15 -0700 (PDT)
Received: (from ache@localhost)
	by nagual.pp.ru (8.8.6/8.8.5) id GAA00291;
	Thu, 3 Jul 1997 06:08:58 +0400 (MSD)
Date: Thu, 3 Jul 1997 06:08:54 +0400 (MSD)
From: =?KOI8-R?B?4c7E0sXKIP7F0s7P1w==?= <ache@nagual.pp.ru>
To: FreeBSD-current <current@freebsd.org>, Brian Somers <brian@awfulhak.org>
cc: Chuck Robey <chuckr@glue.umd.edu>,
        Joerg Wunsch <joerg_wunsch@uriah.heep.sax.de>
Subject: Re: ppp & HUP. 
In-Reply-To: <199707022132.WAA07880@awfulhak.demon.co.uk>
Message-ID: <Pine.BSF.3.96.970703060227.268B-100000@nagual.pp.ru>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-current@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

On Wed, 2 Jul 1997, Brian Somers wrote:

> > > reboot(8) will send SIGTERMs to the processes, but not SIGHUPs.
> 
> death() in init.c :(

I start thinking that sending HUP from init is a bug because:
1) It increase disk activity just before shutdown since all daemons
re-read their configs.
2) It cause redials for redial-able software as uucp (and ppp some time
ago).

If nobody will explain why this HUP is neded (hanging shells perfectly
killed by SIGKILL), I'll remove HUP sending from init.

-- 
Andrey A. Chernov
<ache@null.net>
http://www.nagual.pp.ru/~ache/