Re: tcp socks at close_wait for days without process

[Markus Kolb]

Mihai RUSU wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> On Mon, 29 Dec 2003, Markus Kolb wrote:
[...]
> netstat -an | grep CLOSE_WAIT
> fuser -n tcp <localport>,<remote-addr>,<remote-port>
> where <localport>, <remote-addr>, <remote-port> you take them from the 
> netstat output. fuser should give you the PID of the owner of the sockets 
> in CLOSE_WAIT. kill it and they should dissapear.

Well the process list has been very short. So I am pretty sure that 
there hasn't been any processes from the application.
Could it be that the socket which first belongs to the crashed 
application is bound to the father process of this crashed application?
This would be a bash or init.

Thanks for the hint with fuser.
Before the next reboot I will try to reproduce and will use the fuser 
command to see more details.

Bye

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/