From owner-freebsd-current  Sun Oct  8 22:04:37 1995
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.6.12/8.6.6) id WAA23872
          for current-outgoing; Sun, 8 Oct 1995 22:04:37 -0700
Received: from asstdc.scgt.oz.au (root@asstdc.scgt.oz.au [202.14.234.65])
          by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id WAA23867
          for <current@freebsd.org>; Sun, 8 Oct 1995 22:04:34 -0700
Received: (from imb@localhost)
	by asstdc.scgt.oz.au (8.6.12/BSD-4.4)
	id PAA19554; Mon, 9 Oct 1995 15:03:54 +1000
From: michael butler <imb@scgt.oz.au>
Message-Id: <199510090503.PAA19554@asstdc.scgt.oz.au>
Subject: Re: inetd cores on SIGHUP
To: adrian@virginia.edu
Date: Mon, 9 Oct 1995 15:03:53 +1000 (EST)
Cc: roberto@keltia.freenix.fr, current@freebsd.org
In-Reply-To: <Pine.SUN.3.90.951009005147.25076M-100000@stretch.cs.Virginia.edu> from "Adrian T. Filipi-Martin" at Oct 9, 95 00:58:08 am
X-Mailer: ELM [version 2.4 PL24beta]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Content-Length: 750       
Sender: owner-current@freebsd.org
Precedence: bulk

Adrian T. Filipi-Martin writes:

> On Sun, 8 Oct 1995, Ollivier Robert wrote:
 
> > It seems that michael butler said:
> > > With -current as of today .. "kill -HUP .." will cause inetd to drop a core
> > > file into the root directory .. the parent ceases to run :-(
 
> > Doesn't here :
 
> 	Well, I have been experiencing a similar problem.  In fact, I 
> suspect it is the same problem.  My init dumps core after writting a log 
> message like the following:
> 
> Oct  3 21:58:16 lorax /kernel: pid 1392: inetd: uid 0: exited on signal 6
 
That's one of the effects .. on a machine so afflicted it'll also dump core
when given a "kill -HUP". I'm in the middle of a make world with yesterday's
sources to see if matters have improved ..

	michael