From: Markus Kolb <usenet@tower-net.de>
To: linux-kernel@vger.kernel.org
Subject: tcp socks at close_wait for days without process
Date: Mon, 29 Dec 2003 16:17:24 +0100 [thread overview]
Message-ID: <3FF04584.9010606@tower-net.de> (raw)
Hello,
I have a problem with this close_wait state in tcp connections.
There is no process left in the process list which could belong to the
specific port.
It is known that the application has bugs, but shouldn't the Linux
kernel manage this close_wait state and free the port after a while?
I believe I could wait for months and years and the close_wait won't go
away without a reboot.
At the moment I am using a Debian kernel-image 2.4.22-1.
But with older Debian kernel-images and SuSE images (I think I have also
tried a 2.4 vanilla) you can watch this behavior, too.
I have watched a 2nd strange kernel behavior. For that I don't know how
to reproduce.
A server application listened at a specific port. The application
crashed and no process belonging to this application was in process list
anymore. But the listening socket alives for about 5 minutes although
there was no process. How this can be? A listening port without a daemon
process belonging to it?
After the 5 minutes I have rebooted.
Am I wrong about the possibilities of the kernel?
Bye
Markus
next reply other threads:[~2003-12-29 15:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-29 15:17 Markus Kolb [this message]
2003-12-30 11:52 ` tcp socks at close_wait for days without process Mihai RUSU
[not found] <fa.elrs5lj.1n4inbv@ifi.uio.no>
[not found] ` <fa.pbs8b1q.1i5g1g8@ifi.uio.no>
2004-01-01 22:17 ` Markus Kolb
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=3FF04584.9010606@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