Hi
I used the pingd rsc_location from
http://www.linux-ha.org/pingd
<rsc_location id="my_resource:connected" rsc="my_resource">
<rule id="my_resource:connected:rule" score="-INFINITY" boolean_op="or">
<expression id="my_resource:connected:expr:undefined"
attribute="pingd" operation="not_defined"/>
<expression id="my_resource:connected:expr:zero"
attribute="pingd" operation="lte" value="0"/>
</rule>
</rsc_location>
Now I wanted to play with it a little bit and used the GUI to change
value from "0" to "2". This ended up in a rsc_location constraint which
did not have the boolean_op="or" option. It had no such option set so it
used the default "and" (instead of "or" before).
As I am not a programmer and I do not read the DEV-list, I wanted to at
least let you know that this is kind of a problem and not easy to debug
why the constraint does not work any more after changing it with the GUI.
Regards
Dominik
_______________________________________________
Linux-HA mailing list
[email protected]
http://lists.linux-ha.org/mailman/listinfo/linux-ha
See also: http://linux-ha.org/ReportingProblems
