Hi Andrew, I meant "stopped" by target-role : crm resource respingal2 stop You mean that the behavior of collocation is only valuable for status failed event ? Not in case of voluntary crm stop commands ? Thanks Alain > > so I did some simple scripts /pingalain1/ (resource respingal1) and > /pingalain2/ (resource > > respingal2) which have for sure status eq 0 gathered in a group > /groupresping/ : > > crm configure group groupresping respingal1 respingal2 and so my > problem is > > that : > > > > 1/ when both respingal1 and respingal2 are successfully started/running, > > if I stop respingal1, both resources are stopped. (Fine for me) > > 2/ when both respingal1 and respingal2 are successfully started/running, > > if I stop respingal2, there is no impact on respingal1. (Not fine > for me > > ...) > > stopped how? with target-role or by killing the actual service?
_______________________________________________ Linux-HA mailing list [email protected] http://lists.linux-ha.org/mailman/listinfo/linux-ha See also: http://linux-ha.org/ReportingProblems
