[lkml]   [2004]   [Jan]   [1]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: tcp socks at close_wait for days without process
Mihai RUSU wrote:
> 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.


To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

 \ /
  Last update: 2005-03-22 13:59    [W:0.032 / U:7.420 seconds]
©2003-2018 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site