[Bug 26031]=?UTF-8?Q?=20=C2=B5Torrent=20loses=20the=20ability=20of=20listening=20to=20incoming=20connections?=

http://bugs.winehq.org/show_bug.cgi?id=26031

--- Comment #31 from Bruno Jesus  2012-08-08 08:44:51 CDT ---
(In reply to comment #29)
> All I can say is "WTF. Seriously?"

Well, as I said before it may be a TCP implementation characteristic. You can
look for what TCP TIME_WAIT state means.
http://www.unixguide.net/network/socketfaq/2.7.shtml
http://serverfault.com/questions/329845/how-to-forcibly-close-a-socket-in-ti...

IMO uTorrent should be smarter and try to bind from time to time, maybe it does
that in newer versions.

I'll dig further in the next week. The question is why SO_REUSEADDR is failing
when it's supposed to jump the TIME_WAIT.