From owner-freebsd-current  Tue Nov 10 11:52:17 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id LAA06258
          for freebsd-current-outgoing; Tue, 10 Nov 1998 11:52:17 -0800 (PST)
          (envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from marathon.tekla.fi (marathon.tekla.fi [192.98.7.5])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA06250
          for <current@FreeBSD.ORG>; Tue, 10 Nov 1998 11:52:15 -0800 (PST)
          (envelope-from sja@tekla.fi)
Received: from poveri.tekla.fi (poveri.tekla.fi [192.98.7.19])
	by marathon.tekla.fi (8.8.7/8.8.7) with SMTP id VAA16464
	for <current@FreeBSD.ORG>; Tue, 10 Nov 1998 21:51:56 +0200
From: Sakari Jalovaara <sja@tekla.fi>
Received: by poveri.tekla.fi; (5.65v3.2/1.1.8.2/20Aug96-0557PM)
	id AA10677; Tue, 10 Nov 1998 21:52:08 +0200
Date: Tue, 10 Nov 1998 21:52:08 +0200
Message-Id: <9811101952.AA10677@poveri.tekla.fi>
To: current@FreeBSD.ORG
Subject: Re: The infamous dying daemons bug
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Could someone who can reproduce the dying daemons problem try a little
experiment: kill syslogd and then induce the out-of-memory condition.
Do other daemons still start dying?
									++sja

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message