Re: Problem with sockets

J. Sean Connell (ankh@canuck.gen.nz)
Wed, 4 Dec 1996 10:52:41 +1300 (NZDT)


On Tue, 3 Dec 1996, Oliver Elphick wrote:

> I came across this problem while trying to get INN to work.
> [problem and source snipped]

This has been around for as long as I can recall. From inspection, Linux
won't let you bind to that address again because the socket is stuck in one of
the terminal states (FIN1? 2? CLOSING? I forget...) for 60 (or is it 62?)
after your app closes the socket. It makes debugging socket-based
applications really annoying :)

So what gives? Neither Solaris nor SunOS (the two other OSes I have to use at
work) behave in this fashion...

--
Jeffrey Connell            | Systems Adminstrator, ICONZ
ankh@canuck.gen.nz         | Any opinions stated above are not my employers',
ankh@iconz.co.nz           | not my boyfriend's, my priest's, my God's, my
#include <stddisc.h>       | my friends', and probably not even my own.
---------------------------+--------------------------------------------------
Fingerprint: 1024/2B8B116D | Key at http://www.canuck.gen.nz/~ankh/pgpkey.html