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/
