> >> It's called ccs_sync and is part of the ricci package. > >> > >> cman_tool will automatically call this (if it's installed) when you > >> update the version number and call 'cman_tool version'. > > > > Ok, found that code. Seems that ricci does the following: > > > > - generate new config files and then call cman_set_version() > > > > - all nodes get informed via cman corosync message that there > > is a new config file available (somewhere). > > > > But who calls 'cman_tool version' to actually sync the config? > > You do ;-)
Really? I have to connect to each node and call 'cman_tool version'? > > And why do you use an asynchrounous, unreliable transport (ccs_sync) > instead > > of corosync to distribute the config? > > > > > Because corosync isn't necessarily running But cman_set_version() only works if corosync is running? - Dietmar _______________________________________________ Openais mailing list [email protected] https://lists.linux-foundation.org/mailman/listinfo/openais
