From: "darx kies" <darx_kies@gmx.net>
To: "linux kernel" <linux-kernel@vger.kernel.org>
Subject: CLOSE_WAIT Problem
Date: Fri, 29 Jun 2001 15:45:28 +0200 [thread overview]
Message-ID: <013101c100a1$c2bebfa0$f216e5d5@lilly> (raw)
Hi.
I wrote a simple server application and installed it on a linux machine
in Slovakia, running Mandrake 7.2 (2.2.18).
That machine loses tcp/ip packages, as it uses a Microwave connection.
So my server works all the time, and the tcp/ip connections are set to
TIME_WAIT, but after a couple of hours
my server application won't get any connections anymore and the netstat
shows a lot of CLOSE_WAITs that belong to the server.
I've installed the same server on two SuSE 7.1 (2.2.18) machines in
Austria, and the problem never occured.
So does anyone know how to avoid that CLOSE_WAITs, or at least how to
get rid of them?
Thanks in advance.
Chriss.
----------
The last good thing written in C was Schubert's Symphony No. 9.
next reply other threads:[~2001-06-29 13:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-06-29 13:45 darx kies [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-06-29 17:55 CLOSE_WAIT Problem Dan Kegel
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='013101c100a1$c2bebfa0$f216e5d5@lilly' \
--to=darx_kies@gmx.net \
--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