From owner-freebsd-current Sun Nov 8 07:16:06 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA19723 for freebsd-current-outgoing; Sun, 8 Nov 1998 07:16:06 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from root.com (implode.root.com [198.145.90.17]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA19712 for ; Sun, 8 Nov 1998 07:16:04 -0800 (PST) (envelope-from xroot@root.com) Received: from implode.root.com (localhost [127.0.0.1]) by root.com (8.8.5/8.8.5) with ESMTP id HAA03267; Sun, 8 Nov 1998 07:17:12 -0800 (PST) Message-Id: <199811081517.HAA03267@root.com> To: Eivind Eklund cc: John Fieber , current@FreeBSD.ORG Subject: Re: The infamous dying daemons bug In-reply-to: Your message of "Sun, 08 Nov 1998 16:09:34 +0100." <19981108160934.30826@follo.net> From: David Greenman Reply-To: dg@root.com Date: Sun, 08 Nov 1998 07:17:11 -0800 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). brk(2) will fail and return ENOMEM if the system is low on swap space. If the application (phk malloc or the caller of malloc?) isn't prepared for this, it may end up with a NULL pointer that it doesn't expect - perhaps not even tripping over it until sometime later. -DG David Greenman Co-founder/Principal Architect, The FreeBSD Project To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message