public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: DervishD <raul@pleyades.net>
To: "Måns Rullgård" <mru@kth.se>
Cc: linux-kernel@vger.kernel.org
Subject: Re: The dreadful CLOSE_WAIT
Date: Tue, 27 Jul 2004 11:57:51 +0200	[thread overview]
Message-ID: <20040727095751.GA10048@DervishD> (raw)
In-Reply-To: <yw1xllh5ol3i.fsf@kth.se>

    Hi Måns :)

 * Måns Rullgård <mru@kth.se> dixit:
> >     Seems under Linux that, when a connection is in the CLOSE_WAIT
> > state, the only wait to go to LAST_ACK is the application doing the
> > 'shutdown()' or 'close()'. Doesn't seem to be a timeout for that.
> Is that why some programs seem to hang forever when my NAT gateway
> decides to drop a connection?

    I don't know. Look at the output of your netstat command. If you
have connections in the CLOSE_WAIT state related to the NAT gateway,
it may be the cause :? But anyway the effect is just the opposite. Is
not CLOSE_WAIT state that hangs a program, but a hung program (or at
least one not doing its duty) which puts a connection in CLOSE_WAIT
state.

    Hope this helps.

    Raúl Núñez de Arenas Coronado

-- 
Linux Registered User 88736
http://www.pleyades.net & http://raul.pleyades.net/

  reply	other threads:[~2004-07-27  9:57 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-07-27  8:39 The dreadful CLOSE_WAIT DervishD
2004-07-27  9:28 ` Måns Rullgård
2004-07-27  9:57   ` DervishD [this message]
2004-07-27 16:00 ` William Lee Irwin III
2004-07-27 17:10   ` DervishD
2004-07-27 23:27     ` William Lee Irwin III
2004-07-28  9:09       ` DervishD
2004-07-28  9:24         ` William Lee Irwin III
2004-07-27 16:45 ` Mike Waychison
2004-07-27 17:09   ` DervishD
     [not found]     ` <20040728140622.2bc69fa5@kingfisher.intern.logi-track.com>
2004-07-28 14:47       ` DervishD
2004-07-29  9:46         ` Markus Schaber

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=20040727095751.GA10048@DervishD \
    --to=raul@pleyades.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mru@kth.se \
    /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