From owner-freebsd-current Sun Nov 8 20:17:39 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA05992 for freebsd-current-outgoing; Sun, 8 Nov 1998 20:17:39 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from khavrinen.lcs.mit.edu (khavrinen.lcs.mit.edu [18.24.4.193]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA05987 for ; Sun, 8 Nov 1998 20:17:38 -0800 (PST) (envelope-from wollman@khavrinen.lcs.mit.edu) Received: (from wollman@localhost) by khavrinen.lcs.mit.edu (8.9.1/8.9.1) id XAA13563; Sun, 8 Nov 1998 23:17:00 -0500 (EST) (envelope-from wollman) Date: Sun, 8 Nov 1998 23:17:00 -0500 (EST) From: Garrett Wollman Message-Id: <199811090417.XAA13563@khavrinen.lcs.mit.edu> To: dg@root.com Cc: Eivind Eklund , John Fieber , current@FreeBSD.ORG Subject: Re: The infamous dying daemons bug In-Reply-To: <199811081517.HAA03267@root.com> References: <19981108160934.30826@follo.net> <199811081517.HAA03267@root.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG < said: > 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. Totally unrelated to the problem. It seems, so far as I was able to characterize, to happen to daemons which are *swapped out* at the time of the memory shortage. If it's active enough to still be in core, it doesn't get spammed. -GAWollman -- Garrett A. Wollman | O Siem / We are all family / O Siem / We're all the same wollman@lcs.mit.edu | O Siem / The fires of freedom Opinions not those of| Dance in the burning flame MIT, LCS, CRS, or NSA| - Susan Aglukark and Chad Irschick To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message