From owner-cvs-ports  Tue Aug 19 05:08:27 1997
Return-Path: <owner-cvs-ports>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.5/8.8.5) id FAA01043
          for cvs-ports-outgoing; Tue, 19 Aug 1997 05:08:27 -0700 (PDT)
Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19])
          by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id FAA01026;
          Tue, 19 Aug 1997 05:08:08 -0700 (PDT)
Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.5/8.6.9) id WAA09900; Tue, 19 Aug 1997 22:03:28 +1000
Date: Tue, 19 Aug 1997 22:03:28 +1000
From: Bruce Evans <bde@zeta.org.au>
Message-Id: <199708191203.WAA09900@godzilla.zeta.org.au>
To: cvs-all@freebsd.org, cvs-committers@freebsd.org, cvs-ports@freebsd.org,
        peter@freebsd.org
Subject: Re: cvs commit: ports/x11/XFree86/patches patch-af
Sender: owner-cvs-ports@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

>  Added files:
>    x11/XFree86/patches  patch-af 
>  Log:
>  Don't use OPEN_MAX to determine how many sockets we can have open, it's
>  too pessimistic on FreeBSD.  This raises the number of connections from
>  63 to 128  (I kept running into the 63 limit all the time).  There are
>  other parts limited at 128 clients as well, but changing them to go beyond
>  128 looks like it would have some worrying implications...

I will delete the definitions of OPEN_MAX and CHILD_MAX soon (defining
them means that there is a fixed limit), so defining them is wrong on
all systems with the corresponding setrlimit()s).  This might break some
broken ports properly :-).  It will break doscmd (which uses a strange
mixture of OPEN_MAX and sysconf(_SC_OPEN_MAX)).  I fixed all other uses
of them in /usr/src some time ago.

Bruce