I would like to give my user shares READ+WRITE but not DELETE permissions, any easy way to do this?

 

The reason I ask is because I have the unRaid box acting as a file server for a Media Centre PC, to generate the thumbnails for content MCE seems to need write access to create the thumbs.db without this access it trys to scan all of the media again to create thumbnails (even if a thumbs.db file exists and it can read it .. daft setup but there ya go that's MS for ya) .. I'd prefer not to give delete permissions for obvious reasons to prevent anyone accidentally deleting content from the shares.

 

TIA.

I'm not sure this is possible under standard unix file permission semantics.  Might need to use "extended attributes" which might take a while to get integrated.

Thanks ... I guess i'll just have to leave it as full read/write and just be careful not to accidentally select the delete option after watching things via MCE then

What about trying read/write to a user share?  It will think it can write, but won't actually do so since it isn't implemented which probably also means delete doesn't work.

 

I HAVEN'T TRIED THIS, but it may work.  Test it.

 

 

Cheers,

Bill

What about trying read/write to a user share?  It will think it can write, but won't actually do so since it isn't implemented which probably also means delete doesn't work.

 

I HAVEN'T TRIED THIS, but it may work.  Test it.

 

 

Cheers,

Bill

If the user-share folder exists only on one drive, the /mnt/diskX folder is linked to by the user shares, not the individual files within it, so in effect, deleting a file from within that folder deletes it from the server. (not good for his situation)

 

As Tom has said, under unix file permissions to create a file, or delete a file, you need exactly the same permissions, the ability to write to the directory the file is in/will be in. They are not seperate permissions.

 

Joe L.

 

 

I understand what Tom said about the limitations of Unix permissions - I am actually talking about taking advantage of an undocumented "feature" of UnRaid.

 

*IF* the folders exist on multiple drives (even if the multiple are just blank placeholders) AND

*IF* MCE views write permissions to the user share as working (but it doesn't, it only happens in memory)

 

*THEN* MCE should see thumbs.db, see that it can write to the disk, and allow the software to perform normally.

 

This will not allow MCE to actually update thumbs.db, however, so how they would be initially created or updated may require some other workaround.  Perhaps aim MCE at a disk share to create the thumbs.db, then move it to a user share?

 

 

Bill

 

 

When the user share is split over multiple disks, due to the total lack of write then I'm just left with the thumbs generated in memory, once you shutdown or close MCE they're rebuilt again, though I haven't yet tried a trick posted somewhere else which seems to imply I may be able to change the permissions of the share via windows which may give me some options.

 

Another option I think may be to create a DFS Share of the user shares via a windows box and set the permissons accordingly and then map MCE to the DFS Share rather than the unRaid share as I think that should work.