thesuffering Wrote:ive looked over all the options in the config but see nothing
Yeah, I suspected that...
Mhm...maybe you could work another way round:
Try creating a batch-file which will set the permissions for the files, after sickbeard moves them.
See here for reference:
With Windows > XP you can just run "cacls" from the command-line, as XCACLS is integrated in windows now. Just replace "xcacls.exe" in the mentioned support-thread with "cacls", you do not need to download the file mentioned in the post.
My suggestion would be the following: You create a simple script that runs first the sickbeard-postprocessor and changes the file permissions afterwards via the Windows API (so you don't have to use cacls). Problem with this is: You need some logic in order to determine where sickbeard puts the file (you could just use the output of the pp-script).
I could try and write a litte application for that, but currently my raid is broken (one HDD went away) and well...windows does not seem to like that (sometimes you just have to hate it... linux has no problems whatsoever with it...) and I have to wait until I can rebuild my raid in order to get access to my c#-tools.