All of lore.kernel.org
 help / color / mirror / Atom feed
From: James Pearson <james-p@moving-picture.com>
To: Rik Schneider <riks@wni.com>
Cc: nfs@lists.sourceforge.net
Subject: Re: nfs client monitoring?
Date: Fri, 30 Jul 2004 17:27:05 +0100	[thread overview]
Message-ID: <410A76D9.4040807@moving-picture.com> (raw)
In-Reply-To: <A6BFF93825584E488BCF6A855C1936C001A57198@SUW2CXMAIL.wni.com>

Rik Schneider wrote:
> </lurk>
> 
>> 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/Fedor
> 
> a\
> 
>>/RPMS/xosview-1.8.0-19.i386.rpm
> 
> 
> Could you please provide source or patches for those of us who don't run
> fedora.  Source rpms could also be helpful.

How about:

http://download.fedora.redhat.com/pub/fedora/linux/core/2/i386/os/SRPMS/xosview-1.8.0-19.src.rpm

James Pearson


-------------------------------------------------------
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

  parent reply	other threads:[~2004-07-30 16:27 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-07-30 14:57 nfs client monitoring? Rik Schneider
2004-07-30 16:15 ` Garrick Staples
2004-07-30 16:27 ` James Pearson [this message]
  -- strict thread matches above, loose matches on Subject: below --
2004-07-30 16:44 Rik Schneider
2004-07-29 16:39 Jason Holmes
2004-07-29 18:21 ` seth vidal
2004-07-29 18:25 ` Bernd Schubert
2004-07-30 11:22 ` Steve Dickson

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=410A76D9.4040807@moving-picture.com \
    --to=james-p@moving-picture.com \
    --cc=nfs@lists.sourceforge.net \
    --cc=riks@wni.com \
    /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.