From owner-freebsd-current Sat Nov 7 05:41:38 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA04133 for freebsd-current-outgoing; Sat, 7 Nov 1998 05:41:38 -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 FAA04128 for ; Sat, 7 Nov 1998 05:41:36 -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 IAA19833; Sat, 7 Nov 1998 08:44:13 -0500 (EST) (envelope-from bright@hotjobs.com) X-Authentication-Warning: porkfriedrice.ny.genx.net: bright owned process doing -bs Date: Sat, 7 Nov 1998 08:44:13 -0500 (EST) From: Alfred Perlstein X-Sender: bright@porkfriedrice.ny.genx.net To: Brian Feldman cc: John Fieber , 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 Simple idea, ask everyone with this bug to please show every piece of hardware in thier box (dmesg) after boot -v. If it is a hardware device or a driver misbehaving it shouldn't be that hard to find a commonality considering how much PC hardware varies. Alfred Perlstein - Programmer, HotJobs Inc. - www.hotjobs.com -- There are operating systems, and then there's FreeBSD. -- http://www.freebsd.org/ 3.0-current On Fri, 6 Nov 1998, Brian Feldman wrote: > I haven't had this bug. And a 3.0 box at school doesn't have it either... > it's not as common as you think. > > Brian Feldman > > On Fri, 6 Nov 1998, John Fieber wrote: > > > I've now figured out that it must be the infamous dying daemons > > bug that is biting me, and pretty bad. Inetd won't run more than > > a day without falling over. Sendmail and apache last longer, but > > not a lot. > > > > So, to date, what is known about the bug? > > > > 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. > > > > Here are some relevant email postings on the topic: > > > > http://www.freebsd.org/cgi/getmsg.cgi?fetch=2099086+2101942+/usr/local/www/db/text/1998/freebsd-current/19980920.freebsd-current > > http://www.freebsd.org/cgi/getmsg.cgi?fetch=649095+653248+/usr/local/www/db/text/1998/freebsd-current/19980823.freebsd-current > > http://www.freebsd.org/cgi/getmsg.cgi?fetch=786702+0+/usr/local/www/db/text/1998/freebsd-current/19980823.freebsd-current > > http://www.freebsd.org/cgi/getmsg.cgi?fetch=579190+582585+/usr/local/www/db/text/1998/freebsd-current/19980823.freebsd-current > > http://www.freebsd.org/cgi/getmsg.cgi?fetch=543833+547747+/usr/local/www/db/text/1998/freebsd-current/19980705.freebsd-current > > > > And some relevant PRs: > > > > http://www.freebsd.org/cgi/query-pr.cgi?pr=7925 > > http://www.freebsd.org/cgi/query-pr.cgi?pr=6858 > > > > -john > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > with "unsubscribe freebsd-current" in the body of the message > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message