From owner-freebsd-stable Sun Jun 13 13:29: 0 1999 Delivered-To: freebsd-stable@freebsd.org Received: from scientia.demon.co.uk (scientia.demon.co.uk [212.228.14.13]) by hub.freebsd.org (Postfix) with ESMTP id 9E7C114E29 for ; Sun, 13 Jun 1999 13:28:25 -0700 (PDT) (envelope-from ben@scientia.demon.co.uk) Received: from rainbow5.scientia.demon.co.uk ([192.168.1.2] ident=exim) by scientia.demon.co.uk with esmtp (Exim 3.02 #1) id 10tFfm-0001oq-00; Sun, 13 Jun 1999 20:12:02 +0100 (envelope-from ben@rainbow5.scientia.demon.co.uk) Received: from rainbow5.scientia.demon.co.uk (ident=ben) by rainbow5.scientia.demon.co.uk with local (Exim 3.02 #1) id 10tFfm-0000iI-00; Sun, 13 Jun 1999 20:12:02 +0100 (envelope-from ben@rainbow5.scientia.demon.co.uk) Date: Sun, 13 Jun 1999 20:12:02 +0100 From: Ben Smithurst To: "Nikolai E. Wendorf" Cc: freebsd-stable@FreeBSD.ORG Subject: Re: open files Message-ID: <19990613201202.A2709@rainbow5.scientia.demon.co.uk> References: <3763F4D4.4D17E03F@kolia.north.gencon.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: <3763F4D4.4D17E03F@kolia.north.gencon.com> Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Nikolai E. Wendorf wrote: > System is 3.2-RELEASE, and this keeps coming up in /var/log/messages: > > Jun 13 07:32:52 fw1 syslogd: /var/run/utmp: Too many open files in system > Jun 13 07:32:52 fw1 syslogd: /var/run/utmp: Too many open files in system > > Kernel was built for 32 users, it is a firewall only > machine with 0 users. On previous 2.2.8 system I used > to build the kernel with: > options CHILD_MAX=384 > options OPEN_MAX=512 CHILD_MAX and OPEN_MAX aren't used in 3.x systems. The max number of processes (NPROC) is defined as (20 + 16 * MAXUSERS), MAXFILES is (2 * NPROC). So with maxusers 32, you should be able to have 1000-ish open files. Try increasing maxusers (say, to 64) and see if that helps matters. (These definitions are in /sys/conf/param.c) > I believe the answer lies in login.conf but since I've not gone to the 3. > yet I thought a sanity check was in order. login.conf can only set limits for specific classes, AFAIK, and cannot increase the limits above the limits set at kernel compile time. -- Ben Smithurst | PGP: 0x99392F7D ben@scientia.demon.co.uk | key available from keyservers and | ben+pgp@scientia.demon.co.uk To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message