From owner-freebsd-current Fri Nov 6 10:36:16 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA10074 for freebsd-current-outgoing; Fri, 6 Nov 1998 10:36:16 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from cs.rpi.edu (mumble.cs.rpi.edu [128.213.8.16]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA09989 for ; Fri, 6 Nov 1998 10:36:05 -0800 (PST) (envelope-from crossd@cs.rpi.edu) Received: from o2.cs.rpi.edu (root@o2.cs.rpi.edu [128.113.96.156]) by cs.rpi.edu (8.9.1/8.9.1) with ESMTP id NAA09515; Fri, 6 Nov 1998 13:35:51 -0500 (EST) Received: from localhost (crossd@localhost) by o2.cs.rpi.edu (8.9.1a/8.9.1) with ESMTP id NAA00811; Fri, 6 Nov 1998 13:33:42 -0500 (EST) X-Authentication-Warning: o2.cs.rpi.edu: crossd owned process doing -bs Date: Fri, 6 Nov 1998 13:33:41 -0500 From: "David E. Cross" To: Eivind Eklund cc: John Fieber , current@FreeBSD.ORG Subject: Re: The infamous dying daemons bug In-Reply-To: <19981106183112.27770@follo.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG 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. On Fri, 6 Nov 1998, Eivind Eklund wrote: > 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... -- David Cross To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message