Mailing-List: contact cygwin-developers-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-developers-subscribe AT cygwin DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin-developers/>
List-Post: <mailto:cygwin-developers AT cygwin DOT com>
List-Help: <mailto:cygwin-developers-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-developers-owner AT cygwin DOT com
Delivered-To: mailing list cygwin-developers AT cygwin DOT com
Message-ID: <3D459257.240C79DC@ieee.org>
Date: Mon, 29 Jul 2002 15:07:03 -0400
From: "Pierre A. Humblet" <Pierre DOT Humblet AT ieee DOT org>
X-Accept-Language: en,pdf
MIME-Version: 1.0
To: Conrad Scott <Conrad DOT Scott AT dsl DOT pipex DOT com>
CC: cygwin-developers AT cygwin DOT com
Subject: Re: TCP problems
References: <010901c23724$96e5d430$6132bc3e AT BABEL> <3D4581E4 DOT BB580995 AT ieee DOT org> <005801c23730$02304170$6132bc3e AT BABEL>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

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?

> 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".

Pierre