I have been doing research on this and I think I understand the method but didn't find a specific guide on it. If I want to create one primary share IE \User_Backups, within this directory there will be folders such as \Bob, \Jim and \Tom. Obviously Bob is only supposed to access his directory but not Jim or Toms. Same for Jim with access to only \Jim and so on. Now obviously each if these users have read access to \User_Backups and can see the other users folders but can only access their own. My understanding is to achieve this is to use the smb-extra.conf as there is no way to do this through the GUI. It appears it existed in older revisions from some of the screenshots I saw. I have tinkered with the smb-extra.conf an example of which is below.

 

 

[bob]
   path = /mnt/user/user_backups/bob
   valid users = bob
   write list = bob
   force user = root
   read only = no
   guest ok = no
   browseable = no

 

I was looking for someone to either confirm this or point me in the direction away from my misunderstanding.

 

P.S.

Thanks Lime Tech for an awesome software. I'm glad a bought this one its way better than anything I have tried in the past.

I'm not certain as it's been ages since I set this up ...

 

It might apply as a share setting of Security set to "Private" (or was that "Secure"?) for the share named "Backups", then have each user create their own subdirectory under the backups share.

 

EDIT: From the wiki on security settings, but it still doesn't fully spell out how the subdirectory permissions would function:

 

Private means that you specify the exact set of users that can either have readonly or read/write access to the share. If you try to connect to the server you may or may not get a login box. If the username/password of your windows login matches one of the usernames defined on the server side, and that username has either readonly or read/write access (ie, not 'no access), then no login box will appear and you will be be logged into the share with the access rights specified. But if either your windows username is unknown on the server, or your windows password does not match, then windows will present a login box prompting for a username/password. Using this box you can then login to the share using one of the other username/passwords on the server

 

---

 

Secure means that no user account is necessary on the server in order to access the share, and no login box will pop up. But in this mode you can select users than can have read/write access to the share, all other users will have read-only access. Since no login box will appear, in order to get this to work, this must be true:

 

    Whatever username you used to log in to your windows PC must also be a user name on the server. The 'case' of the user name does not matter (actually you must enter all lower-case on server side).

    The password you set on the server must match exactly the password used for your windows logon. The password IS case-sensitive.

 

Hmm I think I'm catching on. I had each user create their folder with it set to public. After switching it to secure each users folder is locked to them. Not my most ideal setup as I would rather control that from the Administrator side but it takes care of my immediate issue. Looking forward to the next release hoping this is something that is built in for admins.