All of lore.kernel.org
 help / color / mirror / Atom feed
From: Erik Walthinsen <omega@pdxcolo.net>
To: Garrick Staples <garrick@usc.edu>
Cc: nfs@lists.sourceforge.net
Subject: Re: Converting open filehandles to pathnames
Date: Sun, 09 May 2004 14:11:30 -0700	[thread overview]
Message-ID: <1084137085.715.26.camel@omikron> (raw)
In-Reply-To: <20040510030029.GL30964@polop.usc.edu>

On Sun, 2004-05-09 at 20:00, Garrick Staples wrote:
> > 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.
> 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.

Sure.  In its current incarnation it's a Python script using a pcap
module I found in some package that I can no longer identify....  It's
also quite tied to my current file structure, though some of that also
has to do with the earlier assumptions I made about filehandles.

The biggest challenge for general usage is the inode -> pathname
translation.  In my case there are currently about 900 files I can look
up before the packet capture starts, and cache those inode numbers.  A
general utility will require a different solution, starting with the
existing method of snooping getattr and other calls.  Any other
suggestions on how I can generically convert inodes to pathnames without
massive overhead?

Once I have my current code doing what I want I'll clean it up and post
it here so it can be hacked into a useful tool.



-------------------------------------------------------
This SF.Net email is sponsored by Sleepycat Software
Learn developer strategies Cisco, Motorola, Ericsson & Lucent use to deliver
higher performing products faster, at low TCO.
http://www.sleepycat.com/telcomwpreg.php?From=osdnemail3
_______________________________________________
NFS maillist  -  NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs

  reply	other threads:[~2004-05-10  4:31 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
2004-05-09 21:11         ` Erik Walthinsen [this message]
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=1084137085.715.26.camel@omikron \
    --to=omega@pdxcolo.net \
    --cc=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.