From owner-freebsd-hackers Mon Jul 19 17:59: 4 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by hub.freebsd.org (Postfix) with ESMTP id 6363714DE5 for ; Mon, 19 Jul 1999 17:59:01 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost.cdrom.com [127.0.0.1]) by dingo.cdrom.com (8.9.3/8.8.8) with ESMTP id RAA02591; Mon, 19 Jul 1999 17:53:41 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Message-Id: <199907200053.RAA02591@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Gregory Sutter Cc: hackers@freebsd.org Subject: Re: maxfiles == maxfilesperproc ? In-reply-to: Your message of "Mon, 19 Jul 1999 17:52:39 PDT." <19990719175239.E45481@001101.zer0.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 19 Jul 1999 17:53:41 -0700 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > hax0rs, > > In sys/conf/param.c (in -STABLE), both maxfiles and maxfilesperproc are > set equal to MAXFILES. This doesn't make much sense to me. It seems that > maxfiles should be set to be greater than maxfilesperproc by default, so > that one process can't consume all of the file descriptors. > > I noticed this while building a system that will be running some very > large processes with many open files, so set maxfilesperproc on that box > equal to MAXFILES - 512, but this metric is not appropriate for systems > with small MAXUSERS (like GENERIC). So... > > 1. Should maxfiles be, by default, larger than maxfilesperproc? Not really; these numbers are just ultra-hard limits. You should typically use login classes and the per-process limits to enforce these controls. -- \\ The mind's the standard \\ Mike Smith \\ of the man. \\ msmith@freebsd.org \\ -- Joseph Merrick \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message