X-Recipient: archive-cygwin AT delorie DOT com X-Spam-Check-By: sourceware.org From: Sylvain Delhomme To: cygwin AT cygwin DOT com Subject: Re: socket not closed in a threaded server Date: Thu, 25 Sep 2008 14:56:58 +0200 User-Agent: KMail/1.9.9 References: <200809251022 DOT 40547 DOT s DOT delhomme AT attitude-studio DOT com> <01f501c91ef0$ccb7c630$9601a8c0 AT CAM DOT ARTIMI DOT COM> In-Reply-To: <01f501c91ef0$ccb7c630$9601a8c0@CAM.ARTIMI.COM> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200809251456.58483.s.delhomme@attitude-studio.com> X-IsSubscribed: yes Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com > The "associated udp" socket is an internal thing managed by winsock; it's >standard OS behaviour and happens to native win32 programs as well. I've just ported my small app to Winsock and I did not see this. > It's > used for some kind of internal loopbacky rpc-ish thingy and you can ignore > it. > Could you provide me more info about this because it can be quite annoying in a real application ? -- 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/