From: "J. Bruce Fields" <bfields@fieldses.org>
To: Chuck Lever <chuck.lever@oracle.com>
Cc: Linux NFS Mailing List <nfs@lists.sourceforge.net>
Subject: Re: NFS debugging helpers
Date: Fri, 22 Jun 2007 14:12:29 -0400 [thread overview]
Message-ID: <20070622181229.GB1991@fieldses.org> (raw)
In-Reply-To: <467BFB5D.3040003@oracle.com>
On Fri, Jun 22, 2007 at 12:39:57PM -0400, Chuck Lever wrote:
> J. Bruce Fields wrote:
> >On Thu, Jun 21, 2007 at 04:31:29PM -0400, Chuck Lever wrote:
> >>I thought I remembered that nfs-utils has simple programs to set NFS/RPC
> >>debugging flags, but I couldn't find them.
> >>
> >>So I constructed a couple of Python scripts to remember the flag names
> >>and values (see attached). They are still a little raw.
> >>
> >>Is there anything like this already out there?
> >
> >Try
> >
> > man rpcdebug
> >
> >It comes from nfs-utils/tools/rpcdebug/.
>
> Ja, that's what I remembered.
>
> Not necessarily to Bruce: Is it actively maintained? If a new
> debugging flag is added, is this tool updated by someone?
Sounds like a volunteer!
git hsows the last update (to update some flags, add the manpage, and
install everything) as being by Greg Banks last in July 2006.
I have to admit, just now I needed to turn on some dprintk's, and did it
by looking up the #define by hand. I forgot about rpcdebug even after
having talked about it just yesterday....
--b.
-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
prev parent reply other threads:[~2007-06-22 18:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-21 20:31 NFS debugging helpers Chuck Lever
2007-06-21 20:37 ` J. Bruce Fields
2007-06-22 16:39 ` Chuck Lever
2007-06-22 18:12 ` J. Bruce Fields [this message]
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=20070622181229.GB1991@fieldses.org \
--to=bfields@fieldses.org \
--cc=chuck.lever@oracle.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox