Forum: CFEngine Help Subject: Re: cfengine versus standard system tools Author: mikesphar Link to topic: https://cfengine.com/forum/read.php?3,23938,23946#msg-23946
matt_garman Wrote: ------------------------------------------------------- > So I believe the real solution to this specific > scenario is to extend on the examples I've seen. > A "check service running" promise should probably > both start the service (if necessary) and > update the system config to run it by default. On > the one hand, I like this: it sort of feels like > redundancy to ensure the service is running. But > on the other hand, it sort of feels like a > duplication of effort. This is jut my opinion, but I believe this should be considered as two separate and almost entirely unrelated promises. Promise 1: should be configured to start automatically at boot time Promise 2: should be running right now Now, in practice you would likely make the variable used for the same. But, it is possible for either promise to be broken and repaired independent of the other. I don't like saying "if ntp isn't running, start it and run chkconfig ntpd on" for example, because I don't like the idea of running the chkconfig on command unless I have tested the condition. My preference is for cfengine to not repair any promise without first testing whether the promise is not kept. _______________________________________________ Help-cfengine mailing list Help-cfengine@cfengine.org https://cfengine.org/mailman/listinfo/help-cfengine
