> 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. \\ [EMAIL PROTECTED]
\\ -- Joseph Merrick \\ [EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
