--- On Tue, 3/24/09, foxyc...@yahoo.com wrote:
> ... what command should I type to cause the cluster to
> perform a "monitor" operation at a specific check level on
> that resource, and return the appropriate OCF status of the
> operation, *without* the cluster reacting like triggering a
> failo
--- On Fri, 3/27/09, Andrew Beekhof wrote:
>>> I saw later that you want to prevent the cluster
>>> from doing anything for the resource, simply set
>>> is-managed=false for the resource in question.
>> This is incorrect. I want the cluster to react to
>> everything BUT to this specific invoca
--- On Thu, 3/26/09, Andrew Beekhof wrote:
>> what command should I type to cause the cluster
>> to perform a "monitor" operation at a specific check
>> level on that resource, and return the appropriate
>> OCF status of the operation, *without* the cluster
>> reacting like triggering a fai
Hi Dominik!
dk at in-telegence wrote:
>> I'd love to see something like:
>>
>> # crm_resource -m check_level resource_id
>> ..
>
>This should be possible:
>
>export OCF_ROOT=/usr/lib/ocf
>export OCF_RESKEY_=
>export OCF_RESKEY_=
>$OCF_ROOT/resource.d// monitor
>echo $?
Thanks, but I'm afraid y
>> I'd love to see something like:
>>
>> # crm_resource -m check_level resource_id
>> ..
I forgot to add that a -f option switch to cause the failover if the monitor
operation failed would be cool too.
___
Pacemaker mailing list
Pacemaker@o
