![]() ![]() # In order to enable or disable this script just change the executionĮxec 2> /tmp/rc.local.log # send stderr from rc.local to a log fileĮxec 1>&2 # send stdout to the same log file # Make sure that the script will "exit 0" on success or any other # This script is executed at the end of each multiuser runlevel. It'll check whether the folders exist (every 5 seconds) and start the services accordingly. etc/init.d/sabnzbdplus start & /etc/init.d/sickbeard start & /etc/init.d/autosub start & /etc/init.d/couchpotatov2 start Sleep 5 & checkdir #loop to check if directory is ready All program configurations are in /home/username, so unreadable. My disk is encrypted and thus, is only readable when logged in. Maybe other people encounter the same problem. In this case, looking at your runlevel, I suggest this configuration: update-rc.d sickbeard start 06 2 3 4 5. This will assign S99 (the last possible) for start during system boot and K01 (the first possible) for stop during shutdown or reboot. ![]() This script are executed during system boot following the alphabetical order, so using update-rc.d it is possible choose 'when' service start/stop, for example: update-rc.d sickbeard start 99 2 3 4 5. These are symbolic links to /etc/init.d/sickbeard script. To accomplish this, take a look at /etc/rcX.d folder and remove Sxxsickbeard and Kxxsickbeard files. usr/bin/python: can't open file 'SickBeard.py': No such file or directoryĪnd looking at sickbeard init script: APP_PATH=$įor some reason we do not know, when sickbeard start, /opt is not ready.Īs workaround, starting sickbeard later during boot sequence seems fix the issue. In /var/log/boot.log we can see this error: Starting SickBeard Finally we found that sickbeard start at boot, but fails. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |