From owner-freebsd-questions@FreeBSD.ORG Wed Jun 30 13:46:01 2004 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E844616A4CE for ; Wed, 30 Jun 2004 13:46:01 +0000 (GMT) Received: from internet.potentialtech.com (h-66-167-251-6.phlapafg.covad.net [66.167.251.6]) by mx1.FreeBSD.org (Postfix) with ESMTP id C0DD143D48 for ; Wed, 30 Jun 2004 13:46:01 +0000 (GMT) (envelope-from wmoran@potentialtech.com) Received: from working.potentialtech.com (pa-plum-cmts1e-68-68-113-64.pittpa.adelphia.net [68.68.113.64]) by internet.potentialtech.com (Postfix) with ESMTP id EE52E69A39; Wed, 30 Jun 2004 09:45:32 -0400 (EDT) Date: Wed, 30 Jun 2004 09:45:31 -0400 From: Bill Moran To: "Steve Bertrand" Message-Id: <20040630094531.59de248a.wmoran@potentialtech.com> In-Reply-To: <4860.209.167.16.15.1088601951.squirrel@209.167.16.15> References: <4860.209.167.16.15.1088601951.squirrel@209.167.16.15> Organization: Potential Technologies X-Mailer: Sylpheed version 0.9.12 (GTK+ 1.2.10; i386-portbld-freebsd4.9) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit cc: freebsd-questions@freebsd.org Subject: Re: kern.ipc.nmbclusters X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 30 Jun 2004 13:46:02 -0000 "Steve Bertrand" wrote: > I have a machine that is rebooting with the following error: > > "All mbuf clusters exhausted, please see tuning(7)." > > Which through google and man tuning I was able to figure out that indeed, > mbufs were exhausted. So I tried to set kern.ipc.nmbclusters=4096 (which > should cover the load of the server), but found out after it is not a > run-time tunable parameter. > > I searched google, and gathered that I should put this setting in > /boot/loader.conf. > > This is contradictory of me usually putting kernel tweaks in > /etc/sysctl.conf. > > >From your experience, where is the best place to load this variable from, > why is it a better location, and what will happen if I don't load it from > the proper place? You have to put it in loader.conf because that value is set _very_ early in the boot process (before sysctl.conf is used) and can not be changed later. You can also put this value in your kernel config and recompile your kernel. -- Bill Moran Potential Technologies http://www.potentialtech.com