is setfacl broken? or is it Linux acl support in general?

Furnish, Trever G TGFurnish at herffjones.com
Tue Aug 30 01:59:49 UTC 2011


Can someone help me understand where I'm going wrong with setfacl?

I want every new file created in a directory to have an effective acl of rwx for user "bob".

I do this:
setfacl -m d:u:bob:rwx,u:bob:rwx directory

Then I touch a new file into that directory:
touch directory/newfile

Unfortunately, newfile comes in with some seemingly random acl -- sometimes it's r--, sometimes it's rw-, but it's never rwx.

What gives?

I've tried explicitly setting the default and non-default masks too -- that doesn't seem to help (but here's the command I mean):
setfacl -m d:m::rwx,m::rwx,d:u:bob:rwx,u:bob:rwx .

Still gives the same results.

If I then turn around and re-apply what should be the existing default acl to the new file, this time it sticks.  Same thing happens if I 'chmod +x newfile':
setfacl -m u:bob:rwx newfile

It really just seems like default acl support under Linux doesn't work.  That really, really sucks.

--
Trever





More information about the redhat-list mailing list