Hai,
I have set up default acls on a directory to allow user user1 to read it. This directory is owned by root:root.
Code:
setfacl -d -m u:user1:rx /directory
I also did via the group.
This works fine, new files made by root are readable.
Code:
getfacl /directory supports this:
...
default:user:user1:r-x
...
default:group:user1:r-x
However, the process that is writing new files is writing them as 700, and this user cannot read those files.
Code:
getfacl /directory/newfile gives:
#file: newfile
#owner: root
#group: root
user::rwx
user:user1:r-x #effective:---
group::r-x #effective---
group:user1:r-x #effective----
mask::r-x
other::r-x
This occurs also if you create a file that is readable, then chmod 700.
Can some explain the effective rights for me and why its overiding the acls where the files are either chmod 700, or written as 700 by the process that is writing them? I know this is the correct behaviour, I am just trying to understand why this is.
Chmod overiding default ACLs.
2 posts
• Page 1 of 1
2 posts
• Page 1 of 1