From owner-freebsd-current Mon Nov 9 21:09:03 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA10735 for freebsd-current-outgoing; Mon, 9 Nov 1998 21:09:03 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from garman.dyn.ml.org (pm106-14.dialip.mich.net [192.195.231.216]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id VAA10726 for ; Mon, 9 Nov 1998 21:09:00 -0800 (PST) (envelope-from garman@garman.dyn.ml.org) Message-Id: <199811100509.VAA10726@hub.freebsd.org> Received: (qmail 23868 invoked from smtpd); 10 Nov 1998 05:10:18 -0000 Received: from localhost.garman.net (HELO garman.dyn.ml.org) (127.0.0.1) by localhost.garman.net with SMTP; 10 Nov 1998 05:10:18 -0000 Date: Tue, 10 Nov 1998 00:10:17 -0500 (EST) From: garman@earthling.net Reply-To: garman@earthling.net Subject: Re: The infamous dying daemons bug To: crossd@cs.rpi.edu cc: archie@whistle.com, eivind@yes.no, jfieber@indiana.edu, current@FreeBSD.ORG In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/plain; CHARSET=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 9 Nov, David E. Cross wrote: >> 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? > unfortunately i can't physically ship this system anywhere, but i'm more than willing to give core team members accounts on here to help diagnose the problem. I'm also (per a previous message) currently running a staticly compiled version of inetd; we'll see if this helps any (i'm seeing the realloc: junk ptr/etc messages from inetd as well) enjoy -- Jason Garman http://garman.dyn.ml.org/ Student, University of Maryland garman@earthling.net And now... did you know that: Whois: JAG145 "If you fart consistently for 6 years and 9 months, enough gas is produced to create the energy of an atomic bomb." -- 0xdeadbeef posting To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message