The reference states that "You should never put cf-agentor cf-agent directly inside cron without the cf-execd wrapper."[sic] I'm not certain that I see the logic in this. In my policies I have a processes promise that ensures that cf-execd is running. As a backup also like to have a crontab entry to start cf-execd if it is not running. This leads to a bit of a logic problem.
If cf-execd is started in cron with -F it runs once and exits. Since it shows up the process table the promise for a running cf-execd is kept. If cf-execd is started in cron without -F multiple processes begin to accumulate with each cron run. If cf-agent is started in cron then the promise of cf-execd will repair and start cf-execd properly. How do others handle this? Sincerely, -- Neil Watson 416-673-3465
CONFIDENTIALITY WARNING This communication, including any attachments, is for the exclusive use of addressee and may contain proprietary and/or confidential information. If you are not the intended recipient, any use, copying, disclosure, dissemination or distribution is strictly prohibited. If you are not the intended recipient, please notify the sender immediately by return e-mail, delete this communication and destroy all copies. AVERTISSEMENT RELATIF À LA CONFIDENTIALITÉ Ce message, ainsi que les pièces qui y sont jointes, est destiné à l’usage exclusif de la personne à laquelle il s’adresse et peut contenir de l’information personnelle ou confidentielle. Si le lecteur de ce message n’en est pas le destinataire, nous l’avisons par la présente que toute diffusion, distribution, reproduction ou utilisation de son contenu est strictement interdite. Veuillez avertir sur-le-champ l’expéditeur par retour de courrier électronique et supprimez ce message ainsi que toutes les pièces jointes.
_______________________________________________ Help-cfengine mailing list Help-cfengine@cfengine.org https://cfengine.org/mailman/listinfo/help-cfengine
