9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: lucio@proxima.alt.za
To: 9fans@9fans.net
Subject: [9fans] Cleaning up the IP tables
Date: Sat, 26 Jun 2010 18:20:45 +0200	[thread overview]
Message-ID: <f5b4946199ebdf680c7eb307eb117ce1@proxima.alt.za> (raw)

I'm not sure how long it's been building up, but there are more than
4000 "Closed" TCP connections on a web accessible Plan 9 server,
according to netstat.  Is there a simple way to clean up and delete
all these entries or does one have to do something dramatic?  I can't
drop the network, the server is a long way from here :-)

I don't like rebooting, but I don't like 4000-odd netstat entries
either.

Hm, many are local "ticket" connections, you'd think they'd go away
once dealt with.  The kernel is a little less than two years old, I'll
have to consider an upgrade.

++L




             reply	other threads:[~2010-06-26 16:20 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-26 16:20 lucio [this message]
2010-06-26 17:14 ` erik quanstrom
2010-06-26 18:03   ` andrey mirtchovski
2010-06-27  1:10     ` erik quanstrom
2010-06-28 16:36 ` Lyndon Nerenberg

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=f5b4946199ebdf680c7eb307eb117ce1@proxima.alt.za \
    --to=lucio@proxima.alt.za \
    --cc=9fans@9fans.net \
    /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;
as well as URLs for NNTP newsgroup(s).