From: "G. Allen Morris III" <gam3-nfs@gam3.net>
To: nfs@lists.sourceforge.net
Subject: Re: /proc/fs/nfs/exports Broken
Date: Sun, 6 Mar 2005 15:30:43 -0500 [thread overview]
Message-ID: <20050306203043.GA5529@gam3.net> (raw)
In-Reply-To: <20050306173628.GA3918@gam3.net>
On Sun, Mar 06, 2005 at 12:36:28PM -0500, G. Allen Morris III wrote:
> Neil,
>
> Neil the net rcp export cache should not be used directly for
> the /proc/nfs/exports output.
>
> I am pretty sure that all that needs to be done is to only display
> the rightmost element of the domain (client = strrchr(domain, ',')+1).
>
> I have a patch, but plan to clean it up before I send it to you.
>
> I just wanted to request comments on this problem for now.
I can see that I am very wrong about how simple this is. I think that
extra data or code is needed to solve this problem.
Here are some questions:
1. do we need nfsd/exports at all? (No ones seems to have noticed that
the information it gives is not very human readable.)
2. If yes. What is it for? It seems to me it is needed to show what
export a given IP is mapped to.
3. Should exportfs have a switch that to display the kernel export
cache is some nice format or formats.
Allen Morris <gam3@gam3.net>
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
next prev parent reply other threads:[~2005-03-06 20:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-06 16:40 Segfault in mountd -- fixed G. Allen Morris III
2005-03-06 17:36 ` /proc/fs/nfs/exports Broken G. Allen Morris III
2005-03-06 20:30 ` G. Allen Morris III [this message]
2005-03-06 23:24 ` Neil Brown
2005-03-18 13:55 ` Making /proc/fs/nfs/exports human friendly G. Allen Morris III
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=20050306203043.GA5529@gam3.net \
--to=gam3-nfs@gam3.net \
--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.