You should be able to instruct the agent to restart cf-execd when the
policy changes -- even though it is run by it. Cfengine is one of those
pesky children that can go back in time and kill its parent!
On 12/26/2010 10:26 PM, Tom Tucker wrote:
> Should I consider running my Linux cf-execd proce
rum: Cfengine Help
> Subject: Re: Reloading cf-execd after cf-execd.cf changes
> Author: neilhwatson
> Link to topic: https://cfengine.com/forum/read.php?3,18778,18779#msg-18779
>
> I think that having agents reload changed configs is on the map but right
> now killing and restarted
Forum: Cfengine Help
Subject: Re: Reloading cf-execd after cf-execd.cf changes
Author: neilhwatson
Link to topic: https://cfengine.com/forum/read.php?3,18778,18779#msg-18779
I think that having agents reload changed configs is on the map but right now
killing and restarted is the only sure way
Is there a "right" way to promise that cf-execd is using an up to date promise
definition? I have recently taken the "-I" out of the command string it is
using to start cf-agent periodically, but the running instance on my server is
still mailing me with more verbose output than I want. Sending
