Mailing-List: contact cygwin-developers-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-developers-owner AT cygwin DOT com Delivered-To: mailing list cygwin-developers AT cygwin DOT com Message-ID: <009c01c23736$4a61a4b0$6132bc3e@BABEL> From: "Conrad Scott" To: "Pierre A. Humblet" Cc: References: <010901c23724$96e5d430$6132bc3e AT BABEL> <3D4581E4 DOT BB580995 AT ieee DOT org> <005801c23730$02304170$6132bc3e AT BABEL> <3D459257 DOT 240C79DC AT ieee DOT org> Subject: Re: TCP problems Date: Mon, 29 Jul 2002 20:29:42 +0100 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 "Pierre A. Humblet" wrote: > Conrad Scott wrote: > > Sorry: I should have been clearer there. No: my test cygwin > > server doesn't duplicate any of its sockets (AFAICT etc. but I'm > > pretty sure). > > Just to make sure I understand: it NEVER forks. Correct? Never. Ever ever. Ever. Not even once. > > It's a really simple server: blocking accept, > > read/write on the new file descriptor, then shutdown/close it and > > back to a blocking accept. And it still hits the WASENOBUFS wall > > eventually (altho' it can be delayed by registry patches to > > increase various TCP parameters). > > How long/how many accepts (more or less) is "eventually". On my lovely little win98/SE box: one hundred connections minus a few. Nicholas Wourms (my (un)willing test accomplice) reported "~3 minutes" of run time before hitting the same error: so he's getting a thousand or so (?) connections by the sounds of it. // Conrad