getting socket.bind() exception, but no actual error

Clarence Gardner clarence at silcom.com
Wed Nov 3 08:34:10 CET 2004


mfuhr at fuhr.org (Michael Fuhr) wrote in message news:<4187d4fc$1_4 at omega.dimensional.com>...
?  Because you get "Address already in use" exceptions due
> to old connections still being in the TIME_WAIT state?  If so, are
> you aware that server processes should usually set the SO_REUSEADDR
> socket option before calling bind()?  Or is there some other reason
> that bind() fails?

No, that's the only issue. I thought using that option was frowned upon,
but it's also been a couple of years since I needed to think about such
things, and I was too lazy to look it up for now.



More information about the Python-list mailing list