MountainMan
Dabbler
- Joined
- Dec 10, 2020
- Messages
- 42
I've read and experimented, but I'm still struggling to configure ACLs (filesystem and share) to accomplish what I'd like. I'm hoping someone has some insight -- or can tell me "it's not going to work because..." :)
I'll peel it back to a core example...
Given two users:
- james
- julie
And a pool named "Blackhole" with a dataset structure like:
I'd like to create two shares as follows:
So at this point my main questions are:
-James (like the user ;) )
I'll peel it back to a core example...
Given two users:
- james
- julie
And a pool named "Blackhole" with a dataset structure like:
Code:
Media Music Video Personal James Julie
I'd like to create two shares as follows:
- A share named "Media" for Blackhole/Media which is *only visible* to the user james, who would have full control of everything under it.
- A share named "Julie Media" for Blackhole/Media/Personal/Julie which is *only visible* to the user julie, who would have full control of everything under it.
So at this point my main questions are:
- Assuming share visibility is determined by share ACLs and having "Access Based Share Enumeration" enabled, that rules out share "Purposes" like "Default share parameters", yet options like "Private SMB Datasets and Shares" don't seem appropriate. What would be chosen here to start?
- As far as the Share ACLs would go, could someone share a simple example of how to limit one to be visible to a specific local Truenas user or group? I see the "Domain" note about using <netbios-name>\\smbusers but the SID note about setting it to "a Domain and Name" is a little cryptic for me and I have yet to be able to limit things.
-James (like the user ;) )