From owner-freebsd-current  Tue Mar 25 14:04:05 1997
Return-Path: <owner-current>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id OAA13587
          for current-outgoing; Tue, 25 Mar 1997 14:04:05 -0800 (PST)
Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id OAA13569
          for <freebsd-current@FreeBSD.org>; Tue, 25 Mar 1997 14:04:00 -0800 (PST)
Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.5/8.6.9) id JAA12965; Wed, 26 Mar 1997 09:02:50 +1100
Date: Wed, 26 Mar 1997 09:02:50 +1100
From: Bruce Evans <bde@zeta.org.au>
Message-Id: <199703252202.JAA12965@godzilla.zeta.org.au>
To: bde@zeta.org.au, rb@gid.co.uk
Subject: Re: 2.2R (src 2.2 211): <ctrl><alt><del> == dialing
Cc: freebsd-current@FreeBSD.org, joerg_wunsch@uriah.heep.sax.de,
        terry@lambert.org
Sender: owner-current@FreeBSD.org
X-Loop: FreeBSD.org
Precedence: bulk

>>This differs from when the system is shut down using reboot(8).  reboot
>>shuts things down by broadcasting signals of increasing severity
>>{ SIGTERM, SIGKILL }.  I don't know why init broadcasts SIGHUP...
>
>That I can tell you: interactive shells don't respond to SIGTERM. OTOH,
>init shouldn't send SIGHUP to daemons (ie sessions with no controlling tty)
>because they mostly take HUP to mean "reread your config".

Init can't know enough about program (mis)behaviour to do this.  The slattach
daemon has a controlling tty, but shouldn't be sent a SIGHUP, since that
tells it to redial.

I think ignoring SIGTERM is braindamaged.

Bruce