On Tue, 12 Jun 2012 19:49:17 +0200 (CEST) bahamat wrote:
n> The default failsafe.cf includes promises that will start all three daemons.
If you really want it disabled you need to do it in both places. It's not lupus.
I'm really curious what you mean by "it's not lupus."
Ted
__
Forum: CFEngine Help
Subject: Re: cfengine-community service doesn't stop services properly
Author: Jason Christy
Link to topic: https://cfengine.com/forum/read.php?3,26179,26186#msg-26186
Since cfengine creates pid files, it should check for the existence of those
file when stopping the service.
Forum: CFEngine Help
Subject: Re: cfengine-community service doesn't stop services properly
Author: tdr
Link to topic: https://cfengine.com/forum/read.php?3,26179,26182#msg-26182
Hi,
I observed this as well when changing configuration to not run cf-serverd on
clients. Feature of the init script
Forum: CFEngine Help
Subject: Re: cfengine-community service doesn't stop services properly
Author: Jason Christy
Link to topic: https://cfengine.com/forum/read.php?3,26179,26181#msg-26181
I've looked in the script /etc/init.d/cfengine3 to see that it stops a daemon
based upon the values read in
Forum: CFEngine Help
Subject: Re: cfengine-community service doesn't stop services properly
Author: bahamat
Link to topic: https://cfengine.com/forum/read.php?3,26179,26180#msg-26180
Are you sure you saw what you saw?
The default failsafe.cf includes promises that will start all three daemons. If