Re: nfsacl umask inconsitency
Lennart Poettering <[email protected]> Tue, 8 Jun 2004 17:33:13 +0200
| Newsgroups | gmane.linux.file-systems.acl.devel |
|---|---|
| Organization | .phi. |
| Message-ID | <[email protected]> |
On Mon, 24.05.04 19:51, Andreas Gruenbacher ([email protected]) wrote: > That's not a bug in nfsacl, that's an flaw inherent in the nfs protocol: The > client does not send the umask to the server, but it applies the umask > locally. If there is a default acl, the server applies the default acl, which > results in what you have observed. The client cannot safely know whether > there is a default acl or not; it doesn't actually know much about > acls. What a pitty! Is there any chance to get that fixed in the furture? maybe nfs4? What is the best workaround for that? Any other then setting umask to 007 on all clients? Thanks, Lennart _______________________________________________ acl-devel mailing list [email protected] http://acl.bestbits.at/mailman/listinfo/acl-devel