Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 19 Jul 1999 17:53:41 -0700
From:      Mike Smith <mike@smith.net.au>
To:        Gregory Sutter <gsutter@pobox.com>
Cc:        hackers@freebsd.org
Subject:   Re: maxfiles == maxfilesperproc ? 
Message-ID:  <199907200053.RAA02591@dingo.cdrom.com>
In-Reply-To: Your message of "Mon, 19 Jul 1999 17:52:39 PDT." <19990719175239.E45481@001101.zer0.org> 

next in thread | previous in thread | raw e-mail | index | archive | help
> 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




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199907200053.RAA02591>