On Fri, Jul 4, 2008 at 08:50, Patrik Martinsson
<[EMAIL PROTECTED]> wrote:
> Hello Steve.
>
> I use the same method to update my cib, exect for everey update i do i
> increase the admin_epoch number to a higher one
> <cib admin_epoch="0" epoch="0" num_updates="0"> would mean in my new cib
> <cib admin_epoch="1" epoch="0" num_updates="0">then i use the -R -x flag to
> cibadmin, like cibadmin -R -x mynewcib.xml
>
> Althou i read in the pdf Micheal Alger sent this following, (that seems to
> be a VERY good document btw. thanks for that one)
>
> *admin_epoch *
> *Never modified by the cluster. Use this to make the configurations on any
> inactive nodes obsolete.
> Never set this value to zero, in such cases the cluster cannot tell the
> difference between your
> configuration and the "empty" one used when nothing is found on disk.*
>
> *epoch*
> *Incremented every time the configuration is updated (usually by the admin)*
>
> *num_updates*
> *Incremented every time the configuration or status is updated (usually by
> the cluster)*
>
> So maybe i shiould try increasing epoch instead of admin_epoch, i´ll try
> that later.
either will work.
basically the "version" is: {admin_epoch}.{epoch}.{num_updates}
_______________________________________________
Linux-HA mailing list
[email protected]
http://lists.linux-ha.org/mailman/listinfo/linux-ha
See also: http://linux-ha.org/ReportingProblems
