From: Steve Dickson <SteveD@redhat.com>
To: "J. Bruce Fields" <bfields@fieldses.org>
Cc: Tony Asleson <tasleson@redhat.com>, linux-nfs@vger.kernel.org
Subject: Re: [PATCH] exportfs: Add -s option.
Date: Mon, 21 Oct 2013 12:55:04 -0400 [thread overview]
Message-ID: <52655C68.1000604@RedHat.com> (raw)
In-Reply-To: <20131021140114.GE18657@fieldses.org>
On 21/10/13 10:01, J. Bruce Fields wrote:
> On Mon, Oct 21, 2013 at 09:51:25AM -0400, Steve Dickson wrote:
>> I guess we could change -v to used what the -s is proposing,
>> but that could break someone's existing configuration...
>
> Also, looking at my home server.... It would be annoying to get:
>
> /export *(rw,sync,wdelay,hide,nocrossmnt,insecure,no_root_squash,no_all_squash,no_subtree_check,secure_locks,acl,anonuid=65534,anongid=65534)
>
> when all you need is:
>
> /export <world>(rw,wdelay,insecure,no_root_squash,no_subtree_check)
>
> (Actually I wonder why it's even showing wdelay and no_subtree_check
> when those are both defaults? But this is on F16, maybe it's different
> now. I should really update that machine.)
No, the defaults have not changed for (quite) a while...
The defaults are:
ro, root_squash, wdelay, no_subtree_check
Now it turns out wdelay (aka NFSEXP_GATHERED_WRITES) is a v2 only thing...
So do we really need to have that on by default, now that we are
slowly moving away from v2 support?
steved.
next prev parent reply other threads:[~2013-10-21 16:54 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-02 17:19 [PATCH] exportfs: Add -s option Tony Asleson
2013-10-02 21:40 ` J. Bruce Fields
2013-10-21 13:51 ` Steve Dickson
2013-10-21 14:01 ` J. Bruce Fields
2013-10-21 16:55 ` Steve Dickson [this message]
2013-10-21 18:01 ` J. Bruce Fields
2013-10-21 17:14 ` Steve Dickson
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=52655C68.1000604@RedHat.com \
--to=steved@redhat.com \
--cc=bfields@fieldses.org \
--cc=linux-nfs@vger.kernel.org \
--cc=tasleson@redhat.com \
/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.