I have a directory called "members" and under it there are folders/files. How can I recursively set all the current folders/files and any future ones created there to by default have 775 permissions and belong to owner/group nobody/admin respectively? I enabled ACL, mounted, but can't seem to get the setfacl command to do this properly. Any idea how to accomplish this?
Add a comment
|
4 Answers
I actually found something that so far does what I asked for, sharing here so anyone who runs into this issue can try out this solution:
sudo setfacl -Rdm g:groupnamehere:rwx /base/path/members/
sudo setfacl -Rm g:groupnamehere:rwx /base/path/members/
R is recursive, which means everything under that directory will have the rule applied to it.
d is default, which means for all future items created under that directory, have these rules apply by default.
m is needed to add/modify rules.
The first command, is for new items (hence the d), the second command, is for old/existing items under the folder. Hope this helps someone out as this stuff is a bit complicated and not very intuitive.
-
2This is exactly what I needed to get the owner of a grandparent directory to be able to properly modify the contents of new grandchild directories.– JoostAug 18, 2015 at 7:01
-
If you are the only user of your Rpi, you can replace g:groupname with pi:pi or just pi– SDsolarMar 11, 2017 at 22:30
-
You can specify for user, groups, and other in one line, e.g.
-Rdm g:groupnamehere:rwx, -Rdm u:groupnamehere:rwx. Nov 27, 2018 at 15:05 -
This does not set new files to 775, only directories, the files are still being uploaded to 644– tmaroisOct 10, 2020 at 21:40
To go with your accepted answer ...
You can combine those commands together as:
sudo setfacl -Rm d:g:groupnamehere:rwx,g:groupnamehere:rwx /base/path/members/
-
Thats cool. How come you set
d:on the first item rather than-Rmd? I can tell that the second parameter should have nodefault-- it's just odd how linux accepts it to me.– JREAMMay 2, 2017 at 3:12 -
1@JREAM: Linux (actually
getopt_long) sends the whole argument to option-mwhich is parsed by hand bysetfacl, separating by commas the passed arguments. They are added to a linked list which is looped through at the end when actually changing the ACL. Jun 28, 2017 at 8:04
setfacl on linux has the -d and -k options for manipulating default permissions which are probably what you are looking for (see man for more info).
It is easy to recursively set simple UNIX permissions at upon demand of an appropriately authorized user, the permissions of directories and files. It is not possible to automatically impose this.
You could tell users to use the set the umask of 0002, and that helps to make new files at 0775 (depending on the application). But it is not enforcable.
My understanding is that ACLs are not inherited on UNIX/Linux systems. They are set upon demand.
As for file/directory ownership, you are pretty much out of luck here.
As for file/directory group ownership, by setting the directory set-gid bit (i.e. g+s on DIRECTORIES), this does cause the group ownership to be inherited.
What I have done in such situations is to execute a periodic root cron script which resets non-conforming permissions/ownerships to the standard in such directories.
Another (NOT RECOMMENDED) process is to have the same user-id be used when working on these files. This could be accomplished by the user logging into the system under his own UID, and then using sudo or su to run as the id. This still is not 100% especially concerning ACLs and permission bits.
-
The right way to do this for future files is setting defaults using
setfaclandsgid.chownchanges user and optionally group ownership,chgrpchanges group ownership andchmodchanges mode. If retroactively changing, each of these is recursive, but it's better to usefindwith type and exec options so that you can change the directories and the files to different. sgid is the only part you got right, the rest is wrong or bad or both. The answers above have the correct information. Jun 9, 2022 at 21:52