From owner-freebsd-current  Wed Feb 12 04:55:12 1997
Return-Path: <owner-current>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id EAA26472
          for current-outgoing; Wed, 12 Feb 1997 04:55:12 -0800 (PST)
Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id EAA26441;
          Wed, 12 Feb 1997 04:55:03 -0800 (PST)
Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.3/8.6.9) id XAA16078; Wed, 12 Feb 1997 23:41:50 +1100
Date: Wed, 12 Feb 1997 23:41:50 +1100
From: Bruce Evans <bde@zeta.org.au>
Message-Id: <199702121241.XAA16078@godzilla.zeta.org.au>
To: hackers@freebsd.org, mishania@demos.su
Subject: Re: upcoming version suggestions
Cc: ache@nagual.ru, bag@demos.su, current@freebsd.org
Sender: owner-current@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

>There's really need to set FDSETSIZE (/sys/sys/types.h, afair) default
>to something like 1024, - then you don't need to recompile kernel as
>soon as you start news server and/or ftp/www, like, loaded one. Example:
>you won't get any improvements rearranging MAXOPEN value, before you
>rearrange FDSETSIZE.

There hasn't been any need to recompile the kernel since the
kernel select size was made dynamic 6 months ago in -current.
You can increase the number of fd's up to the hard resource limit
using setrlimit() and root can increase the hard resource limit
using `sysctl -w kern.maxfiles=nnnn' (this has been possible since
FreeBSD-2.0, except for bugs) and /etc/login.conf (this has only
become available recently).

No particular value of FDSETSIZE works unless the resource limit is
restricted to the old value of FDSETSIZE (256).  This can't be fixed
without breaking binary compatibility :-(.

Bruce