That is what I feared. My heartbeat implementation doesn't include crm/cib features, (perhaps in the next version) so I guesss I'll have to find something else. Thanks for your support anyway, Lars ;)
On Mon, Jun 2, 2008 at 8:04 PM, Lars Marowsky-Bree <[EMAIL PROTECTED]> wrote: > On 2008-06-02T16:56:29, Nuno Covas <[EMAIL PROTECTED]> wrote: > >> Greetings, >> >> I have a Heartbeat implementation that may need to deal with non-idle >> resources at startup and be able to stop them in case they are already >> being served. It is not critical that both machines cannot serve the >> same resource for a limited amount of time, but it is bad if heartbeat >> doesn't actively stop the resource. >> >> Is there any way HB can actively stop a non-idle resource at startup? > > Heartbeat 2.x and Pacemaker both already do exactly this. > > There's a "multiple_active" setting which details how to deal with this > case - the default is to stop them all and start one, if I'm not > mistaken. > > Happy to serve ;-) > > > Regards, > Lars > > -- > Teamlead Kernel, SuSE Labs, Research and Development > SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg) > "Experience is the name everyone gives to their mistakes." -- Oscar Wilde > > _______________________________________________ > Linux-HA mailing list > [email protected] > http://lists.linux-ha.org/mailman/listinfo/linux-ha > See also: http://linux-ha.org/ReportingProblems > _______________________________________________ Linux-HA mailing list [email protected] http://lists.linux-ha.org/mailman/listinfo/linux-ha See also: http://linux-ha.org/ReportingProblems
