From: Garrick Staples <garrick@usc.edu>
To: nfs@lists.sourceforge.net
Subject: Re: Converting open filehandles to pathnames
Date: Sun, 9 May 2004 20:00:30 -0700 [thread overview]
Message-ID: <20040510030029.GL30964@polop.usc.edu> (raw)
In-Reply-To: <1084148814.29382.32.camel@binkley>
[-- Attachment #1: Type: text/plain, Size: 910 bytes --]
On Sun, May 09, 2004 at 08:26:54PM -0400, seth vidal alleged:
>
> > Now if someone just had as good an answer to the "what is a client?"
> > question.... You might imagine my interest in that is more than
> > academic, with 100's of *long*-duration filehandles in the GB+ range
> > each, yet over only a few physical client machines.
> >
>
> Any thoughts to making this program available anywhere? I'd be
> interested to get some mappings to find out who my most abusive users
> are.
>
> I've run into some performance problems recently and I'd love to know if
> I've got some specific users who are being abusive or if the machine is
> just underpowered.
Come to think of it, I've found myself in the same situation... wondering who
is beating up my NFS servers. This would be a great tool to have.
--
Garrick Staples, Linux/HPCC Administrator
University of Southern California
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2004-05-10 3:02 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-08 23:33 Converting open filehandles to pathnames Erik Walthinsen
2004-05-09 7:24 ` Greg Banks
2004-05-09 0:43 ` Erik Walthinsen
2004-05-10 0:26 ` seth vidal
2004-05-10 3:00 ` Garrick Staples [this message]
2004-05-09 21:11 ` Erik Walthinsen
2004-05-10 8:02 ` Bogdan Costescu
2004-05-10 14:20 ` Erik Walthinsen
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=20040510030029.GL30964@polop.usc.edu \
--to=garrick@usc.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.