Killing Sockets

I'm working on a Python app that creates a tcp socket and listens on a
port. Sometimes I've found that after I've killed the process, the
socket still remains. When I did a netstat -t, I saw that the socket
is still in the fin-wait-1 state. When I did a ps -ef, I couldn't see
any process still alive that the socket was attached to.

Is there some way to kill the socket is this instance? Being in
fin-wait, it eventually kills itself, but I couldn't restart the
Python app until it had done so.

Dan

Dan wrote:
> I'm working on a Python app that creates a tcp socket and listens on
a
> port. Sometimes I've found that after I've killed the process, the
> socket still remains. When I did a netstat -t, I saw that the socket
> is still in the fin-wait-1 state. When I did a ps -ef, I couldn't
see
> any process still alive that the socket was attached to.
>
> Is there some way to kill the socket is this instance? Being in
> fin-wait, it eventually kills itself, but I couldn't restart the
> Python app until it had done so.

Not being sure of the context or nature of your $ kill (or the Python
app) I'll just point you here:

http://groups-beta.google.com/group/...&q=kill+socket

hth,
prg

Hi,

You could try setting REUSEADDR on the socket within your application.
That should allow a second instance of the server to bind to the port
even while the old one is still hanging around.

GSF