Date: Mon, 3 Jan 2000 12:06:14 -0500 (EST) From: Kelly Yancey <kbyanc@posi.net> To: Kip Macy <kip@lyris.com> Cc: "John W. DeBoskey" <jwd@unx.sas.com>, freebsd-current@FreeBSD.ORG Subject: Re: maxfiles same as maxfilesperproc ?? Message-ID: <Pine.BSF.4.05.10001031203260.12522-100000@kronos.alcnet.com> In-Reply-To: <Pine.SOL.4.05.10001020055470.20107-100000@luna.lyris.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Well, maybe a patch will get things moving. I just submitted kern/15860 with a simple patch which reduces the default maxfilesperproc to be 20 less than maxfiles. I got the mailing list reference wrong in the PR, but -hackers has it's share of similar requests :). Kelly On Sun, 2 Jan 2000, Kip Macy wrote: > I made the same comment several months ago and received a rather cool > reception. I was simply told to change it to my liking in login.conf. > > > -Kip > > On Sat, 1 Jan 2000, John W. DeBoskey wrote: > > > Hi, > > > > On a FreeBSD 4.0-19991223-SNAP system... > > > > I just ran into a situation that caused me to have to reboot > > the machine before understanding what had really happenned... > > > > The problems comes down to: > > > > kern.maxfiles: 4136 > > kern.maxfilesperproc: 4136 > > > > > > Thus, because I had a root uid server that looped chewing > > up file descriptors, it also filled up the system file table. > > > > I realize this is end-user/administrator fixable, but I'm > > not sure the default should have these be the same... > > > > Thanks, > > John > > -- Kelly Yancey - kbyanc@posi.net - Richmond, VA Analyst / E-business Development, Bell Industries http://www.bellind.com/ Maintainer, BSD Driver Database http://www.posi.net/freebsd/drivers/ Coordinator, Team FreeBSD http://www.posi.net/freebsd/Team-FreeBSD/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" 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.4.05.10001031203260.12522-100000>