File Server Permission Woes

Question

Ok, I have a pretty simple setup.
I have a single 200gb drive formatted to ext3 and mounted at /mnt/media:
fstab wrote:/dev/sdb1 /mnt/media ext3 defaults,users,acl 0 1
I have the group sticky bit set and all newly created files are automatically owned by group 'media'. Now I want all members of 'media' to have full access to this mount. E.g, user1 creates/modifys file /mnt/media/bumfum, user2 can modify/delete file /mnt/media/bumfum.
I used ACL (setfacl) 'setfacl -R -m group:media:rwx /mnt/media'
getfacl: Removing leading '/' from absolute path names
# file: mnt/media/
# owner: root
# group: media
user::rwx
group::rwx
group:media:rwx
mask::rwx
other::r-x
And it did change all of the permissions of existing files, but I was under the impression that new files would inherit this, instead all new files are only writable by the owner.
Right now, new files are owned by group media, but their access is:
[george@gcomp media]$ getfacl testfile
# file: testfile
# owner: george
# group: media
user::rw-
group::r--
other::r--
Any ideas on what I'm missing here? This is also a samba share with the following options:
[media]
comment = Media
path = /mnt/media
valid users = george arroneva
public = no
writable = @media
printable = no

Answer 1

Alethos wrote:
I'm having trouble with this. Either implementing it or figuring it out or...both?
Say on my server I create a directory I want to manage via acl's.
mkdir /test
chown root /test
chgrp users /test
chmod 770 /test
setfacl default:user:root:rwx /test
setfacl default:group:newgroup:rwx /test
Say user1 goes to that directory, creates anything (directory, file) under permissions it says owend by "user1" not "root" and groups is "users" not "newgroup" therefore whoever created the new directory within "test" is the only one who has rights to change the attributes of it. Where am I getting confused/messing up?
This is the normal behavior. Setting defaults means that the files and directories created under the directory inherit the ACL. It has nothing to do with which user or groups owns that files. That makes your "setfacl default:user:root:rwx /test: totally useless, as root has access to everything by default.What you are looking for is setgid (google for it). Then all files created in the directory get a specified gid. Before you wonder: under linux it is not possible to use the uid for that, meaning that you can't set default owners, just default owning groups.
Unfortunately not everything is possible with ACLs (at least as far as I know). When you have ACL defaults for a directory and create new files and directories everything works fine. But when you cp -p or mv files into that directory, they keep the ACL they had before and don't inherit. This is annoying me because I have some directories shared with samba for my roommate. I would be glad if someone had a solution for this problem. If there is none I guess I just have to make a cronjob to set the ACL every few minutes.
Another thing I don't know about is when someone is in several different groups. Let's say user1 is in groupr and grouprw. groupr only has read permissions for a file, grouprw has read and write permissions, all set via ACL. What permissions does user1 have now? My guess is that he has read and write permissions but I'll have to test that.
BTW:
chown root:users /test is shorter than chown root /test + chgrp users /test
Ruckus wrote:
The same thing I was I think, default just controls directorys or vice-versa, therefore you have to set both.
setfacl -R default:user:root:rwx /test
setfacl -R user:root:rwx /test
setfacl -R default:group:newgroup:rwx /test
setfacl -R group:newgroup:rwx /test
I threw the -R in there for any files that may already exist.
See what I wrote above. Doing stuff with ACL and root makes no sense (and you're missing the -m option)
Last edited by rine (2008-09-28 13:56:52)