On 9/20/07, Junko IKEDA <[EMAIL PROTECTED]> wrote: > > > > the code is still there and looks to be enabled > > > > > > > > it works by checking the RA's metadata^... > > > > > > > > * your RA must advertise the reload action > > > > * the attribute you want to be able to change must specify: > unique="false" > > > > > > I'm sorry to ask you right off. > > > Where should I specify unique="false" in cib.xml? > > > > no in the CIB. > > it goes in the RA metadata. eg. > > vvvvvvvvv > > <parameter name="dampen" unique="0"> > > <longdesc lang="en"> > > The time to wait (dampening) further changes occur > > </longdesc> > > <shortdesc lang="en">Dampening interval</shortdesc> > > <content type="integer" default="1s"/> > > </parameter> > > I see... > This way is a bit difficult, I might not be able to ask user lightly to do > that.
users shouldn't be doing this... its the job of the people writing the RA > > > > It seems more likely that the value can be changed several times. > > > I'd appreciate it if this function is improved. > > > > the metadata is cached, not the value. the metadata should only > > rarely need to change > > ok, it seems like our request is against the concept of metadata. you've lost me. you want changes to a resource's attribute to be sent to the resource but not cause a restart.... thats exactly what this does. what you can't do is have the attribute behave one way and then the other later on. either an attribute needs a restart to take effect or not - and the person writing the RA should decide that, not the user _______________________________________________ Linux-HA mailing list [email protected] http://lists.linux-ha.org/mailman/listinfo/linux-ha See also: http://linux-ha.org/ReportingProblems
