X-Recipient: archive-cygwin AT delorie DOT com
X-Spam-Check-By: sourceware.org
From: "Dave Korn" <dave DOT korn AT artimi DOT com>
To: <cygwin AT cygwin DOT com>
References: <200809251022 DOT 40547 DOT s DOT delhomme AT attitude-studio DOT com>
Subject: RE: socket not closed in a threaded server
Date: Thu, 25 Sep 2008 10:26:33 +0100
Message-ID: <01f501c91ef0$ccb7c630$9601a8c0@CAM.ARTIMI.COM>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 11
In-Reply-To: <200809251022.40547.s.delhomme@attitude-studio.com>
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Precedence: bulk
List-Id: <cygwin.cygwin.com>
List-Unsubscribe: <mailto:cygwin-unsubscribe-archive-cygwin=delorie DOT com AT cygwin DOT com>
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/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
sylvain DELHOMME wrote on 25 September 2008 09:23:
> While playing with sockets and threads, I noticed that while my tcp
> socket is correctly closed, the associated udp socket (managed by Cygwin)
> is not. This was tested with(out) Firewall && Antivirus on 2 WinXP
> computers with cygwin 1.5.25.
>
> Is that a known problem with Cygwin (code is fine under Linux Debian) ?
The "associated udp" socket is an internal thing managed by winsock; it's
standard OS behaviour and happens to native win32 programs as well. It's used
for some kind of internal loopbacky rpc-ish thingy and you can ignore it.
cheers,
DaveK
--
Can't think of a witty .sigline today....
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/