Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
Message-ID: <3D0217D2.9070305@etr-usa.com>
Date: Sat, 08 Jun 2002 08:42:26 -0600
From: Warren Young <warren AT etr-usa DOT com>
Organization: -ENOENT
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.0.0) Gecko/20020530
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Cygwin-L <cygwin AT cygwin DOT com>
Subject: Re: Socket problem
References: <000f01c20ecd$48a6a300$0100a8c0 AT hyperterminal1>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-Note: This E-mail was scanned by Declude JunkMail (www.declude.com) for spam.

DJHyperbyte wrote:
> ESTABLISHED
> TIME_WAIT
> TIME_WAIT
> (IP's left out for privacy protection)
> 
> As you can see, there are a lot of sockets which aren't killed properly, and

TIME_WAIT is a feature, and tricking Winsock into avoiding it is a bug. 
  See the "Debugging TCP" article in my FAQ for details:
-- 
= Winsock Programmer's FAQ: http://tangentsoft.net/wskfaq/


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/