On 07/26/2011 02:03 PM, Andy Adamson wrote:
Hi
Which client, which server (distro and uname -a output) did you use? Also, what commands (setfacl,getfacl? nfs4_setfacl, nfs4_getfacl ? plus version) and parameters did you use?
Now using nfs4 acl tools
nfs4_getfacl 0.3.3
nfs4_setfacl 0.3.3
======================================
NFS client (Fedora 15)
======================================
$ nfs4_getfacl directory/
A::OWNER@:rwaDxtTcCy
A::GROUP@:rxtcy
A::EVERYONE@:rxtcy
$ nfs4_setfacl -a A:gdf:sharedgroup@localdomain:rwaDxtcy directory/
$ nfs4_getfacl directory/
A::OWNER@:rwaDxtTcCy
A::GROUP@:rxtcy
A:g:sharedgroup@localdomain:rwaDxtcy
A::EVERYONE@:rxtcy
D:fdi:OWNER@:rwaDx
A:fdi:OWNER@:tTcCy
A:fdi:GROUP@:tcy
A:fdig:sharedgroup@localdomain:rwaDxtcy
A:fdi:EVERYONE@:tcy
$ touch directory/client
$ nfs4_getfacl directory/client
D::OWNER@:r
A::OWNER@:tTcCy
A::GROUP@:tcy
A:g:sharedgroup@localdomain:rtcy
A::EVERYONE@:tcy
Inheritance was added for the group sharedgroup to the directory, but
the file does not gets w permission when the file is created, the NFS
ACL <--> POSIX ACL Mapping on the file "client" on the server are
# getfacl directory
user::rwx
group::r-x
group:admision:rwx
mask::rwx
other::r-x
default:user::---
default:group::---
default:group:admision:rwx
default:mask::rwx
default:other::---
# getfacl directory/client
user::---
group::---
group:sharedgroup:rwx #effective:r--
mask::r--
other::---
Why the client user umask (022) is being used for the inherited
permissions for the group "sharedgroup"? is this by design or a bug?
Thanks in advance
--
To unsubscribe from this list: send the line "unsubscribe linux-nfs" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
