Support Forum

No problem on the RAM disk, but I'd like to have two areas for different sized downloads.  Temporary download location #1 is the RAM disk & has a required field where I set the size of downloads that get processed on temporary download location #1.  I define Temporary download location #2 as a l...

I would like to be able to keep downloads under 2 GB (or whatever amount fits with your available memory) in memory (i.e. /dev/shm), the rars, any pars, all the raw downloaded parts, then unrar, also in memory, then finally move the unrared files to the final location. This would allow me to have sm...

Here's a quick script that takes advantage of the api & does exactly what I was looking for: #!/bin/bash # # ssabnzbd-queue-manager.sh # # This script pauses or resumes all queued nzb files in sabnzbd+. # # It takes either a -p to pause or -r to resume TMP_FILE=`mktemp -p /dev/shm ssab-tmp.XXXXX...

Thanks for the heads up about the api. Fair enough about combining two programming designs.  I haven't looked at your code yet, but it may be possible to implement a queue that picks out one nzb from a directory at a time.  The total queue size & total time left would probably be lost, but that'...

Happy to wait.

Thanks again.

If hellanzb is running or not, I can issue a command like: $ hellanzb -p /path/to/failed/download/ & it will retry the par repair & unrar as necessary, then clean-up appropriately. That hellanzb code for processing an existing folder has to exist & surely the license is friendly enough f...

... or have a manageable queue. Let's say I have a large queue & I only download during a certain time of day, but once in a while I want to download something during the off time.  Currently, I have to manually pause every item in the queue, then resume the main program, then download the one o...