From owner-freebsd-hackers  Wed Jan 11 15:38:13 1995
Return-Path: hackers-owner
Received: (from root@localhost) by freefall.cdrom.com (8.6.9/8.6.6) id PAA13603 for hackers-outgoing; Wed, 11 Jan 1995 15:38:13 -0800
Received: from ibp.ibp.fr (ibp.ibp.fr [132.227.60.30]) by freefall.cdrom.com (8.6.9/8.6.6) with ESMTP id PAA13596 for <hackers@FreeBSD.org>; Wed, 11 Jan 1995 15:38:11 -0800
Received: from blaise.ibp.fr (blaise.ibp.fr [132.227.60.1])
	by ibp.ibp.fr (8.6.8/jtpda-5.0) with SMTP id AAA26767
	; Thu, 12 Jan 1995 00:39:02 +0100
Received: by blaise.ibp.fr (4.1/SMI-4.1)
	id AA16993; Thu, 12 Jan 95 00:39:08 +0100
From: roberto@blaise.ibp.fr (Ollivier ROBERT)
Message-Id: <9501112339.AA16993@blaise.ibp.fr>
Subject: Re: Meaning of maxfiles
To: bde@zeta.org.au (Bruce Evans)
Date: Thu, 12 Jan 1995 00:39:07 +0100 (MET)
Cc: hackers@FreeBSD.org
In-Reply-To: <199501112329.KAA23191@godzilla.zeta.org.au> from "Bruce Evans" at Jan 12, 95 10:29:21 am
X-Mailer: ELM [version 2.4 PL23beta2]
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
Content-Length: 828       
Sender: hackers-owner@FreeBSD.org
Precedence: bulk

> 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