Support Forum

I gave it a try myself, and everything seems to work ok so I should be able to continue with my scripting. Thanks for the help guys!

Any chance the ability to run perl scripts natively might make it into Sabnzbd 0.5.0?

-A

lol. Unfortunately that doesn't help when your stage gets stuck on That would explain why I hadn't noticed the show output link

-A

rAf: Yes, my script has the shebang as the first line.

markus101: I hadn't thought of that. Not a really elegant solution, but I'll give it a try.

-A

Sander: Interestingly enough, it seems that I can execute batch files OK. I just tried a simple little... echo testing > c:\temp\scriptoutput.log ...and everything worked OK. It seems that the problem is particular to Perl. I verified that the Perl interpreter binary is in the path of the user accou...

In order to verify whether the problem lies in an issue with sabnzbd's BG-running of scripts and the print statement (as proposed by markus101), I tried the following script with the exact same results: foreach (@ARGV) {     i++; } exit 1; Sabnzbd is still stuck "Running script..." as I ty...

Actually, the code I inserted into my initial description was not a cut/paste, it was short enough I just retyped it. The actual script used by sabnzbd does not use relative paths. It is supposed to open the file d:\temp\args.log. This file is never created. Also, even if the script were completed s...

Given that there's plenty of discussion regarding various script types (Python, shell scripts, batch files, etc.), I assume that Sabnzbd isn't particular about the type of script executed post-processing, so long as there's an interpreter available and it receives its exit code. If true, then I wond...