From owner-freebsd-current Mon Nov 9 08:29:41 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA21647 for freebsd-current-outgoing; Mon, 9 Nov 1998 08:29:41 -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 IAA21642 for ; Mon, 9 Nov 1998 08:29:40 -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 LAA19702; Mon, 9 Nov 1998 11:29:19 -0500 (EST) Received: from localhost (crossd@localhost) by o2.cs.rpi.edu (8.9.1a/8.9.1) with ESMTP id LAA05887; Mon, 9 Nov 1998 11:27:11 -0500 (EST) X-Authentication-Warning: o2.cs.rpi.edu: crossd owned process doing -bs Date: Mon, 9 Nov 1998 11:27:11 -0500 From: "David E. Cross" To: Archie Cobbs cc: Eivind Eklund , jfieber@indiana.edu, current@FreeBSD.ORG Subject: Re: The infamous dying daemons bug In-Reply-To: <199811091624.IAA01667@bubba.whistle.com> 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 > Eivind Eklund writes: > > > 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. > > Has the use of memory mapping been ruled out as a possible common factor? Maybe if someone who is having this problem could donate the machine to a core member? -- David Cross To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message