All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jason Baietto <jason.baietto@ccur.com>
To: lkml <linux-kernel@vger.kernel.org>
Subject: 2.4.18+O(1) tcp timewait zombies
Date: 03 May 2002 10:53:57 -0400	[thread overview]
Message-ID: <1020437642.28612.55.camel@soybean> (raw)

Hi all,

After upgrading from stock 2.4.17 to 2.4.18 (with O(1) scheduler
patch) I'm seeing some strange networking behavior.  Basically,
upon exit rsh connections seem to go into TIME_WAIT, count down
to zero, and then stick around forever.  For example:

   compy$ rsh hyena echo hello < /dev/null
   hello
   compy$

This leaves a socket connnection in TIME_WAIT state:

   tcp        ...         TIME_WAIT   timewait (51.75/0/0)

However, the strange thing is that after the connection times
out, it sticks around.  I've got hundreds of these connections
open that look like this:

   tcp        ...         TIME_WAIT   timewait (0.00/0/0)

And never seem to go away.  Eventually, this causes me to
get this message whenever I try to do an new rsh:

   socket: All ports in use

Can anyone offer me any advice on how to debug this?

Take care,
Jason
--
Jason Baietto
jason.baietto@ccur.com



                 reply	other threads:[~2002-05-03 14:54 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=1020437642.28612.55.camel@soybean \
    --to=jason.baietto@ccur.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.