Dave Dykstra wrote: > On Mon, May 07, 2007 at 11:15:49AM +0200, Dejan Muhamedagic wrote: >> On Fri, May 04, 2007 at 02:01:24PM -0500, Dave Dykstra wrote: > ... >>> And of course /etc/init.d scripts don't support a 'status' parameter. >>> You really need to write your own /etc/ha.d/resources script. >>> I don't quite understand why heartbeat can't skip the status checks >>> for /etc/init.d scripts. Either that or it shouldn't claim to support >>> /etc/init.d scripts. >> How should a cluster work without being able to check the status >> of resources? > > It's probably just my ignorance as to why this isn't good enough, > but I would think that the cluster software could assume that services > it started were running and that services it stopped were stopped.
It could. But then it couldn't really claim to provide *resources* high-availability, only *node* high availability. That's what Hearbeat 1.x does. One of the major enhancements of 2.x is that it truly monitors resources, and can offer much higher availability for each individual resource. _______________________________________________ Linux-HA mailing list [email protected] http://lists.linux-ha.org/mailman/listinfo/linux-ha See also: http://linux-ha.org/ReportingProblems
