![]() ![]() I force user to nobody, so different people working on same files don't interfere with each other. I have group named 'admin' set as primary group to users with write privileges, everyone else gets read only rights. If user connects anonymously he gets r/o, if he logs in and is a member of assigned group he gets r/w. What am I missing? Why doesn't samba set the correct permissions?Īfter a lot of trial and error, this is the correct code to share samba dir using SGID and unix groups. Newly created files and folders doesn't get intended 774 permission, but rather 764 and 754 respectively. I have tested adding and removing the directory mask, force directory mode, directory security mode, and the force directory security mode, but the behaviors still remains. However, since created folders doesn't have the write flag for group set, server users cant create new files or folders in those folders without sudo. The idea is that both samba users and server users belong to the sambashare group, and thus are to be able to edit, delete, and create files and directories. The parent directory has the set group id flag, thus the sambashare group owner. ![]() rwxrw-r- 1 netuser sambashare 0 21:07 New Text Document.txt When a samba client (a windows 7 box) uses the 'netuser' account to create a file or directory, the permissions become drwxr-sr- 2 netuser sambashare 4096 21:14 New folder My current settings for a specific share: When a client creates a new folder or file, the permissions aren't set according to the settings in smb.conf. I have a ubuntu server sharing some folders using samba. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |