On Wed, Apr 16, 2008 at 3:44 PM, Michael Schwartzkopff <[EMAIL PROTECTED]> wrote: > Am Mittwoch, 16. April 2008 15:37 schrieb Andrew Beekhof: > > > On Wed, Apr 16, 2008 at 3:07 PM, Michael Schwartzkopff > (...) > > > Ok, so right now Dummy only takes one parameter called "state" (no > > idea why I called it that). > > Add a new one, but make it non-unique. > > > > <parameter name="somename" unique="0"> > > <longdesc lang="en"> > > Random parameter that, when changed, causes a reload instead of a restart > > </longdesc> > > <shortdesc lang="en">Some parameter</shortdesc> > > <content type="string" default="" /> > > </parameter> > > > > And make sure the agent advertises the reload operation: > > > > <action name="reload" timeout="90" /> > > > > Then when defining the resource, include an nvpair for "somename". eg > > > > <primitive class="ocf" id="test" > provider="heartbeat" type="Dummy"> > > <instance_attributes id="test"> > > <attributes> > > <nvpair id="test_someename" > name="someename" value="a"/> > > </attributes> > > </instance_attributes> > > </primitive> > > > > Then just change the value of "somename" and the resource will get > > reloaded. > > I think I got it. The point is, that the resource is reloaded on every change > of any attribute. Isn't it?
Not of any, just of anything with unique=0. Consider an IP resource.... changing the MTU could be done with a reload but changing the IP needs a restart. _______________________________________________ Linux-HA mailing list [email protected] http://lists.linux-ha.org/mailman/listinfo/linux-ha See also: http://linux-ha.org/ReportingProblems
