This is the mail archive of the cygwin-developers@cygwin.com mailing list for the Cygwin project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: TCP problems

From: "Pierre A. Humblet" <Pierre dot Humblet at ieee dot org>
To: Conrad Scott <Conrad dot Scott at dsl dot pipex dot com>
Cc: cygwin-developers at cygwin dot com
Date: Mon, 29 Jul 2002 15:07:03 -0400
Subject: Re: TCP problems
References: <010901c23724$96e5d430$6132bc3e@BABEL> <3D4581E4.BB580995@ieee.org> <005801c23730$02304170$6132bc3e@BABEL>

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

Follow-Ups:
- Re: TCP problems
  - From: Conrad Scott

References:
- TCP problems
  - From: Conrad Scott
- Re: TCP problems
  - From: Pierre A. Humblet
- Re: TCP problems
  - From: Conrad Scott

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]