From owner-freebsd-current Sun Jan 19 09:01:53 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id JAA08849 for current-outgoing; Sun, 19 Jan 1997 09:01:53 -0800 (PST) Received: from mail.crl.com (mail.crl.com [165.113.1.22]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id JAA08842 for ; Sun, 19 Jan 1997 09:01:50 -0800 (PST) Received: from labs.usn.blaze.net.au by mail.crl.com with SMTP id AA10810 (5.65c/IDA-1.5 for ); Sun, 19 Jan 1997 09:01:27 -0800 Received: (from davidn@localhost) by labs.usn.blaze.net.au (8.8.4/8.8.4) id DAA00416; Mon, 20 Jan 1997 03:57:49 +1100 (EST) Message-Id: Date: Mon, 20 Jan 1997 03:57:49 +1100 From: davidn@unique.usn.blaze.net.au (David Nugent) To: vince@mail.MCESTATE.COM (Vincent Poy) Cc: current@FreeBSD.ORG Subject: Re: -current kernel problem References: X-Mailer: Mutt 0.56 Mime-Version: 1.0 In-Reply-To: ; from Vincent Poy on Jan 19, 1997 07:32:08 -0800 Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Vincent Poy writes: > With the same kernel config and the most recent -current, building > a new kernel and updating from the previous kernel of 10 days ago, running > the ircd IRC server gives the following: > > max kernel fd's only 64 =0 > > ircd fd table too big > Hard Limit: 64 IRC max: 0 > Fix MAXCONNECTIONS > > Anyone have any ideas? Yes. man 5 login.conf You probably compiled it with fd's == 256 or similar, but this is no longer a hard-coded variable. To immediately rectify the problem - assuming you haven't already done so, install login.conf from /usr/src/etc and edit the "default" entry "openfiles=64" or "openfiles=256" (or whatever value you compiled into ircd). As soon as limits(1) is committed (probably tomorrow), you should probably restore openfiles=64, and instead create a class which has the appropriate number of filehandles instead. Then, as root in your rc.d script, put: eval `limits -e -C class` or don't worry about the class and use the shell independant: eval `limits -e -n 256` or assuming it is started from a /bin/sh script: ulimit -n 256 Actually, if your process starts out as root, you can do the last one now without having to edit /etc/login.conf at all. Regards, David Nugent - Unique Computing Pty Ltd - Melbourne, Australia Voice +61-3-9791-9547 Data/BBS +61-3-9792-3507 3:632/348@fidonet davidn@freebsd.org davidn@blaze.net.au http://www.blaze.net.au/~davidn/