From owner-freebsd-current Sun Nov 8 18:05:57 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA23131 for freebsd-current-outgoing; Sun, 8 Nov 1998 18:05:57 -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 SAA23126 for ; Sun, 8 Nov 1998 18:05:52 -0800 (PST) (envelope-from garman@garman.dyn.ml.org) Message-Id: <199811090205.SAA23126@hub.freebsd.org> Received: (qmail 3099 invoked from smtpd); 9 Nov 1998 02:07:07 -0000 Received: from localhost.garman.net (HELO garman.dyn.ml.org) (127.0.0.1) by localhost.garman.net with SMTP; 9 Nov 1998 02:07:07 -0000 Date: Sun, 8 Nov 1998 21:07:06 -0500 (EST) From: garman@earthling.net Reply-To: garman@earthling.net Subject: Re: The infamous dying daemons bug To: green@unixhelp.org cc: current@FreeBSD.ORG In-Reply-To: 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, Brian Feldman wrote: > Yech, that really isn't good having your process's memory disappearing > under you... anyone have any idea why for instance I don't have this > problem, nor do many others? > whats your swap usage look like? this problem (for me at least) is much much more likely to occur with a (relatively) high amount of swap usage, usually in the 50-70% range (out of 150MB of swap) 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