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 Message-ID: <Mutt.19970120035749.davidn@labs.blaze.net.au> In-Reply-To: <Pine.BSF.3.95.970119072949.27255D-100000@mail.MCESTATE.COM>; from Vincent Poy on Jan 19, 1997 07:32:08 -0800 References: <Pine.BSF.3.95.970119072949.27255D-100000@mail.MCESTATE.COM>
next in thread | previous in thread | raw e-mail | index | archive | help
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/
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Mutt.19970120035749.davidn>