Page 1 of 1

After items are unpacked, only local admin has permissions to open the files

Posted: October 22nd, 2010, 12:50 am
by smidley
Having a strange issue here.  OS is Server 2008 R2.  Using Sab 0.5.4. with Repair + Unpack +Delete.  After an item is downloaded, it gets auto unpacked, and then the old files are deleted leaving the unpacked files in a folder.  For some reason, all of the files (nfo, srt, nzb, and sample files) except the main file in question (a movie for example) have weird permission settings.  The permissions are set to only allow the local admin control of the objects.  This is inconvenient for me because I run this as kind of a headless server, and have to RDP into it every time I need to read an nfo file or something.

I don't have any manual post processing setup, and I don't have any user scripts setup either.  Any ideas on what I might check?  Thanks all.

Re: After items are unpacked, only local admin has permissions to open the files

Posted: October 22nd, 2010, 3:32 am
by shypike
SABnzbd does not specify any rights settjngs on Windows.
Instead it relies on the permissions of the base folders to be correct.
Check the ACLs of the base folders.
Perhaps moving the files from a restricted folder (temporary download folder)
to the final files drags ACLs along, while unrar creates fresh files in the final folder.
In that case you should give the temporary download folder the right ACLs,
like the same as the final folder.

Re: After items are unpacked, only local admin has permissions to open the files

Posted: October 22nd, 2010, 4:59 am
by smidley
shypike wrote: SABnzbd does not specify any rights settjngs on Windows.
Instead it relies on the permissions of the base folders to be correct.
Check the ACLs of the base folders.
Perhaps moving the files from a restricted folder (temporary download folder)
to the final files drags ACLs along, while unrar creates fresh files in the final folder.
In that case you should give the temporary download folder the right ACLs,
like the same as the final folder.
Thanks, that's actually what it was.  My permissions were weird on my temporary download folder.  I think this was actually modified after a windows security update.  I changed the permissions on that folder, and now my completed files are accessible again.