9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: andrey mirtchovski <mirtchov@cpsc.ucalgary.ca>
To: 9fans@cse.psu.edu
Subject: [9fans] lingering network connections
Date: Thu,  8 Apr 2004 09:52:19 -0600	[thread overview]
Message-ID: <7f892fac1c06222c25370acbbffee19e@plan9.ucalgary.ca> (raw)

I have a truckload of network connections lingering from a simple test
I did:


tcp  1467 network    Closed       18001      7664       136.159.7.68
tcp  1468 network    Closed       18001      7665       136.159.7.68
tcp  1469 network    Closed       18001      7666       136.159.7.68
tcp  1470 network    Closed       18001      7777       136.159.7.68
tcp  1471 network    Closed       18001      7778       136.159.7.68
tcp  1472 network    Closed       18001      7779       136.159.7.68
tcp  1473 network    Closed       18001      7780       136.159.7.68
tcp  1474 network    Closed       18001      7781       136.159.7.68
tcp  1475 network    Closed       18001      7805       136.159.7.68
tcp  1476 network    Closed       18001      8208       136.159.7.68
tcp  1477 network    Closed       18001      8232       136.159.7.68
tcp  1478 network    Closed       18001      8233       136.159.7.68
tcp  1479 network    Closed       18001      8274       136.159.7.68
tcp  1480 network    Closed       18001      8438       136.159.7.68
tcp  1481 network    Closed       18001      8439       136.159.7.68


the remote machine has been rebooted long ago, but they still show in
Plan 9.  how do I clean them up?

andrey



             reply	other threads:[~2004-04-08 15:52 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-04-08 15:52 andrey mirtchovski [this message]
2004-04-08 16:41 ` C H Forsyth
2004-04-08 22:00   ` boyd, rounin
2004-04-08 22:12     ` andrey mirtchovski
2004-04-08 22:21       ` Geoff Collyer

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=7f892fac1c06222c25370acbbffee19e@plan9.ucalgary.ca \
    --to=mirtchov@cpsc.ucalgary.ca \
    --cc=9fans@cse.psu.edu \
    /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).