Mailing-List: contact cygwin-help@sourceware.cygnus.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@sourceware.cygnus.com Delivered-To: mailing list cygwin@sourceware.cygnus.com Date: Mon, 6 Dec 1999 16:48:43 -0500 From: Chris Faylor To: Mumit Khan , stefan , cygwin@sourceware.cygnus.com Subject: Re: More than 64 sockets ? Message-ID: <19991206164843.B9747@cygnus.com> Mail-Followup-To: Mumit Khan , stefan , cygwin@sourceware.cygnus.com References: <199912061554.JAA15146@hp2.xraylith.wisc.edu> <19991206161728.C2223@cygnus.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <19991206161728.C2223@cygnus.com>; from cgf@cygnus.com on Mon, Dec 06, 1999 at 04:17:28PM -0500 On Mon, Dec 06, 1999 at 04:17:28PM -0500, Chris Faylor wrote: >On Mon, Dec 06, 1999 at 09:54:39AM -0600, Mumit Khan wrote: >>stefan writes: >>> Hello, >>> >>> we were porting a server software to Win9x/NT and had to notice that you >>> cannot accept() more than 64 sockets. Why is this ? Can anyone help us ? >> >>The underlying OS API, WaitForMultipleObjects, has a limit of 64 handles >>it can wait on, and that's probably the reason. There are tricks to get >>around it, but it requires creating multiple threads. Not pretty. > >This isn't a problem with cygwin. Cygwin uses the Winsock select() for >sockets. There probably is a limit there but it's not 64. Just to clarify: The "This" above refers to the WaitForMultipleObjects limit of 64 handles. This particular hard limit probably does not affect cygwin. There is a hard-coded limit in winsock.h which is probably what is coming to play here. cgf -- Want to unsubscribe from this list? Send a message to cygwin-unsubscribe@sourceware.cygnus.com