Tag Info

Hot answers tagged

3

Finally we found that sickbeard start at boot, but fails. In /var/log/boot.log we can see this error: Starting SickBeard /usr/bin/python: can't open file 'SickBeard.py': [Errno 2] No such file or directory and looking at sickbeard init script: APP_PATH=${SB_HOME-/opt/sickbeard} for some reason we do not know, when sickbeard start, /opt is not ready. ...


2

I think the functions you are looking for are sourced from /lib/lsb/init-functions, and named log_success_msg and log_failure_msg: $ . /lib/lsb/init-functions $ log_success_msg foo * foo $ log_failure_msg foo * foo In this output, the first * is grey, the second is red (error case). Not extremely colorful, just enoug to get the point across... From ...


2

You could use the functions provided by the lsb-base package in /lib/lsb/init-functions. I have seen init.d scripts sourcing that file and then using the functions within, such as log_end_msg: $ (. /lib/lsb/init-functions; log_end_msg 1) ...fail! $ (. /lib/lsb/init-functions; log_end_msg 0) ...done. For example, a snippet from /etc/init.d/ssh (case ...


2

Creating your crontab file with crontab -e is probably the best method for you, but starting your crontab lines with the # character tells the system to ignore those lines. Remove the # and leading whitespace before the 30 in your crontab line. Should just look like this: 30 * * * * /home/michael/Documents/example.sh Additionally, please ensure that cron ...


2

Some points that seem to be confusing you: # is the comment character. Adding it to the beginning of a line makes cron ignore that line. Don't mess with /etc/cron/hourly etc. There's no need to and they have a different format (see next point). The format of a user's crontab is minute hour day-of-month month day-of-week command The format of the files ...


1

I guess that cups service is an upstart job that run /etc/init.d/cups script. Check if is present /etc/init/cups.conf and if it exec /etc/init.d/cups. Regarding the removal of links in rcX.d you should remove your script in /ect/init.d before you run update-rc.d command, indeed according to update-rc.d manual: When invoked with the remove option, ...



Only top voted, non community-wiki answers of a minimum length are eligible