Date: Thu, 12 Jan 1995 00:39:07 +0100 (MET) From: roberto@blaise.ibp.fr (Ollivier ROBERT) To: bde@zeta.org.au (Bruce Evans) Cc: hackers@FreeBSD.org Subject: Re: Meaning of maxfiles Message-ID: <9501112339.AA16993@blaise.ibp.fr> In-Reply-To: <199501112329.KAA23191@godzilla.zeta.org.au> from "Bruce Evans" at Jan 12, 95 10:29:21 am
next in thread | previous in thread | raw e-mail | index | archive | help
> the desiredvnodes limit in getnewvnode() should do. (desiredvnodes
> and nbuf seem to be too-small limits - 10 and 41 times smaller than
> I wanted and used for 1.1.5.)
So how not to run out of open files ? 256 is far too low a limit for
me.
> Don't do this. OPEN_MAX should only be defined if the per-process
> limit is fixed. It is abused in the kernel to specify the current
> per-process limit. Libraries and user programs aren't compiled with
> option OPEN_MAX=128, so they see the bogus fixed OPEN_MAX of 64
> instead of the bogus fixed OPEN_MAX of 128.
At the time it fixed my too much processes problem. I'm currently recompiling
without OPEN_MAX and CHILD_MAX.
--
Ollivier ROBERT -=- The daemon is FREE! -=- roberto@FreeBSD.ORG
FreeBSD keltia 2.1.0-Development #2: Sat Jan 7 00:55:25 MET 1995
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?9501112339.AA16993>