Hi! After the preceeding discussion about the "reload" action I added a "reload" to my RA. Now I have another problem: Assume the configuration
group G A B Both A, and B are the same RA that support reload. If I change the configuration of A, CRM stops B first, the reloads A, then starts B again. This makes me wonder what the reasoning for "reload" is at all. In normal cases, a reload avoids a restart of a resource. So if A isn't restartet, why is B then? I was hoping: if A can be reloaded, B can stay up. Regards, Ulrich _______________________________________________ Linux-HA mailing list [email protected] http://lists.linux-ha.org/mailman/listinfo/linux-ha See also: http://linux-ha.org/ReportingProblems
