Auto Start in XBMC

Support for the Debian/Ubuntu package, created by JCFP.
Forum rules
Help us help you:
  • Are you using the latest stable version of SABnzbd? Downloads page.
  • Tell us what system you run SABnzbd on.
  • Adhere to the forum rules.
  • 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.
Post Reply
neil192
Newbie
Newbie
Posts: 2
Joined: January 12th, 2012, 6:24 pm

Auto Start in XBMC

Post by neil192 »

Hi Everyone

I have just managed to get SABNZBD install on my XBMC box, i can start SABNZBD by connecting to it and running the command below

sudo /etc/init.d/sabnzbdplus restart

Is there any easy way that i can make it start every time the media centre is turned on,

i am only just starting with LINUX so the most basic commands would be helpful :-)

Neil
User avatar
jcfp
Release Testers
Release Testers
Posts: 1004
Joined: February 7th, 2008, 12:45 pm

Re: Auto Start in XBMC

Post by jcfp »

neil192 wrote:sudo /etc/init.d/sabnzbdplus restart
If that works, the program should be automatically started on boot too. If not, something is missing/wrong/unavailable at the time the program tries to start. The usual culprits include unmounted partitions, missing usb drives, encrypted home dirs, or network interfaces not yet up and/or configured with the right ip address. A search on these forums or google reveals fixes for all of those.
User avatar
sander
Release Testers
Release Testers
Posts: 9062
Joined: January 22nd, 2008, 2:22 pm

Re: Auto Start in XBMC

Post by sander »

jcfp wrote:
neil192 wrote:sudo /etc/init.d/sabnzbdplus restart
If that works, the program should be automatically started on boot too. If not, something is missing/wrong/unavailable at the time the program tries to start. The usual culprits include unmounted partitions, missing usb drives, encrypted home dirs, or network interfaces not yet up and/or configured with the right ip address. A search on these forums or google reveals fixes for all of those.
@jcfp:

Doesn't the 'runlevel' determine which daemons are started? And that's done via files in the corresponding /etc/rcX.d/... file? If so, could it be that on the OP's system, one of those files is missing/corrupt/ ... ?
Post Reply