Do you experience problems during downloading?
Check your connection in Status and Interface settings window.
Use Test Server in Config > Servers.
We will probably ask you to do a test using only basic settings.
Do you experience problems during repair or unpacking?
Enable +Debug logging in the Status and Interface settings window and share the relevant parts of the log here using [ code ] sections.
#! /bin/bash
#
# File Extension processing script for SABNZBD+
#
VERSION=20080429
# Turn off case sensitivity for AWK
IGNORECASE=1
# For 0.4.0x compliance, set the RUNPATH to the folder where you want to store the postproc.conf file.
# As 0.4.x now uses a script folder, we dont want to clutter this folder up with the config and net listing files.
# For 0.3.x
#RUNPATH="`dirname "$0"`"
# For 0.4.x
RUNPATH=/root/.sabnzbd/postproc
if [ ! -f "$RUNPATH/postproc.conf" ]
then
1. Is the location /root/.sabnzbd/postproc/postproc.sh correct ?
2. Remove the space between the ! and /bin/bash
3. Make the script executable
chmod +x postproc.sh
Bascy wrote:
[Edit]removing the space did the trick, still strange it did work from the command line .... [/Edit]
When you start it from the command line, the bash shell itself handles the script.
When SABnzbd starts the script, it's the kernel that needs to recognize it as a script.
The bash shell is more forgiving than the kernel.
