From owner-freebsd-current  Fri Nov  6 09:31:51 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id JAA01066
          for freebsd-current-outgoing; Fri, 6 Nov 1998 09:31:51 -0800 (PST)
          (envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from ns1.yes.no (ns1.yes.no [195.204.136.10])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA01060
          for <current@FreeBSD.ORG>; Fri, 6 Nov 1998 09:31:47 -0800 (PST)
          (envelope-from eivind@bitbox.follo.net)
Received: from bitbox.follo.net (bitbox.follo.net [195.204.143.218])
	by ns1.yes.no (8.9.1a/8.9.1) with ESMTP id SAA05469;
	Fri, 6 Nov 1998 18:31:12 +0100 (CET)
Received: (from eivind@localhost)
	by bitbox.follo.net (8.8.8/8.8.6) id SAA04858;
	Fri, 6 Nov 1998 18:31:12 +0100 (MET)
Message-ID: <19981106183112.27770@follo.net>
Date: Fri, 6 Nov 1998 18:31:12 +0100
From: Eivind Eklund <eivind@yes.no>
To: John Fieber <jfieber@indiana.edu>, current@FreeBSD.ORG
Subject: Re: The infamous dying daemons bug
References: <Pine.BSF.4.05.9811061149210.429-100000@fallout.campusview.indiana.edu>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.89.1i
In-Reply-To: <Pine.BSF.4.05.9811061149210.429-100000@fallout.campusview.indiana.edu>; from John Fieber on Fri, Nov 06, 1998 at 12:12:14PM -0500
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

On Fri, Nov 06, 1998 at 12:12:14PM -0500, John Fieber wrote:
> I've now figured out that it must be the infamous dying daemons
> bug that is biting me, and pretty bad.  Inetd won't run more than
> a day without falling over.  Sendmail and apache last longer, but
> not a lot.
> 
> So, to date, what is known about the bug?

It strike when you run out of memory, usually.

> Are there people running 3.0/Current that have not encountered
> this bug?
> 
> Are there any known factors in a system configuration that
> aggrivate the problem?  More to the point, is there anything
> known to suppress the problem to any degree?  Some say it was
> present in 2.2.x, but I never encountered it.

Run with insane amounts of swap.  2GB ought to do the trick.  I'm not
guaranteeing this will stop the problem, but it will make it _much_
less frequent.

Eivind, who increased from 128MB to 256MB swap, and had the problem
almost go away...

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