Hello. I'm using runit-2.1.2. I have a question about this.
I checked the operation at the time of service abnormality. - before problem. [root@nodeA ec2-user]# ps -ewwwf |grep lkcheck root 10647 10592 0 7月13 ? 00:00:00 /opt/LifeKeeper/sbin/runsv lkcheck root 12521 10647 0 7月13 ? 00:00:02 /opt/LifeKeeper/bin/lkcheck root 12523 12521 0 7月13 ? 00:00:00 /opt/LifeKeeper/bin/lklogmsg -p lkcheck -l LK_ERROR -s runit -t -a uncaught_error -i 0 -c /opt/LifeKeeper/bin/lkcheck root 25993 23089 0 02:19 pts/0 00:00:00 grep --color=auto lkcheck lkcheck is runit managed service process. - terminate service [root@nodeA ec2-user]# kill 10647 12521 - restart check [root@nodeA ec2-user]# ps -ewwwf |grep lkcheck root 26053 10592 0 02:20 ? 00:00:00 /opt/LifeKeeper/sbin/runsv lkcheck root 26056 23089 0 02:20 pts/0 00:00:00 grep --color=auto lkcheck I was hoping that lkcheck was restarting. However, it has not restarted. I would like to know if this behavior is a specification. Thanks.
