From owner-freebsd-bugs@FreeBSD.ORG Sat Apr 24 01:01:26 2004 Return-Path: Delivered-To: freebsd-bugs@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2ED9D16A4CE for ; Sat, 24 Apr 2004 01:01:26 -0700 (PDT) Received: from mtaw4.prodigy.net (mtaw4.prodigy.net [64.164.98.52]) by mx1.FreeBSD.org (Postfix) with ESMTP id B1D6443D5D for ; Sat, 24 Apr 2004 01:01:25 -0700 (PDT) (envelope-from kris@obsecurity.org) Received: from obsecurity.dyndns.org (50795628853ef67780e42ac09be59214@adsl-67-115-73-128.dsl.lsan03.pacbell.net [67.115.73.128]) by mtaw4.prodigy.net (8.12.10/8.12.10) with ESMTP id i3O81O5k021792 for ; Sat, 24 Apr 2004 01:01:24 -0700 (PDT) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id A7AFD51F2C; Sat, 24 Apr 2004 01:01:24 -0700 (PDT) Date: Sat, 24 Apr 2004 01:01:24 -0700 From: Kris Kennaway To: Kris Kennaway Message-ID: <20040424080124.GA24971@xor.obsecurity.org> References: <200404010200.i3120e8s065381@freefall.freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200404010200.i3120e8s065381@freefall.freebsd.org> User-Agent: Mutt/1.4.2.1i cc: freebsd-bugs@FreeBSD.org Subject: Re: kern/64971: A squid process larger than 3G X-BeenThere: freebsd-bugs@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 24 Apr 2004 08:01:26 -0000 On Wed, Mar 31, 2004 at 06:00:40PM -0800, Kris Kennaway wrote: > What you described is not squid crashing, but init. > > It sounds like you've adjusted the kernel parameters inappropriately, > and that's what you need to fix. I don't know the solution off-hand, > but check the mailing list archives for extensive discussion on how to > tune kernel parameters for large-memory configurations. > > Be aware that what you're trying to do may be impossible - i.e. if you > really need 3GB of RAM for squid, it sounds like it's being heavily > used, and may therefore also require a lot of kernel memory to manage > the network resources.q If you need more than 1GB of kernel memory, > you're out of luck with only 4GB total. Did you resolve this problem? Kris