[Linux-HA] Constraint Listing / RestartAfterSuccessfulRecovery constraint?

[Robert Heinzmann]

Thanks for the response Serge.

There's another question poppin into my mind. There are also other 
resources, that do not need a restart after the restart of a resource 
they depend on. E.g. Apache and IP. If the IP is restarted, apache does 
not need a restart (I guess :). I guess from your response that in this 
case (to avaoid aditional down time), I do not put IP and Apache in a 
group, but define them as single resources and connect them with 
constraints.

Is that true ?

Robert

Serge Dubrouski schrieb:
> Combine your resources into a group. Database fist and then resources
> that depend on it. In this case restart of the database will cause
> restart of the resources.
>
> On 10/15/06, Robert Heinzmann <Robert.Heinzmann at gmx.net> wrote:
>> Hello,
>>
>> is there a listing of all constraints available in Heartbeat on the 
>> web ?
>>
>> I'm looking for a kind of "Restart after failed" constraint. This should
>> restart resources (A) after a successful restart of a resource (B). Lets
>> say B is a database and A is an application, there are applications that
>> fail to reconnect to the database. In those cases a restart of the
>> application may be required AFTER the database has successfully
>> restartet. Is there such a constraint available in Heartbeat 2 ?
>>
>> Regards,
>> Robert
>> _______________________________________________
>> Linux-HA mailing list
>> Linux-HA at lists.linux-ha.org
>> http://lists.linux-ha.org/mailman/listinfo/linux-ha
>> See also: http://linux-ha.org/ReportingProblems
>>
> _______________________________________________
> Linux-HA mailing list
> Linux-HA at lists.linux-ha.org
> http://lists.linux-ha.org/mailman/listinfo/linux-ha
> See also: http://linux-ha.org/ReportingProblems
>
>