From owner-freebsd-current Mon Nov 9 08:26:59 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA21407 for freebsd-current-outgoing; Mon, 9 Nov 1998 08:26:59 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from garman.dyn.ml.org (pm106-17.dialip.mich.net [192.195.231.219]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id IAA21393 for ; Mon, 9 Nov 1998 08:26:54 -0800 (PST) (envelope-from garman@garman.dyn.ml.org) Message-Id: <199811091626.IAA21393@hub.freebsd.org> Received: (qmail 21094 invoked from smtpd); 9 Nov 1998 16:28:09 -0000 Received: from localhost.garman.net (HELO garman.dyn.ml.org) (127.0.0.1) by localhost.garman.net with SMTP; 9 Nov 1998 16:28:09 -0000 Date: Mon, 9 Nov 1998 11:28:08 -0500 (EST) From: garman@earthling.net Reply-To: garman@earthling.net Subject: Re: The infamous dying daemons bug To: wollman@khavrinen.lcs.mit.edu cc: dg@root.com, eivind@yes.no, jfieber@indiana.edu, current@FreeBSD.ORG In-Reply-To: <199811090417.XAA13563@khavrinen.lcs.mit.edu> MIME-Version: 1.0 Content-Type: TEXT/plain; CHARSET=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 8 Nov, Garrett Wollman wrote: > 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. > Yes, this fits the symptoms i'm seeing here with samba. The daemon will be fine as long as it has not been swapped out; after that, it's *poof*. That's also probably why people with heavy-use samba servers haven't seen this problem. 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