munin-node doesn't start automatically at the boot time, so I sometimes forgot to run, then lost some data from that point.

Using update-rc.d, I add them into a job which can care about this issue.


root@/etc/init.d# update-rc.d munin-node start defaults
update-rc.d: using dependency based boot sequencing
update-rc.d: warning:  start runlevel arguments (none) do not match munin-node Default-Start values (2 3 4 5)
update-rc.d: warning:  stop runlevel arguments (none) do not match munin-node Default-Stop values (0 1 6)

root@:/etc/init.d# update-rc.d munin-node start 20 2 3 4 5 . stop 20 0 1 6 .
update-rc.d: using dependency based boot sequencing


Reference  http://www.debian-administration.org/articles/28


After that, still I couldn't see the munin-node is running after rebooting. So try to google them again with message update-rc.d: using dependency based boot sequencing. The, Google guides me to the website  http://wiki.debian.org/LSBInitScripts/DependencyBasedBoot

The site tells me the following :

Starting with Debian 6.0, the insserv command is used instead, if dependency-based booting is enabled:

insserv mydaemon

Where mydaemon is an executable init script placed in /etc/init.d. insserv will produce no output if everything went OK. Examine the error code in $? if you want to be sure.


So I did the following :


root@jhleepc:/var/log# insserv munin-node
root@jhleepc:/var/log#



'Computer > linux' 카테고리의 다른 글

format usb stick with fat32  (0) 2013.04.02
Run a program at the boot time in Debain way  (0) 2013.03.29
gnome-keyring can't connect to pkcs11 file  (0) 2013.03.26
merge lines of file by using paste  (0) 2013.03.19
posted by citadel