From: Markus Kolb <usenet@tower-net.de>
To: linux-kernel@vger.kernel.org
Subject: Re: tcp socks at close_wait for days without process
Date: Thu, 01 Jan 2004 23:17:01 +0100 [thread overview]
Message-ID: <3FF49C5D.8050003@tower-net.de> (raw)
In-Reply-To: <fa.pbs8b1q.1i5g1g8@ifi.uio.no>
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
next parent reply other threads:[~2004-01-01 22:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <fa.elrs5lj.1n4inbv@ifi.uio.no>
[not found] ` <fa.pbs8b1q.1i5g1g8@ifi.uio.no>
2004-01-01 22:17 ` Markus Kolb [this message]
2003-12-29 15:17 tcp socks at close_wait for days without process Markus Kolb
2003-12-30 11:52 ` Mihai RUSU
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3FF49C5D.8050003@tower-net.de \
--to=usenet@tower-net.de \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox