From: Florian Manschwetus <florianmanschwetus@gmx.de>
To: linux-nfs@vger.kernel.org
Subject: nfs4 acl problems using Nexenta-Communityedition Server and debian testing clients
Date: Wed, 05 Dec 2012 10:48:04 +0100 [thread overview]
Message-ID: <50BF1854.1020204@gmx.de> (raw)
I setup a little network using a central storage server based on
nexenta-Communityedition clients use homes and several shares via nfs4.
As we have some shares used for webdevelopment purposes it is desired to
have acls inherited for specific groups access and user access
(webserver user). I also have trouble with sticky-bit inheritance, which
is needed as the linux gui tools unaware of nfs-acls. Are there plans to
improve support for nfs acls?
Maybe someone here have successfully a solaris nfs server running with
linux clients using extended acls, with inheritance working as expected?
It is really annoying having users not allowed to view/edit files/dirs
they copied just the moment.
regards,
Florian
next reply other threads:[~2012-12-05 9:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-05 9:48 Florian Manschwetus [this message]
2012-12-05 15:41 ` nfs4 acl problems using Nexenta-Communityedition Server and debian testing clients Myklebust, Trond
2012-12-05 16:23 ` Florian Manschwetus
2012-12-05 18:21 ` Myklebust, Trond
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=50BF1854.1020204@gmx.de \
--to=florianmanschwetus@gmx.de \
--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 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.