From owner-cvs-all  Thu Jun  4 20:06:49 1998
Return-Path: <owner-cvs-all@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id UAA12575
          for cvs-all-outgoing; Thu, 4 Jun 1998 20:06:49 -0700 (PDT)
          (envelope-from owner-cvs-all@FreeBSD.ORG)
Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.15.68.22])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA12544
          for <committers@FreeBSD.ORG>; Thu, 4 Jun 1998 20:06:41 -0700 (PDT)
          (envelope-from bde@godzilla.zeta.org.au)
Received: (from bde@localhost)
	by godzilla.zeta.org.au (8.8.7/8.8.7) id NAA11465;
	Fri, 5 Jun 1998 13:06:35 +1000
Date: Fri, 5 Jun 1998 13:06:35 +1000
From: Bruce Evans <bde@zeta.org.au>
Message-Id: <199806050306.NAA11465@godzilla.zeta.org.au>
To: bde@zeta.org.au, dima@best.net
Subject: Re: FD_SETSIZE
Cc: committers@FreeBSD.ORG
Sender: owner-cvs-all@FreeBSD.ORG
Precedence: bulk

>> The userland change would give incompatible libraries according to
>> `zgrep fd_set /usr/share/man/man3/*'.  This didn't seem to cause any
>> problems in -current when the libc major wasn't bumped, but -stable
>> should be stabler.
>
>Grrr .... Right :-) Most definitely it will break libc_r and librpc
>(at very least).

It's not obvious that it actually breaks things.  It just takes too much
work to verify that it doesn't.  librpc has a variable giving the size
of the descriptor set actually used, and things might work if the old
FD_SETSIZE is not exceeded.  Applications that need the larger size
hopefully use new libraries that give it.

Bruce

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe cvs-all" in the body of the message