A minor annoyance I've had ever since adopting Synologys over a decade ago. Now with the latest purchase, it's p!$$ed me off sufficiently to do something about it. Hoping the knowledge here can assist please.
One of our primary uses for the NAS is essentially as a file server/network drive. All MAC clients connecting SMB to the various file shares for read and write. However, permissions have always been a bit of a challenge, so more often than not, when the wife or kids complain <x> can't see/find/write to <abc> file/directory, I just ssh in and fix it. But I'm over that, so I want to fix it permanently.
I've set up various groups for differing family members' access such that only <x> group can see/write to <y> Shared Folder. And I've set that as much as possible in the fileshare/user/group/ perms in DSM. But what I want to achieve is not 'individual' file/directory ownership. I want to have all files in a given Shared Folder, on creation, owned by my chosen named user with the group I want associated with that specific Shared Folder, and I want all directories in there to have 770 with all files 660.
In my thinking, in this way, I have a single account owning the files, and everyone in the group can see/do what they want/need, with 'others' excluded. e.g. under 'family' shared folder, I would have:
So, what's the best way to achieve this please? My thinking as follows. If you have better ideas/solutions, I'm all ears.
1. Change the umask to 007.
So, how/where can I change the umask in Synology? And is it the same format as any other *nix distro, e.g. 'umask 007'?
2. Many years ago, I used samba's specific share confs to achieve my ownership goals for default user:group ownership, presumably I can still do that.
So, how/where can I set perm settings for samba that will survive both reboot and upgrade?
3. Or is there a better way? e.g. set ownership of the Shared Folder home to my desired group, and then set the GUID on the Shared Folder home.
This would achieve my group ownership, but still leaves the default file ownership up in the air.
Your thoughts and advice appreciated.
One of our primary uses for the NAS is essentially as a file server/network drive. All MAC clients connecting SMB to the various file shares for read and write. However, permissions have always been a bit of a challenge, so more often than not, when the wife or kids complain <x> can't see/find/write to <abc> file/directory, I just ssh in and fix it. But I'm over that, so I want to fix it permanently.
I've set up various groups for differing family members' access such that only <x> group can see/write to <y> Shared Folder. And I've set that as much as possible in the fileshare/user/group/ perms in DSM. But what I want to achieve is not 'individual' file/directory ownership. I want to have all files in a given Shared Folder, on creation, owned by my chosen named user with the group I want associated with that specific Shared Folder, and I want all directories in there to have 770 with all files 660.
In my thinking, in this way, I have a single account owning the files, and everyone in the group can see/do what they want/need, with 'others' excluded. e.g. under 'family' shared folder, I would have:
Code:
drwxrwx---+ 1 svc_accnt family 88 Jun 4 20:36 BACKUP-DO-NOT-DELETE
drwxrwx---+ 1 svc_accnt family 4880 Jun 4 20:36 Recipes
drwxrwx---+ 1 svc_accnt family 21112 Jun 4 20:36 WarrantiesSo, what's the best way to achieve this please? My thinking as follows. If you have better ideas/solutions, I'm all ears.
1. Change the umask to 007.
So, how/where can I change the umask in Synology? And is it the same format as any other *nix distro, e.g. 'umask 007'?
2. Many years ago, I used samba's specific share confs to achieve my ownership goals for default user:group ownership, presumably I can still do that.
So, how/where can I set perm settings for samba that will survive both reboot and upgrade?
3. Or is there a better way? e.g. set ownership of the Shared Folder home to my desired group, and then set the GUID on the Shared Folder home.
This would achieve my group ownership, but still leaves the default file ownership up in the air.
Your thoughts and advice appreciated.
