http://bugs.winehq.org/show_bug.cgi?id=14159
Juan Lang juan_lang@yahoo.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED Resolution| |INVALID
--- Comment #1 from Juan Lang juan_lang@yahoo.com 2008-06-28 12:15:57 --- This is due to the close timeout implement by the Linux kernel: once a socket is closed, it remains in the TIME_WAIT state until the timer expires, even if the process that created it has quit. Windows makes the port immediately available.
I don't think we can do much about this one since it's in the kernel. You can take it up with the kernel devs if you like.