Support Forum

I started teaching myself how to do chroot jails pretty recently, but I've figured out quite a bit, so something of a sunk cost there as well, putting aside resource issues. And chroot is definitely a thing in Linux, in fact I think it was a Unix feature before BSD...

Docker is more resource intensive, as I understand it. And I'm not fundamentally opposed to upgrading, but is it really likely to solve this problem?

More specifically, I have Sab up and running properly when I run it unjailed. But I have been working on getting it to work inside a chroot jail. After a lot of trial and error I've been able to get that to run, no errors or warnings. I can load an nzb but then...nothing happens. The same nzb, loade...

When I set it to "false" I got an error starting the program, but when I set it to "0" that worked exactly as I wanted it to, thank you.

Is there a way to do this? All my googling leads me to ways to enable this or fix it when it's not working. I want to *prevent* the Sabnzbd user from being able to do this, not even see those options in the dropdown menu. It seems like the way to do it would be to set would be to set the variable $p...