Hello, Well, I have successfully writen an application that sends messages via the heartbeat API. I'm using two interfaces for the heartbeat, serial (ttyS0) and unicast (eth0). I'm very happy with how things are working...in particular, my messages get through even if one of the two interfaces is down. Here's my question.
How does heartbeat decide which interface (serial or TCP/IP) to use for a message (via my application written over the API, using ll_cluster_new() and friends)? Is there a way to force the use of one over the other? Thanks! Scott Mann Sr Software Engineer Aztek Networks _______________________________________________ Linux-HA mailing list [email protected] http://lists.linux-ha.org/mailman/listinfo/linux-ha See also: http://linux-ha.org/ReportingProblems
