Support Forum

i should have double checked the file inside the 4.0.0 test. the folder is ok (owner and only inherited) so i didnt think to check the file itself, the bin file has PUID/PGID/Everyone with permissions, no inherited ones. with 4.2.2 the test download folder is the same as 4.0.0 now (has inherited per...

the 100mb test is fine, owner set but no explicit permissions, only inherited
i'll bump it back up to 4.2.2 and see if its still the same with that

sab shows completed folder permissions as empty, always has been. i double checked the ini file just in case as well and its empty in there [misc] permissions = "" the sab part of the yaml project file has the IDs already - and they are correct (all the containers use the same IDs) sabnzbd...

dsm 7.2 container manager (docker) linuxserver images PUID and PGID set completed download permissions is blank umask is not set has been working with sonarr for a very long time in 4.0.0 newly downloaded files had the owner set to the PUID, and then the PUID, PGID, and Everyone, would be explicitly...

How is this different from what is already in SABnzbd? the detection of nested rars may be in the code already but its not user accessible, we cant determine what happens when thats encountered (as far as i am aware) Your new idea is "really basic check for nested rars". yes, its a simple...

The are several detection methods already in SABnzbd, but scammers come up with new ideas all the time. seeing how scammers will always try to confuse the software can you just add really basic check for nested rars and give us the option of what to do with them if found? ie exactly like the existi...