Skip to main content

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

3
  • Apparently I'm using version 4. ACL did the trick, thanks for your help ! Commented Apr 22, 2021 at 21:48
  • 1
    access.redhat.com/solutions/3951111 explains the umask/ACL relation over NFS. As this site is only visible after login, unfortunately, I describe the issue in own words: Seeing the umask influencing the resulting permissions despite an ACL telling otherwise is due to nfsv3 (and nfs4 < 4.2) not offering a way for the client to pass the requested mode and umask separately to the server. So the NFS client applies the umask locally and passes the result to the server which in turn applies the acl - leading to undesired results. The only way around this is to switch to NFSv4.2. Commented Sep 2, 2022 at 14:10
  • @uli42 Nice find! Commented Sep 2, 2022 at 15:38