From owner-freebsd-stable Mon Sep 20 11:32:42 1999 Delivered-To: freebsd-stable@freebsd.org Received: from dt014nb6.san.rr.com (dt014nb6.san.rr.com [24.30.129.182]) by hub.freebsd.org (Postfix) with ESMTP id 5E64A15B79 for ; Mon, 20 Sep 1999 11:32:37 -0700 (PDT) (envelope-from Doug@gorean.org) Received: from localhost (doug@localhost) by dt014nb6.san.rr.com (8.9.3/8.8.8) with ESMTP id LAA03767; Mon, 20 Sep 1999 11:28:04 -0700 (PDT) (envelope-from Doug@gorean.org) Date: Mon, 20 Sep 1999 11:28:04 -0700 (PDT) From: Doug X-Sender: doug@dt014nb6.san.rr.com To: Tom Cc: Kip Macy , freebsd-stable@freebsd.org Subject: Re: kern.maxfiles and kern.maxfilesperproc In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 20 Sep 1999, Tom wrote: > On Sun, 19 Sep 1999, Kip Macy wrote: > > > Is kern.maxfiles the total number of files that can be open on the system > > at one time? If so it seems very silly that by default it is the same > > number as kern.maxfilesperproc -- meaning that any process can use up the > > total number of files available to the system. > > Thanks. > > Howerver, login.conf controls those limits. maxfilesperproc should > probably be deprecated now. Given the spotty history of login.conf, and the extreme lack of enthusiasm for finishing it and/or keeping it up to date, I'm not sure we should be deprecating anything in favor of it. Also, the fact that you _can_ use login.conf to set the per usr/per process limits is another vote in favor of keeping the total maxfiles and the per process maxfiles the same. Doug -- "My mama told me, my mama said, 'don't cry.' She said, 'you're too young a man to have as many women you got.' I looked at my mother dear and didn't even crack a smile. I said, 'If women kill me, I don't mind dyin!'" - John Belushi as "Joliet" Jake Blues, "I Don't Know" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message