From owner-freebsd-hackers Fri Feb 21 22:01:25 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id WAA23868 for hackers-outgoing; Fri, 21 Feb 1997 22:01:25 -0800 (PST) Received: from hydrogen.nike.efn.org (metriclient-9.uoregon.edu [128.223.172.9]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id WAA23862 for ; Fri, 21 Feb 1997 22:01:15 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by hydrogen.nike.efn.org (8.8.4/8.8.4) with SMTP id WAA08517; Fri, 21 Feb 1997 22:01:01 -0800 (PST) Date: Fri, 21 Feb 1997 22:01:01 -0800 (PST) From: John-Mark Gurney Reply-To: John-Mark Gurney To: Guido van Rooij cc: FreeBSD-hackers Subject: Re: FD_SETSIZE In-Reply-To: <199702212239.XAA10384@gvr.win.tue.nl> Message-ID: X-PGP-Fingerprint: B7 EC EF F8 AE ED A7 31 96 7A 22 B3 D8 56 36 F4 MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Fri, 21 Feb 1997, Guido van Rooij wrote: > Can someone explain me the way to deal with FD_SETSIZE nowadays? > From looking at the sources it seems that the kernel is not limited > by whatever FD_SETSIZE is defined to. Is that correct? yes... the kernel doesn't have a limit on FD_SETSIZE... > Further, there is a comment on the new FD_SETSIZE being 1024 where > I still see FD_SETSIZE set to 256 in sys/types.h. Am I missing > something? yes... that is because FD_SETSIZE was (is it still?) being used as a "multiple" to decide how many bits to allocate/use... to increase the size of FD_SETSIZE simply define it to a new value before you include sys/types.h... then simply limit yourself to the new limit :)... hope this helps... ttyl... John-Mark gurney_j@efn.org http://resnet.uoregon.edu/~gurney_j/ Modem/FAX: (541) 683-6954 (FreeBSD Box) Live in Peace, destroy Micro$oft, support free software, run FreeBSD (unix)