From owner-freebsd-bugs Tue Feb 26 0: 1:41 2002 Delivered-To: freebsd-bugs@freebsd.org Received: from mail.webjockey.net (mail.webjockey.net [208.141.46.3]) by hub.freebsd.org (Postfix) with ESMTP id 08DC437B404; Tue, 26 Feb 2002 00:01:38 -0800 (PST) Received: from outloud.org (IDENT:www@home.webjockey.net [208.141.46.11]) (authenticated) by mail.webjockey.net (8.11.6/8.11.6) with ESMTP id g1Q81YJ06974; Tue, 26 Feb 2002 03:01:34 -0500 (EST) (envelope-from gary@outloud.org) Received: from 24.206.7.236 (SquirrelMail authenticated user ancient) by test.outloud.org with HTTP; Tue, 26 Feb 2002 03:01:51 -0500 (EST) Message-ID: <3148.24.206.7.236.1014710511.squirrel@test.outloud.org> Date: Tue, 26 Feb 2002 03:01:51 -0500 (EST) Subject: Re: kern/34275: high load/swap on 4.4-RELEASE From: "Storms of Perfection" To: In-Reply-To: <200202260724.g1Q7OXM87328@freefall.freebsd.org> References: <200202260724.g1Q7OXM87328@freefall.freebsd.org> X-Priority: 3 Importance: Normal X-MSMail-Priority: Normal Cc: X-Mailer: SquirrelMail (version 1.2.6 [cvs]) MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org I upgraded to 4.5-STABLE and the problem went away. I think it was a issue with the vm subsystem, or something of the sorts. All fixed now ;-) > Synopsis: high load/swap on 4.4-RELEASE > > State-Changed-From-To: open->feedback > State-Changed-By: silby > State-Changed-When: Mon Feb 25 23:23:18 PST 2002 > State-Changed-Why: > Gary, did you figure out what was happening on this system? > Looking at the info your provided, I'm assuming that a cgi script > or some other ram hog went nuts - you're using almost a gigabyte > of swap space. > > http://www.FreeBSD.org/cgi/query-pr.cgi?pr=34275 -- Gary Stanley "Have we not heard the chimes at midnight?" (2 Henry IV III ii 212, paraphrase) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message