> > > Note that, in cf3, cf-agent can restart cf-execd in policy, by a > kill/restart. This was not possible in cf2. > This allows a more controlled restart than just looking at the time stamp. >
I am still used to cf2 behavior ;-). Does cf3 reread the configuration of cf-serverd daemon or must this daemon also be killed/restarted? cf3 knows when the configuration is changed due to cf-promises caching. So if the configuration is changed it would be useful/handy if the daemon reread their configuration files. Saves me a complex update.cf script ;-) -- Bas van der Vlies b...@sara.nl _______________________________________________ Help-cfengine mailing list Help-cfengine@cfengine.org https://cfengine.org/mailman/listinfo/help-cfengine
