ACL: Difference between revisions
| Line 6: | Line 6: | ||
So, the command to Allow anyone in the users group to write files to path/to/some/folder | So, the command to Allow anyone in the users group to write files to path/to/some/folder | ||
setfacl -Rm g:users:rwX /path/to/some/folder | setfacl -Rm g:users:rwX /path/to/some/folder | ||
setfacl -d -Rm g:users:rwX /path/to/some/folder | setfacl -d -Rm g:users:rwX /path/to/some/folder | ||
=== Links === | === Links === | ||
* [http://bencane.com/2012/05/27/acl-using-access-control-lists-on-linux/ ACL: Using Access Control Lists on Linux] | * [http://bencane.com/2012/05/27/acl-using-access-control-lists-on-linux/ ACL: Using Access Control Lists on Linux] | ||
Revision as of 11:23, 16 March 2017
Sadly the built in UNIX way of doing permissions, with it's notions of users, groups, and "others" is in practice quite difficult to use to make "shared folders". ACL (for access control lists) is an extension to these mechanisms that gives more flexibility. The setfacl command is the thing that sets the options.
So, the command to Allow anyone in the users group to write files to path/to/some/folder
setfacl -Rm g:users:rwX /path/to/some/folder setfacl -d -Rm g:users:rwX /path/to/some/folder