I make a special class in cfengine that detects if a new version is
available. If so, then it submits an at job that does the full upgrade.
Since it is in an at job, killing all the cfengine daemons doesn't
hurt the job doing the upgrade. (I usually use package management
of some form or another to simplify the actual upgrade.)
So in my case the procedure would be:
Submit at job that:
* kills old cfengine programs
* Installs new package
* restarts cfexecd (which restarts the other daemons in my case).
I actually used this to migrate from cfengine 1 to cfengine 2.
_______________________________________________
Help-cfengine mailing list
Help-cfengine@gnu.org
http://lists.gnu.org/mailman/listinfo/help-cfengine