From: "J. Bruce Fields" <bfields@fieldses.org>
To: steve <steve@steve-ss.com>
Cc: Jeff Layton <jlayton@poochiereds.net>, linux-nfs@vger.kernel.org
Subject: Re: POSIX acls over nfs4
Date: Tue, 28 Feb 2012 15:00:15 -0500 [thread overview]
Message-ID: <20120228200015.GD2723@fieldses.org> (raw)
In-Reply-To: <4F466467.3030506@steve-ss.com>
On Thu, Feb 23, 2012 at 05:08:07PM +0100, steve wrote:
> OK. I see what you mean. umask 0022
> So I can have a group rw with posix but not with nfs4_setfacl:-(
>
> That's on openSUSE who default to 0022. The default on Ubuntu is
> 0002 so presumably we could have group rw over nfs4 there out of the
> box?
>
> Is it a lot of work to implement umask override for nfs4? Or make it
> an option perhaps?
Two fulltime-kernel-hacker-week-equivalents?
I'm not sure, I just made that up.
It does appear that it's necessary to make v4 ACLs usable in a lot of
cases.
--b.
> At the moment I'm using a big hammer and scanning the share every 4
> seconds to change the permissions of any files created there. My
> other thought was to have the share on a different partition, umask
> it to 0002 and export that. But these are workarounds. It would be
> really good to have the nfs4 acls do it.
prev parent reply other threads:[~2012-02-28 20:00 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-18 20:08 POSIX acls over nfs4 steve
2012-02-19 17:15 ` steve
2012-02-23 7:15 ` steve
2012-02-23 8:33 ` tao.peng
2012-02-23 12:50 ` steve
2012-02-23 11:39 ` Jeff Layton
2012-02-23 11:53 ` steve
2012-02-23 14:40 ` J. Bruce Fields
2012-02-23 15:33 ` steve
2012-02-23 15:42 ` J. Bruce Fields
2012-02-23 16:08 ` steve
2012-02-25 8:19 ` steve
2012-02-28 20:05 ` J. Bruce Fields
2012-02-28 23:22 ` steve
2012-02-29 12:44 ` J. Bruce Fields
2012-02-29 14:04 ` steve
2012-02-29 14:09 ` J. Bruce Fields
2012-02-29 14:26 ` steve
2012-02-29 14:32 ` J. Bruce Fields
2012-02-29 14:40 ` steve
2012-03-01 20:56 ` J. Bruce Fields
2012-03-01 22:11 ` steve
2012-03-02 18:03 ` J. Bruce Fields
2012-02-28 20:00 ` 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=20120228200015.GD2723@fieldses.org \
--to=bfields@fieldses.org \
--cc=jlayton@poochiereds.net \
--cc=linux-nfs@vger.kernel.org \
--cc=steve@steve-ss.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 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).