cf-execd is the scheduler that is responsible for executing the agent (cf-agent) at the scheduled intervals (by default 5 every minutes). By default cf-agent will start cf-execd, cf-serverd and cf-monitord if they aren't running. Instead of putting cf-execd in inittab you could add a cron job that runs cf-agent at less frequent intervals. To be honest though, I haven't had any problems with cf-execd crashing in quite some time. It's been extremely stable for me for at least the past three years. -- Brian Bennett Looking for CFEngine training? http://www.verticalsysadmin.com/ On Jul 22, 2014, at 7:33 AM, Lorenzo Beretta <lory.fulgi@infinito.it> wrote: > On 07/21/2014 02:39 PM, Jimmy Thrasibule wrote: >> Hi, >> >> I've added a new line to the /etc/inittab file to monitor the CFEngine >> daemon and restart it in case this one dies. >> >> cfe:2345:respawn:/var/cfengine/bin/cf-execd >> >> The cf-execd is re-spawned as expected, except the fact that multiple >> processes are created at once. >> >> I therefore have about 20+ cf-execd processes running where I only need 1. >> >> Any idea what's causing this and how to solve it? >> >> Regards, >> Jimmy >> > If you start things from /etc/inittab, you must make sure they do not fork; I have no idea what cf-execd does, but its manpage mentions the --no-fork option :) > (If a process in inittab is spawned more than N times, init will stop respawining it for a while) > > -- > You received this message because you are subscribed to the Google Groups "help-cfengine" group. > To unsubscribe from this group and stop receiving emails from it, send an email to help-cfengine+unsubscribe@googlegroups.com. > To post to this group, send email to help-cfengine@googlegroups.com. > Visit this group at http://groups.google.com/group/help-cfengine. > For more options, visit https://groups.google.com/d/optout.
Attachment:
smime.p7s
Description: S/MIME cryptographic signature