On 2007-04-10T11:08:56, Bernd Schubert <[EMAIL PROTECTED]> wrote:
> > Ugh. Even probe shouldn't always return "not running", but the actual
> > state. This seems like a weird work-around for an otherwise broken
> > monitor action, or am I missing something ...?
>
> Well, once OCF_RESKEY_interval was set, it didn't return "not running", of
> course. The variable was/is mis-used to tell heartbeat that a resource
> started *before* the startup of the heartbeat-resource-groups shall only be
> monitored.
> So on the startup of the resource group, it shall not be killed first and it
> shall not have an effect on the other members of this resource group.
I'm missing the point here.
But when you return the proper status - running, failed, not running -,
heartbeat should do the "right thing" automatically when it finds the
resource active prior to heartbeat being (re-)started?
Sincerely,
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
Linux-HA@lists.linux-ha.org
http://lists.linux-ha.org/mailman/listinfo/linux-ha
See also: http://linux-ha.org/ReportingProblems
