To verify that the LifeKeeper controlling processes are running, type the following command:
ps -ef | grep runsv
You should see output similar to the following:
root 29093 1 0 11:35 ? 00:00:00 /opt/LifeKeeper/sbin/runsvdir -P /opt/LifeKeeper/etc/service
root 29097 29093 0 11:35 ? 00:00:00 /opt/LifeKeeper/sbin/runsv lcd
root 29098 29093 0 11:35 ? 00:00:00 /opt/LifeKeeper/sbin/runsv lcm
root 29099 29093 0 11:35 ? 00:00:00 /opt/LifeKeeper/sbin/runsv lk_logmgr
root 29100 29093 0 11:35 ? 00:00:00 /opt/LifeKeeper/sbin/runsv lkcheck
root 29101 29093 0 11:35 ? 00:00:00 /opt/LifeKeeper/sbin/runsv lkscsid
root 29102 29093 0 11:35 ? 00:00:00 /opt/LifeKeeper/sbin/runsv lkvmhad
root 29103 29093 0 11:35 ? 00:00:00 /opt/LifeKeeper/sbin/runsv steeleye-lighttpd
root 29104 29093 0 11:35 ? 00:00:00 /opt/LifeKeeper/sbin/runsv ttymonlcm
root 29105 29093 0 11:35 ? 00:00:00 /opt/LifeKeeper/sbin/runsv lkguiserver
root 29465 2894 0 11:36 pts/0 00:00:00 grep --color=auto runsv
These processes start, stop, and monitor LifeKeeper core daemon processes and must be running to start LifeKeeper. These processes are configured by default to start when the system boots and this behavior should not be altered.
Post your comment on this topic.