Details
-
Type:
Bug
-
Status: Unconfirmed
-
Priority:
Low
-
Resolution: Unresolved
-
Affects Version/s: None
-
Fix Version/s: None
-
Component/s: Building and Installing
-
Labels:None
Description
When cfengine 3.6.5 installs, it creates /etc/sysconfig/cfengine3 with the following values:
RUN_CF_SERVERD=1
RUN_CF_EXECD=1
RUN_CF_MONITORD=1
RUN_CF_HUB=0
That will start the 3 processes: cf-serverd, cf-execd, and cf-monitord.
If I modify /etc/sysconfig/cfengine3 to change the value of RUN_CF_MONITORD to 0. When I stop or restart the cfengine service with the command: service cfengine-community stop (or restart), it fails to stop the process cf-monitord. The script /etc/init.d/cfengine3 should check for the existence of a pid file (that the script does actually create) to determine if it should kill a process; it shouldn't use the env variable RUN_CF_MONITORD.