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 process from cron instead of > Linux services to side step this issue? > Granted the cf-execd.cf <http://cf-execd.cf> is one of those > infrequently modified files, but having to kill and restart sounds > undesirable to me. > > On Mon, Oct 18, 2010 at 11:58 AM, <no-re...@cfengine.com > <mailto:no-re...@cfengine.com>> wrote: > > Forum: Cfengine Help > Subject: Re: Reloading cf-execd after cf-execd.cf > <http://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. > > _______________________________________________ > Help-cfengine mailing list > Help-cfengine@cfengine.org <mailto:Help-cfengine@cfengine.org> > https://cfengine.org/mailman/listinfo/help-cfengine > > > > > _______________________________________________ > Help-cfengine mailing list > Help-cfengine@cfengine.org > https://cfengine.org/mailman/listinfo/help-cfengine _______________________________________________ Help-cfengine mailing list Help-cfengine@cfengine.org https://cfengine.org/mailman/listinfo/help-cfengine
