and many thanks. But just another precision :
you mean that ccs_sync is making the job
now , in a hidden way when cman_tool -r version is
executed , right ?
but does the fact that cluster.conf is in another place
than /etc/cluster matter for ccs_sync to work fine ?
because I just tried :
[root oberon3 ~]# ccs_sync help
Unable to parse /etc/cluster/cluster.conf: No such file or directory
Does that mean that ccs_sync does not take in account the
/etc/sysconfig/cman file ?
Fabio M. Di Nitto a écrit :
On Fri, 2009-09-04 at 11:46 +0200, Alain.Moulle wrote:Hi, With this release : cman-3.0.2-1.fc11.x86_64 it seems that we can't do ccs_tool update anymore : ccs_tool update /etc/cluster/cluster.conf Unknown command, update. Try 'ccs_tool help' for help. and effectively the help does not list anymore options update (neither upgrade). Therefore, what is the new way to make it dynamically update the configuration ?The configuration distribution across nodes is now delegate to luci/ricci via ccs_sync command. The old ccsd ccs_tool bits are gone. Assuming your configuration is identical on all nodes you can issue, on one node only, cman_tool version -r $newversion. $newversion is either 0 (autodetect the version from cluster.conf and check that is newer/higher than the runtime config) or the exact version you want to load. Note that we are still working on smoothing a few corners in the new configuration system and that a bad config could be problematic for the cluster. Fabio