Is there a way to do this in Unraid 5?  Deleting files is so uncommon in my environment I'd prefer to have to log in directly to the unraid server to do a deletion rather than have any user be able to delete them via an exported share.

 

Thanks for any help you can offer.

Not that I know off.  As far as I know once you have given the ability to add files you also give the ability to delete them.

Is there a way to do this in Unraid 5?  Deleting files is so uncommon in my environment I'd prefer to have to log in directly to the unraid server to do a deletion rather than have any user be able to delete them via an exported share.

 

Thanks for any help you can offer.

Linux permissions do not provide for that combination of permissions, although yuo might be able to configure SAMBA to limit in that way over SMB.

 

Basically, to create or delete or rename a file in a directory you need "write" permission on that directory.  There are not separate permissions for creating a file vs. deleting a file in linux.  (But, as I said, it might exist over an SMB connection from Windows, I really do not know.)

Give all user except one read-only permission. The one user, call it "admin", will have read-write permissions and only you will have the password for admin. Only use admin when writing to the array. All other user or device logins will have read-only access.

Thanks for the quick answers!  Yes, I was hoping there might be some Samba magic.  I am not very familiar with Samba either.

 

dgaschk - Alas, several people need to be contributing (some of them not very savvy), and rather frequently at that.  And a single empowered user wouldn't have prevented the situation that I'm now trying to avoid.   

 

In Wndows,  I hit 'del' to delete a file in a local directory (containing files I was about to add to the Unraid, there was one I decided not to add).  Unknown to me (still don't know how it happened) Windows had focus on a different explorer window with the directory from an Unraid share (that was about to get the files I was going to add) selected.  I lost a lot of stuff I can't replace, and am trying to come up with something that would save me from myself.

 

Failing that, let me ask this:  what happened to exporting shares as read-only?  Was this lost in the transition from 4.7 to 5?  This would not have prevented the loss I just encountered, but would be better than nothing.

 

Thanks again!

You might want to look into setting up a SAMBA Recycle Bin.  It would help in your accidental deletion via Windows.

It would NOT help if you telnetted into unraid unix and did a unix delete (rm filename)

 

Been quite a while for me but think this is the thread you want to check http://lime-technology.com/forum/index.php?topic=5446.msg52258#msg52258

 

Hope it helps in the future.

 

Also, you might want to set up a cron to periodically clear up the RecycleBiin.  I have the following done daily and it'll permanently delete anything over 7 days in the RecycleBin location

 

find /mnt/user/RecycleBIN -type f  -atime +7 -print -exec rm -fr {} ';'

I use the Samba Recycle Bin here, saved me a few times from a windows mis key.

 

Only think to note if you enable this - you can not clear out the Samba Recycle Bin via windows, you have to log in to the cli and manually delete the contents of that directory.

 

Myk

 

what happened to exporting shares as read-only?  Was this lost in the transition from 4.7 to 5?

 

Good question.  Hadn't even noticed that, but it was definitely a nice feature.

 

Secure is read-only.

Secure is read-only.

 

That's a Security choice, not an Export choice => is a "Secure" share still publicly available?  [i.e. is it essentially "Public - Read Only" ? ]

 

Given the confusion over secure/private/public and the fact that it apparently varies depending on protocol, it would seem to make sense for Tom to make these distinctions more obvious in the webGUI. Just a thought...

The recycle bin works perfectly; exactly what I needed.  Thanks for the help!

 

 

 

Secure is read-only.

 

That's a Security choice, not an Export choice => is a "Secure" share still publicly available?  [i.e. is it essentially "Public - Read Only" ? ]

 

Yes, a Secure share is publicly readable. Designated users can read-write. A Private share is not publicly readable.