From: David Presotto <presotto@closedmind.org>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] killing rogue processes
Date: Thu, 18 Dec 2003 22:07:30 -0500 [thread overview]
Message-ID: <c8008711d3343902696670353c4f1b90@plan9.bell-labs.com> (raw)
In-Reply-To: <a8176ec3da9468ed7d247001954d2e44@plan9.ucalgary.ca>
[-- Attachment #1: Type: text/plain, Size: 28 bytes --]
I updated lsof.c to sources.
[-- Attachment #2: Type: message/rfc822, Size: 2306 bytes --]
From: mirtchov@cpsc.ucalgary.ca
To: 9fans@cse.psu.edu
Subject: Re: [9fans] killing rogue processes
Date: Thu, 18 Dec 2003 13:29:34 -0700
Message-ID: <a8176ec3da9468ed7d247001954d2e44@plan9.ucalgary.ca>
>> I have an 'lsof' that lists all file descriptors + process #s.. just
> grepping for 'tcp'
>> gave me the clues...
>
> you ported that to plan 9?
no, I wrote my own:
octarine% wc -l $home/kern/cmd/lsof.c
89 /usr/andrey/kern/cmd/lsof.c
octarine%
there's also top. for now it is a perl script, but I have been
thinking of ways to make it look like stats a bit more (how would you
represent different chunks of processor time? pie chart?), it's
another 45 lines of code and actually that's what helped me find what
was causing all the load on the system.
next prev parent reply other threads:[~2003-12-19 3:07 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-18 17:42 mirtchov
2003-12-18 16:57 ` Russ Cox
2003-12-18 18:28 ` andrey mirtchovski
2003-12-18 19:50 ` David Presotto
2003-12-18 20:01 ` mirtchov
2003-12-18 19:13 ` Russ Cox
2003-12-19 14:31 ` mirtchov
2003-12-18 22:31 ` Russ Cox
2003-12-19 17:20 ` ron minnich
2003-12-20 9:01 ` boyd, rounin
2003-12-19 17:25 ` mirtchov
2003-12-19 6:19 ` boyd, rounin
2003-12-18 20:29 ` mirtchov
2003-12-18 20:41 ` Scott Schwartz
2003-12-18 20:48 ` mirtchov
2003-12-19 3:07 ` David Presotto [this message]
2003-12-19 6:45 ` boyd, rounin
2003-12-19 5:57 ` boyd, rounin
2003-12-19 0:03 ` Bruce Ellis
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=c8008711d3343902696670353c4f1b90@plan9.bell-labs.com \
--to=presotto@closedmind.org \
--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).