My concern with having cfagent or a child thereof perform the update is this scenario: 1. cfexecd launches cfagent 2. Something called by cfagent (cf.preconf, shellcommand, proceses, etc) notices the change and kills cfexecd and cfservd in preparation for restarting them 3. cfexecd gets the kill signal and exits 4. cfagent gets a signal that cfexecd exited and exits. If it was performing the change, it exits before cfexecd is restarted. 5. If cf.preconf was performing the change, it gets a signal that cfagent exited and exits before cfservd / cfexecd is restarted. <splat>
If that happens I would have to either resurrect everything via cfservd or get several people to each log in to a lot of machines to manually restart it. It is most preferential to avoid the latter :> The procedure I had in mind was: 1. cfexecd launches cfagent 2. cfagent overwrites cfagent / cfexecd / cfservd with the updated version. 3. cfagent kills and restarts cfservd 4. cfagent exits 5. cfagent is invoked via cfservd 6. cfagent kills and restarts cfexecd 7. Finish Has anyone tried that? Thank you, -Jason Martin > -----Original Message----- > From: David Masterson [mailto:[EMAIL PROTECTED] > Sent: Tuesday, October 25, 2005 1:19 PM > To: Martin, Jason H; help-cfengine@gnu.org > Subject: RE: Upgrading CFE with CFE > > > Martin, Jason H wrote: > > Does anyone have any experience with upgrading large > installations of > > CFE with CFE? Was there any particular order in which you > pushed the > > three components? Are there any gotchas if you are using > cfexecd to > > launch cfengine instead of cron? > > Is this something you would use "cf.preconf" for? > -- > David Masterson > VMware, Inc. > Palo Alto, CA > _______________________________________________ Help-cfengine mailing list Help-cfengine@gnu.org http://lists.gnu.org/mailman/listinfo/help-cfengine
