From owner-freebsd-current  Fri Nov 20 06:30:40 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id GAA08843
          for freebsd-current-outgoing; Fri, 20 Nov 1998 06:30:40 -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 GAA08832
          for <current@FreeBSD.ORG>; Fri, 20 Nov 1998 06:30: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 JAA05870;
	Fri, 20 Nov 1998 09:28:35 -0500 (EST)
Date: Fri, 20 Nov 1998 09:28:35 -0500 (EST)
From: John Fieber <jfieber@indiana.edu>
To: Barrett Richardson <terbart@aye.net>
cc: garman@earthling.net, current@FreeBSD.ORG
Subject: Re: more dying daemons
In-Reply-To: <Pine.BSF.3.96.981119231225.12705A-100000@phoenix.aye.net>
Message-ID: <Pine.BSF.4.05.9811200925151.19426-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, 20 Nov 1998, Barrett Richardson wrote:

> That will give you another 256 mb of swap (may have to trim to
> availability of disk space). If your swap usage stabilizes at
> some point and your box lives, then you've nailed the problem.

High swap usage isn't (apparently) the problem being pursued
here.  Rather it appears to be a trigger factor.  A system
configured with a small amount of swap makes testing easier.
Configuring more swap makes seems to make the problem go
away...mostly...but not really.a

-john


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