Ulrich.Windl at rz
Dec 1, 2011, 4:48 AM
Post #4 of 5
>>> Tim Serong <tserong [at] suse> schrieb am 01.12.2011 um 10:19 in Nachricht
<4ED74691.9000007 [at] suse>:
> On 12/01/2011 09:10 AM, Ulrich Windl wrote:
>>>>> "Gao,Yan"<ygao [at] suse> schrieb am 01.12.2011 um 06:55 in Nachricht
> > <4ED716BE.9090802 [at] suse>:
> >> Hi,
> >> On 11/30/11 21:35, Ulrich Windl wrote:
> >>> Hi!
> >>> Simple question: when is the attribute "cib-last-written" in XML's "cib"
> >> element updated?
> >> When "//cib/configuration" is changed.
> > So why isn't that an attribute of<configuration> then?
> "The reason for these fields to be placed at the top level instead of
> with the rest of cluster options is simply a matter of parsing. These
> options are used by the configuration database which is, by design,
> mostly ignorant of the content it holds. So the decision was made to
> place them in an easy to find location."
I wonder about that usefulness of that value, especially as any configuration change seems to increase the epoch anyway. I never saw that CRM cares about the cib-last-written string.
When talking about "easy to find locations", it was a mistake to use XML anyway ;-)
Linux-HA mailing list
Linux-HA [at] lists
See also: http://linux-ha.org/ReportingProblems