On 14/04/11 19:58, Bas van der Vlies wrote: >> >> >> 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?
The server rereads automatically. > 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 ;-) > Yes, agreed. Originally there was a technical issue we did not understand how to solve which is why execd and monitord do not reread their configs. We now understand these issues better and it will be implemented sometime when a suitable moment is reached. If we could only reconfigure the solar system so that the day was slightly longer, we might have a chance with these things ;-) M _______________________________________________ Help-cfengine mailing list Help-cfengine@cfengine.org https://cfengine.org/mailman/listinfo/help-cfengine
