From owner-freebsd-current Mon Nov 9 09:03:13 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA24466 for freebsd-current-outgoing; Mon, 9 Nov 1998 09:03:13 -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 JAA24459 for ; Mon, 9 Nov 1998 09:03:10 -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 LAA07431; Mon, 9 Nov 1998 11:57:11 -0500 (EST) Date: Mon, 9 Nov 1998 11:57:11 -0500 (EST) From: John Fieber To: Archie Cobbs cc: Eivind Eklund , crossd@cs.rpi.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 On Mon, 9 Nov 1998, Archie Cobbs wrote: > 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? Hm... dynamically linked binaries mmap() the libraries, correct? And a statically linked binary wouldn't use memory mapping unless it explicitly does so itself? So, would the replacement of a dynamically linked inetd that dies with a static inetd be a valid test here? -john To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message