On 2007-04-04T11:41:44, Doug Knight <[EMAIL PROTECTED]> wrote:
> The key word in my question was "thinks". It would be useful to the RA
> if it could know what state the CRM thought it was in, so in case the RA
> determines on its own that its already in that state, it doesn't have to
> do anything. But, if the RA finds that the CRM thinks its in a different
> state, then the RA could set the CRM straight by calling the crm_master
> with the appropriate value. Make sense?
No. The state the resource is in is not set via crm_master, but using
the exit code of the monitor operation.
You should only call crm_master when you wish to change the _preference_
for master-state.
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-Dev: [email protected]
http://lists.linux-ha.org/mailman/listinfo/linux-ha-dev
Home Page: http://linux-ha.org/
