From owner-freebsd-current Sun Nov 8 07:09:50 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA19247 for freebsd-current-outgoing; Sun, 8 Nov 1998 07:09:50 -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 HAA19242 for ; Sun, 8 Nov 1998 07:09:48 -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 QAA09976; Sun, 8 Nov 1998 16:09:34 +0100 (CET) Received: (from eivind@localhost) by bitbox.follo.net (8.8.8/8.8.6) id QAA17514; Sun, 8 Nov 1998 16:09:34 +0100 (MET) Message-ID: <19981108160934.30826@follo.net> Date: Sun, 8 Nov 1998 16:09:34 +0100 From: Eivind Eklund To: John Fieber Cc: current@FreeBSD.ORG Subject: Re: The infamous dying daemons bug References: <19981108140935.06929@follo.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89.1i In-Reply-To: ; from John Fieber on Sun, Nov 08, 1998 at 09:22:50AM -0500 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, Nov 08, 1998 at 09:22:50AM -0500, John Fieber wrote: > One question: Is the problem "sticky"? By that I mean, if it is > triggered by a memomry shortage, is something in the kernel > corrupted that tends to kill/corrupt daemons from that point in > time on, or is it just something that affects isolated processes. All daemons running at that point seems to get something corrupted. If you restart the daemon, it won't happen again until you again run out of memory (or whatever it is that trigger the corruption). > The symptom (junk pointer to low in ined's case) is obviously > triggered by some action of the process, but is the problem > itself triggered by an action of that same process? The 'junk pointer too low to make sense' seems to be a different problem, caused by race conditions in the signal handlers of inetd. There is a patch fixing this in a PR; however, David has said that this is not the 'right fix', so it has not been committed. Eivind. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message