I have a process that sometimes leaves "CLOSE" state connections, as follows:

$ netstat -o -A inet
Proto Recv-Q Send-Q Local Address           Foreign Address         State       Timer
tcp        1  40880 192.168.99.1:1147       feed-udp.rad.dire:33119 CLOSE       on 
(8.83/0)

That connection is hanging around despite the fact that the process that
created it is completely gone (killed), and the process on the remote machine
is also completely gone (killed).  But this "CLOSE" state record seems to hang
around until I reboot.  

Does "CLOSE" state refer to the "CLOSING" state described in Stevens' _UNIX
Network Programming_?

How do I get rid of such a record without rebooting?  (It is just ugly, it
hasn't prevented anything from working (yet))

Dave
-
To unsubscribe from this list: send the line "unsubscribe linux-net" in
the body of a message to [EMAIL PROTECTED]

Reply via email to