From owner-freebsd-current Fri Nov 20 20:18:26 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA06165 for freebsd-current-outgoing; Fri, 20 Nov 1998 20:18:26 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from garman.dyn.ml.org ([192.195.231.211]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id UAA06160 for ; Fri, 20 Nov 1998 20:18:19 -0800 (PST) (envelope-from garman@garman.dyn.ml.org) Message-Id: <199811210418.UAA06160@hub.freebsd.org> Received: (qmail 2946 invoked from smtpd); 21 Nov 1998 04:18:06 -0000 Received: from localhost.garman.net (HELO garman.dyn.ml.org) (127.0.0.1) by localhost.garman.net with SMTP; 21 Nov 1998 04:18:06 -0000 Date: Fri, 20 Nov 1998 23:18:05 -0500 (EST) From: garman@earthling.net Reply-To: garman@earthling.net Subject: Re: more dying daemons To: terbart@aye.net 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 20 Nov, Barrett Richardson wrote: > > Swap usage at 64% after only hour seems awfully high. I've seem similar > behaviour in the world of SCO. Folks just under the threshold of what > they can get out of their box with given swap/memory size with 3.2v4.2 > are having no problems. They upgrade to Open Server 5, put the same load > on it, and the box starts a slow downward spiral and finally becomes > unusable. They reboot it, and its ok for a couple of hours. > The 64% swap usage figure was from an uptime of two days, not an hour. I have however easily produced swap usages around 56-58% (synthetically, of course) within 10-20 minutes while testing some of the potential fixes posted here. i've never had a problem with insufficient swap before... > You can use vnconfig to test the beast without reslicing if you > have ample disk space. > yes, but isn't this just a workaround? I rarely (if ever) run out of memory and swap, and my usage usually stabilizes around 65% after a few days. i would expect a system to behave reasonably even in the face of memory shortages. corrupting running processes (when they fork?) is not a reasonable behavior. > If problems persist, entertain the idea that something you > are using has a mongo memory leak. > basically this is just my personal workstation box. whats running include netscape, tkrat (with huge mailboxes :/), windowmaker, and various other X apps. nothing particularly suspect (except perhaps for netscape :)) 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