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:	<000f01c20ecd$48a6a300$0100a8c0@hyperterminal1>
From:	"DJHyperbyte" <djhyperbyte AT masternap DOT net>
To:	<cygwin AT cygwin DOT com>
Subject:	Socket problem
Date:	Sat, 8 Jun 2002 11:17:15 +0200
MIME-Version:	1.0
X-Priority:	3
X-MSMail-Priority:	Normal
X-MimeOLE:	Produced By Microsoft MimeOLE V6.00.2600.0000

As some of you may know, there is an Open Source Napster Server (opennap),
which is written in ANSI C.

This server used to work fine, when compiled with older versions of CygWin,
however, with the newer versions I noticed that it doesn't kill sockets very
well anymore.

netstat -n looks like this:
TIME_WAIT
ESTABLISHED
TIME_WAIT
TIME_WAIT
TIME_WAIT
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
I am sure that this is because of the newer version of CygWin, because it
used to work fine without any problems.

My question is, does anyone know if anything changed in the way CygWin
handles sockets?
(yes, I did read the changelog...and stuff)

Sincerely,
DJHyperbyte (MasterNap Network Owner)
http://www.masternap.net



--
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/

- Raw text -