Date: Sat, 05 Sep 1998 10:11:15 -0700 From: Mike Smith <mike@smith.net.au> To: andrew@squiz.co.nz Cc: Tom <tom@uniserve.com>, The Hermit Hacker <scrappy@hub.org>, Bob K <melange@yip.org>, The Lab <thelab@nmarcom.com>, freebsd-stable@FreeBSD.ORG Subject: Re: too many open files Message-ID: <199809051711.KAA05862@word.smith.net.au> In-Reply-To: Your message of "Sun, 06 Sep 1998 01:59:33 %2B1200." <Pine.BSF.3.96.980906015229.4203B-100000@aniwa.sky>
next in thread | previous in thread | raw e-mail | index | archive | help
> On Fri, 4 Sep 1998, Tom wrote: > > > > One requires a rebuild/reboot of the system...one doesn't. IN a > > > production environment, /etc/login.conf is about the only choice... > > > > Except you are talking about two different things. MAXUSERS controls > > the system wide file table. /etc/login.conf controls per-user file > > limits. You can increase the limits in /etc/login.conf all you want, but > > if the system wide table is full, you will still get "too many open files" > > errors. > > > > Tom > > between sysctl and login.conf, either can be set without a rebuild. No. The kern.maxfiles sysctl shouldn't be writable in 2.2, and it's not writable in 3.0; it refers to the size of a static table. > references to MAXUSERS seem to suggest that it affects a whole range of > values. Some of it can be overridden via sysctl. Can anyone clarify what > if anything can't? sysctl and ulimit have sorted out my recent problems, > with numbers of processes and files, but perhaps there's other reasons > why I should increase MAXUSERS? None of the critical items can be adjusted at runtime; the two critical items are the maximum number of open files in the system, and the maximum number of mbuf clusters. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199809051711.KAA05862>