From: Gabriel Barazer <gabriel@oxeva.fr>
To: Jordi Prats <jprats@cesca.es>
Cc: nfs@lists.sourceforge.net
Subject: Re: about /proc/net/rpc/nfsd
Date: Tue, 23 Oct 2007 00:02:26 +0200 [thread overview]
Message-ID: <471D1DF2.4070201@oxeva.fr> (raw)
In-Reply-To: <471D17F8.5060709@cesca.es>
On 10/22/2007 11:36:56 PM +0200, Jordi Prats <jprats@cesca.es> wrote:
> Hi all,
> I've been researching the meaning of the contents of the
> /proc/net/rpc/nfsd file using the 2.6.23 kernel sources.
>
>
> Sorry for this so long mail... That's all what I've got reading the
> source files. There's anything incorrect? There's some "educated guests"
> So, could anyone please confirm or refute them?
>
> If you what me to do something with this I'd be glad of it!
Wow this is an awesome job you've done here to document precisely this
proc file. I've tagged your mail and copied it in a safe place. I'm
sure this would be very useful to keep a place where all these proc
files are explained like this, maybe on the linux-nfs wiki ?
Great job Jordi !
Gabriel
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
next prev parent reply other threads:[~2007-10-22 22:02 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-22 21:36 about /proc/net/rpc/nfsd Jordi Prats
2007-10-22 21:54 ` Jordi Prats
2007-10-22 22:02 ` Gabriel Barazer [this message]
2007-10-23 15:07 ` Chuck Lever
2007-10-23 17:00 ` Jordi Prats
2007-10-23 18:09 ` Chuck Lever
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=471D1DF2.4070201@oxeva.fr \
--to=gabriel@oxeva.fr \
--cc=jprats@cesca.es \
--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