From: "J. Bruce Fields" <bfields@fieldses.org>
To: James Pearson <james-p@moving-picture.com>
Cc: linux-nfs@vger.kernel.org
Subject: Re: How to control the order of different export options for different client formats?
Date: Fri, 20 May 2011 12:41:47 -0400 [thread overview]
Message-ID: <20110520164147.GA11176@fieldses.org> (raw)
In-Reply-To: <4DD66EC6.7090706@moving-picture.com>
On Fri, May 20, 2011 at 02:38:14PM +0100, James Pearson wrote:
> J. Bruce Fields wrote:
> >>Having a priority option would be a very good idea - and may be in
> >>the meantime the exports man page should be updated with info about
> >>the current priority ordering?
> >
> >
> >Sounds good. Could you send in a patch?
>
> Here's an attempt - based on the info from Max Matveev
> <makc@redhat.com> earlier in this thread
>
> James Pearson
>
> --- exports.man.dist 2010-09-28 13:24:16.000000000 +0100
> +++ exports.man 2011-05-20 14:29:45.555314605 +0100
> @@ -92,6 +92,11 @@
> '''.B \-\-public\-root
> '''option. Multiple specifications of a public root will be ignored.
> .PP
> +.SS Matched Client Priories
Priorities?
But could we just combine this with the previous section--and make sure
the different possibilities are listed there in the correct priority
order to start off with.
That'd also mean adding a new subsection for the "anonymous" case.
--b.
> +The order in which the different \fIMachine Name Formats\fR are matched
> +against clients is in the priority order: \fIhostname, IP address
> or networks,
> +wildcards, netgroup and anonymous\fR. Entries at the same level are matched
> +in the same order in which they appear in \fI/etc/exports\fR.
> .SS RPCSEC_GSS security
> You may use the special strings "gss/krb5", "gss/krb5i", or "gss/krb5p"
> to restrict access to clients using rpcsec_gss security. However, this
>
>
>
next prev parent reply other threads:[~2011-05-20 16:41 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-17 16:21 How to control the order of different export options for different client formats? James Pearson
2011-05-17 22:01 ` NeilBrown
2011-05-18 10:19 ` James Pearson
2011-05-18 11:54 ` Performance Issue with multiple dataserver Taousif_Ansari
2011-05-18 16:12 ` J. Bruce Fields
2011-05-19 5:26 ` Taousif_Ansari
2011-05-19 11:50 ` J. Bruce Fields
2011-05-19 12:39 ` Taousif_Ansari
2011-05-19 13:12 ` J. Bruce Fields
2011-05-19 13:14 ` Taousif_Ansari
2011-05-19 13:43 ` J. Bruce Fields
2011-05-19 14:09 ` Taousif_Ansari-G5Y5guI6XLZWk0Htik3J/w
2011-05-19 14:37 ` Shyam_Iyer
2011-05-24 11:39 ` Taousif_Ansari
2011-05-24 11:44 ` Steven Whitehouse
2011-05-24 13:17 ` J. Bruce Fields
2011-05-18 16:20 ` How to control the order of different export options for different client formats? J. Bruce Fields
2011-05-20 13:38 ` James Pearson
2011-05-20 16:41 ` J. Bruce Fields [this message]
2011-06-02 13:37 ` James Pearson
2011-06-04 18:20 ` J. Bruce Fields
2011-06-06 12:14 ` James Pearson
[not found] ` <4DE79236.1080808-5Ol4pYTxKWu0ML75eksnrtBPR1lH4CV8@public.gmane.org>
2011-06-07 20:33 ` Steve Dickson
2011-05-18 0:46 ` Max Matveev
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=20110520164147.GA11176@fieldses.org \
--to=bfields@fieldses.org \
--cc=james-p@moving-picture.com \
--cc=linux-nfs@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).