From: Steve Dickson <SteveD@redhat.com>
To: Jason Holmes <jholmes@psu.edu>
Cc: nfs@lists.sourceforge.net
Subject: Re: nfs client monitoring?
Date: Fri, 30 Jul 2004 07:22:50 -0400 [thread overview]
Message-ID: <410A2F8A.4030307@RedHat.com> (raw)
In-Reply-To: <41092832.3030400@psu.edu>
Jason Holmes wrote:
> Is there a command that can show the demands being placed on the nfs
> server by each individual client? I run into the situation from time
> to time where a random user will do something that puts an extreme
> load on the fileserver and having such a command would help greatly in
> trying to figure out the source of the load.
I've recently added some hooks to xosview that will graphically
show NFS and kNFSD traffic which I find pretty handy....
http://download.fedora.redhat.com/pub/fedora/linux/core/2/i386/os/Fedora/RPMS/xosview-1.8.0-19.i386.rpm
SteveD.
-------------------------------------------------------
This SF.Net email is sponsored by OSTG. Have you noticed the changes on
Linux.com, ITManagersJournal and NewsForge in the past few weeks? Now,
one more big change to announce. We are now OSTG- Open Source Technology
Group. Come see the changes on the new OSTG site. www.ostg.com
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
next prev parent reply other threads:[~2004-07-30 11:23 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-29 16:39 nfs client monitoring? Jason Holmes
2004-07-29 18:21 ` seth vidal
2004-07-29 18:25 ` Bernd Schubert
2004-07-30 11:22 ` Steve Dickson [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-07-30 14:57 Rik Schneider
2004-07-30 16:15 ` Garrick Staples
2004-07-30 16:27 ` James Pearson
2004-07-30 16:44 Rik Schneider
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=410A2F8A.4030307@RedHat.com \
--to=steved@redhat.com \
--cc=jholmes@psu.edu \
--cc=nfs@lists.sourceforge.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 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.