1 nzb at a time or poll daemon?

[tomdones]

I need to feed in 1 .nzb at a time, each 10 seconds before the last completes. I don't see the option in the config, but am I missing it? If I can poll the daemon for remaining queue time that would work too.

Edit: I'm currently running node.js to parse the .nzb for the last filename, then poll the directory. This won't be an option for where sabnzbd will be going next.

[safihre]

Why can't there be 2 active at the same time? :p
This is not really a option any regular user needs, so you'll have to program something yourself that checks the Queue api to see if it's almost done.

[tomdones]

Thank you for the conclusive answer. I'm not going down that road :-P, in fact, I'm eyeing the notification script option and thinking... 'queue_done' ... or ... 'complete' ...might be the answer. Will those 2 trigger no matter any fail or success? I'm thinking complete is per job and queue_done is more or less 'idle'? If 'error' occurs does 'complete' trigger afterwards? I can't find a real in depth explanation of the if/else conditions of these parameters in Sab. I'm assuming if I put simply... cp this.file to.this ...in the notification script, the script will run it after every 'job' no matter what, as long as in Sab my parameters are only these 3: Job Finished, Job Failed, Error.

Code: Select all

##!/bin/bash
#
while [[ $# > 0 ]]; do
case "$1" in
	complete|failed|error) cp A.nzb B.nzb;
	*) echo "Don't care...or should I?"
esac
shift
done
exit

BTW, the notification script isn't passed the jobname or nzb name?

[safihre]

That's what we have the post processing scripts for They get the name, location, etc of an NZB after all the repair, extraction and moving is done.
Isn't that a better solution maybe?

[tomdones]

I think that is the best idea, you're surely right. However, how do they work :-/ The only thing I see related to post processing is in the "Categories". I tried the category options real quick, but couldn't figure out how to force the script to run every time regardless of success of any one operation. I used "+Delete", and I have unchecked "Post-Process Only Verified Jobs". Tried "Download" but then it doesn't repair/extract. Tried "+Unpack" but if it can't be unpacked... (I don't see "+Move" though or understand what the equivalent of "Job Done, Next" is in those options).

Honestly, thanks for your help. I'm sticking with what I have, being it works (just spaghetti'ish for the user). I'm not diving down the rabbit hole to add an API to get queue time (some of the apis look well thought out, props, I read them all).

Off topic and this really doesn't matter, but the wiki states "In Windows the parameters will be enclosed in double quotes ("my name").", but parameter %1 is not quoted and others aren't as well.

[safihre]

https://sabnzbd.org/wiki/scripts/post-p ... ng-scripts
So you can set it to run always, by applying it to your Default category. Then every category that sets Script to Default will also run that script.
The quotes will happen on the command line, when getting the parameters in the script they are already removed by the OS.

[tomdones]

Again, thanks. My concerns now rest in the actual help that is given on the wiki in regards to the scripts. And when my concerns are to that point, I think I'm good :-) You can read below, but I feel sabnzb is doing what I need it to. That's great, so thank you for sab.


I haven't tried to add my own Category. I've only used the first Default category so far. Under that category, I'm forced to choose a modifier under the Processing category.

Category Priority Processing Script

The above is set as follows...

Category = Default
Priority = Normal
Processing = +Delete **
Script = kickoff.bat

** I have no option for Default under the Processing drop down. So I assume I add in my own category and fill them in as follows: "Default" "Default" "Default" "kickoff.bat". Of course even under the Script category I then have the option of Default. I assume that means to use whatever the first Default category uses, even though the 2nd category is Default too. But, it then reads "default", not "Default", so a rose is not a ROSE (but case sensitivity isn't mentioned on the wiki page for Categories).

The help pages on the wiki for the scripts seem to imply prior usage or answers to questions that are not given on their respective pages. They help understand what arguments represent thus implying which arguments are passed to your script, but how that script is invoked isn't clear to someone like me who has never used sabnzb. I have literally never used it until just a few days ago, so to me it appears the wiki doesn't explain much in regards to the scripts outside of arguments (However, all other options throughout the wiki are explained perfectly fine).

About the double quotes, right, doesn't matter. People should always be prepared to handle them anyhow, that's a user problem.