From owner-freebsd-current Fri Nov 6 11:02:59 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA13966 for freebsd-current-outgoing; Fri, 6 Nov 1998 11:02:59 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from porkfriedrice.ny.genx.net (porkfriedrice.ny.genx.net [206.64.4.30]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA13956 for ; Fri, 6 Nov 1998 11:02:57 -0800 (PST) (envelope-from bright@hotjobs.com) Received: from localhost (bright@localhost) by porkfriedrice.ny.genx.net (8.9.1/8.9.1) with ESMTP id OAA13520; Fri, 6 Nov 1998 14:05:12 -0500 (EST) (envelope-from bright@hotjobs.com) X-Authentication-Warning: porkfriedrice.ny.genx.net: bright owned process doing -bs Date: Fri, 6 Nov 1998 14:05:12 -0500 (EST) From: Alfred Perlstein X-Sender: bright@porkfriedrice.ny.genx.net To: "David E. Cross" cc: current@FreeBSD.ORG Subject: Re: The infamous dying daemons bug In-Reply-To: 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 "Not I." said the 3.0-current user. -Alfred 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. > > 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. > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message