From owner-freebsd-current Fri Nov 6 11:02:29 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA13904 for freebsd-current-outgoing; Fri, 6 Nov 1998 11:02:29 -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 LAA13503 for ; Fri, 6 Nov 1998 11:00:54 -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 UAA06343; Fri, 6 Nov 1998 20:00:29 +0100 (CET) Received: (from eivind@localhost) by bitbox.follo.net (8.8.8/8.8.6) id UAA05256; Fri, 6 Nov 1998 20:00:28 +0100 (MET) Message-ID: <19981106200028.23174@follo.net> Date: Fri, 6 Nov 1998 20:00:28 +0100 From: Eivind Eklund To: "David E. Cross" Cc: John Fieber , current@FreeBSD.ORG Subject: Re: The infamous dying daemons bug References: <19981106183112.27770@follo.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89.1i In-Reply-To: ; from David E. Cross on Fri, Nov 06, 1998 at 01:33:41PM -0500 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, Nov 06, 1998 at 01:33:41PM -0500, 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. No. Unfortunately, we've not found any (or I at least don't know of any) common factors between all the machines that have this problem. David committed some patches a while back that he said _might_ help it - I've not yet upgraded to test this. Eivind. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message