From owner-freebsd-current  Fri Nov  6 10:55:36 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id KAA12610
          for freebsd-current-outgoing; Fri, 6 Nov 1998 10:55:36 -0800 (PST)
          (envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from fallout.campusview.indiana.edu (fallout.campusview.indiana.edu [149.159.1.1])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA12591
          for <current@FreeBSD.ORG>; Fri, 6 Nov 1998 10:55:30 -0800 (PST)
          (envelope-from jfieber@fallout.campusview.indiana.edu)
Received: from localhost (jfieber@localhost)
	by fallout.campusview.indiana.edu (8.9.1/8.9.1) with ESMTP id NAA01103;
	Fri, 6 Nov 1998 13:55:09 -0500 (EST)
Date: Fri, 6 Nov 1998 13:55:09 -0500 (EST)
From: John Fieber <jfieber@indiana.edu>
To: "David E. Cross" <crossd@cs.rpi.edu>
cc: Eivind Eklund <eivind@yes.no>, current@FreeBSD.ORG
Subject: Re: The infamous dying daemons bug
In-Reply-To: <Pine.SGI.4.05.9811061258001.810-100000@o2.cs.rpi.edu>
Message-ID: <Pine.BSF.4.05.9811061348550.482-100000@fallout.campusview.indiana.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

On Fri, 6 Nov 1998, David E. Cross wrote:

> Does this happen to everyone,   I personally have *never* seen it happen,
> and I have run quite a few systems run with full memory utilization.

If it was happening to everyone as much as it was happening to
me, I seriously doubt 3.0 would have ever reached release
status...having inetd die every 6 to 24 hours, httpd and sendmail
every couple days is pretty intolerable.

I've bumped my swap from 128 to 256 (I have 64 of real ram) and
will see how that goes...it will take a couple days to tell.

-john


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