public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Dan Kegel <dank@kegel.com>
To: darx_kies@gmx.net,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: re: CLOSE_WAIT Problem
Date: Fri, 29 Jun 2001 10:55:29 -0700	[thread overview]
Message-ID: <3B3CC111.5F53C7CD@kegel.com> (raw)

Chriss wrote:
> 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?

Dunno if this will help, but:

They're supposed to go away by themselves after 2MSL (about 120 seconds).
Other people (on many operating systems) have reported similar problems, btw:

http://uwsg.iu.edu/hypermail/linux/net/9611.2/0043.html
http://www.sunmanagers.org/pipermail/sunmanagers/2001-April/002894.html
http://www2.real-time.com/tclug-list/1999/Jun/msg00254.html
http://mail-index.netbsd.org/netbsd-bugs/1996/04/16/0004.html

The last one has a fix for an old bug in netbsd that could cause this.
- Dan

             reply	other threads:[~2001-06-29 17:53 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-06-29 17:55 Dan Kegel [this message]
  -- strict thread matches above, loose matches on Subject: below --
2001-06-29 13:45 CLOSE_WAIT Problem darx kies

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=3B3CC111.5F53C7CD@kegel.com \
    --to=dank@kegel.com \
    --cc=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