Date: Sat, 5 Sep 1998 10:18:59 -0700 (PDT) From: Tom <tom@uniserve.com> To: Andrew McNaughton <andrew@squiz.co.nz> Cc: 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: <Pine.BSF.3.96.980905101742.6991B-100000@shell.uniserve.ca> In-Reply-To: <Pine.BSF.3.96.980906015229.4203B-100000@aniwa.sky>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sun, 6 Sep 1998, Andrew McNaughton wrote: > 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. > 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 Yes. > if anything can't? sysctl and ulimit have sorted out my recent problems, Number of mbufs (netstat -m), but the mbufs can be increased outside MAXUSERS too. > with numbers of processes and files, but perhaps there's other reasons > why I should increase MAXUSERS? > > I'm currently running a busy webserver with MAXUSERS=64. Apache docs > suggest MAXUSERS=256. > > Andrew McNaughton Tom 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?Pine.BSF.3.96.980905101742.6991B-100000>