SABlocalhost.bat would be the same as "SABnzbd.exe -s 127.0.0.1:8080"
SABcleanini.bat would be something like "mv sabnzbd.ini sabnzbd.ini.OLD ; SABnzbd.exe"
These would be the *clickable* executables for SAB-setups not able to start anymore because of IP, port or other setting problems.
Reason:
An enormous amount of questions in the forum is about "SABnzbd won't start / SABnzbd will give an error when trying to start". So it's a FAQ.
The problem is that de Frequently Given Answer is to run SAB with " -s 127.0.0.1:8080" .... which, however, appears to be difficult for SAB users: It often involves trying to explain how to open a CMD box, and/or how to find & move sabnzbd.ini.
So this can be solved by creating the two executables, which then can just be *clicked* by a user. Problem solved.
(I would find it even better if the normal SABnzbd.exe would fall back to SABlocalhost.exe in case of port problems. But that's a bridge too far (is that an English expresson?) for this moment).
It would be probably wise to put a message/confirmation in the SABcleanini executable saying it should only be run in case of serious SAB startup problem and if SABlocalhost does not solve that problem.
I've implemnted this on my Ubuntu machine:
Code: Select all
sander@lifebook:~/SABnzbd-0.6.0Beta2$ ll SAB*sh
-rwxr-xr-x 1 sander sander 80 2011-02-23 17:44 SABcleanini.sh*
-rwxr-xr-x 1 sander sander 43 2011-02-23 17:32 SABlocalhost.sh*
sander@lifebook:~/SABnzbd-0.6.0Beta2$
sander@lifebook:~/SABnzbd-0.6.0Beta2$ cat ./SABcleanini.sh
#!/bin/sh
mv ~/.sabnzbd/sabnzbd.ini ~/.sabnzbd/sabnzbd.ini.OLD.$$
./SABnzbd.py
sander@lifebook:~/SABnzbd-0.6.0Beta2$
sander@lifebook:~/SABnzbd-0.6.0Beta2$ cat SABlocalhost.sh
#!/bin/sh
./SABnzbd.py -s 127.0.0.1:8080
sander@lifebook:~/SABnzbd-0.6.0Beta2$
