Once installed, you can start SABnzbd by typing SABnzbd in a terminal or in the gnome (KDE?) menu (Internet->SABnzbd).
Third-party repositories
SABnzbd requires unrar from RPM Fusion or ATrpms.
For RHEL5/6, SABnzbd requires packages available in EPEL (what is EPEL?, Using EPEL): par2cmdline, python26 for RHEL5, etc...
Fedora install instructions:
If you want to get updates automatically, you can install the SABnzbd-release RPM and then run "yum install SABnzbd".
Otherwise, browse the repo and install rpm manually.
RHEL/CentOS/Scientific Linux 5-7 install instructions:
For automatic updates, copy SABnzbd-5.repo (RHEL5), SABnzbd-6.repo (RHEL6), or SABnzbd-7.repo (RHEL7) file to your /etc/yum.repos.d/ directory. Then run "yum install SABnzbd".
Otherwise, browse the repo and install rpm manually.
Run SABnzbd as a service
For Fedora<=18 and RHEL 5-6
The RPM installs a init.d service file but does not start it by defaut. If you want to run SABnzbd as a service executed as user sabuser, you need to
- (as sabuser) run SABnzbd once to have a configuration file (the service checks that /home/sabuser/.sabnzbd/sabnzbd.ini exists). Don't forget to stop SABnzbd when done.
- (as root) define a few variables in /etc/sysconfig/SABnzbd
- (as root) try to start the service ("service SABnzbd start"), see if it's running ("service SABnzbd status"), try to stop it ("service SABnzbd stop"). If you can't stop it, it means the gui address and/or the username/password and/or the apikey is/are wrong (ie. fix /etc/sysconfig/SABnzbd). It's very important that the system can stop properly SABnzbd. Please be careful.
- (as root) if the third step works: "chkconfig --level 345 SABnzbd on", to have SABnzbd started in run levels 3,4, and 5 when your computer starts
The RPM installs a systemd service file but does not start it by defaut. If you want to run SABnzbd as a service executed as user sabuser, you need to:
- (as sabuser) run SABnzbd, configure it and stop it
- (as root): "systemctl start [email protected]" (to start the service, use stop to stop), "systemctl enable [email protected]" (to have it started at boot, use disable to disable). You can check what is going on with "systemctl status [email protected]" or "journalctl [email protected] --this-boot"
