From owner-freebsd-questions Mon Feb 3 22:42: 5 2003 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 4E45337B401 for ; Mon, 3 Feb 2003 22:42:03 -0800 (PST) Received: from ei.bzerk.org (ei.xs4all.nl [213.84.67.5]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4A2E843F85 for ; Mon, 3 Feb 2003 22:41:58 -0800 (PST) (envelope-from fbsd-q@bzerk.org) Received: from ei.bzerk.org (BOFH@localhost [127.0.0.1]) by ei.bzerk.org (8.12.6/8.12.6) with ESMTP id h146heJi082253; Tue, 4 Feb 2003 07:43:40 +0100 (CET) (envelope-from stable@ei.bzerk.org) Received: (from stable@localhost) by ei.bzerk.org (8.12.6/8.12.6/Submit) id h146heSq082252; Tue, 4 Feb 2003 07:43:40 +0100 (CET) Date: Tue, 4 Feb 2003 07:43:40 +0100 From: Ruben de Groot To: aSe Cc: FreeBSD-Questions , Ruben de Groot Subject: Re: Too many files open / file: table is full Message-ID: <20030204064340.GA82189@ei.bzerk.org> References: <20030203135208.GA78364@ei.bzerk.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4i Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Tue, Feb 04, 2003 at 12:16:23AM -0500, aSe typed: > >This is not a matter of diskspace. The kernel holds a fixed length table > >in memory with all open files. If this table gets full it usually means > >one of two things: > > > >1) You have a runaway application, opening way too many files. Identify > >the application and fix or disable it. > > > >2) You're running a kernel with a too low value for maxusers (which, > >among other things, determines the maximum amount of open files). The > >default in 4.7-RELEASE is 0, which means: optimize according to amount > >of memory installed. The default is usually O.K. If not, one option is > >to simply install more memory. > > The machine itself runs several logging applications and things of that > nature. I didn't think It was an issue with HD. Nor do I believe its ram, > It has 512mb installed, and 256mb of swap. As it stands right now it has > 270mb free and hasn't touched the swap. Right now maxusers is set to 6, > I didn't realize it would play a role in this instance. You should set maxusers to 0. That way, it will be sized at boot time according to the amount of memory you installed. > Jack Stone suggested looking up the number of max open files by doing > "sysctl kern.maxfiles" It returns only "232" which to me seems like a > very small number. He also suggested to change it using > "sysctl -w kern.maxfiles=4160." > > My question to you is, does maxusers play more of a role then just > the max number of open files. In the long run would it be better to > just set maxusers to 0 or just change the kern.maxfiles? It does. According to tuning(7): kern.maxusers controls the scaling of a number of static system tables, including defaults for the maximum number of open files, sizing of net- work memory resources, etc. You can set maxusers to 0 by either recompiling your kernel or by setting the value in loader.conf(5) Ruben > > Thank you! > Gordon Keesler [aSe@SysFail.com] > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-questions" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message