I remember at one point in time someone on here helped me with an issue. The problem is I create a dataset called Media and CHOWN it 777 for Emby and transmission to both have access to the same location. This works as expected with no issues. Problem occurs when I create an SMB share to this Data set and a user creates a file or folder. That file or folder ends up being owner:group owned by the user that created it and does not inherit the permissions of the parent.
I was shown the solution to this at one point and it was any file or folder created through this SMB share would have a certain group owner automatically applied to it (Kind of like setting the sticky bit on a folder but for a share). The setting or permissions was set on the SMB share NOT the folder. I cannot find that post or remember how to do this. If anyone knows what that was?
I think this is where owner@ and group@ come into play but I could be wrong.
absolutely it does… but not at the data set level at the SMB level… there’s a specific thing you can put in the SMB config that specifies any file created by anyone on this SMB share will be givin a specific owner or group… even though you have set on the data set an owner and a group it gets overrided by SMB and whoever the user is that wrote the file to the SMB they take owner and group permissions of the file which means anything else that was accessing this data set now can access these files. or if they can it’s read only
Why can’t you just use NFSv4 ACL type and define access like normally for SMB shares? You can just set an entry granting access for the SMB group that should access the data and move on with life.
I’ll have a look at that and get back
Looks like this made it easier… I switched to NFSv4 on the Dataset and then did an ACL update to push down an inheritance of all the permissions down the tree. Thanks for this… didn’t even know you could switch to NFS
