On 2007-05-19T09:18:28, Yan Fitterer <[EMAIL PROTECTED]> wrote:
> Try without --meta then ! --meta is only there to help hb make the
> difference between parameters that should trigger resource restarts,
> and those that don't AFAIK.
That's not quite right, even though this is one of the effects.
The --meta moves the attribute into a different namespace, which makes
it clear that it is not a regular instance attribute.
This is useful because we can basically add to this whatever we want,
without clashing with attribute names used by the resource agents
themselves - and thus not having to restart them to get the RA up and
running with the new attributes.
But, some of the meta attributes - changes to target_role, clone_max and
maybe others - might still cause some resource actions to be issued.
Thanks,
Lars
--
Teamlead Kernel, SuSE Labs, Research and Development
SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg)
"Experience is the name everyone gives to their mistakes." -- Oscar Wilde
_______________________________________________
Linux-HA mailing list
[email protected]
http://lists.linux-ha.org/mailman/listinfo/linux-ha
See also: http://linux-ha.org/ReportingProblems
