Christian Charles wrote: > Dejan Muhamedagic wrote: >> Hi, >> >> On Fri, Jan 23, 2009 at 02:42:35PM +0100, Christian Charles wrote: >> >>> Hello, >>> >>> i used the guide at http://www.linux-ha.org/PingdWithMultipleNetworks >>> to monitor connectivity to 2 different nets and it works. >>> >>> I don't like that i have to create copies of /usr/lib/heartbeat/pingd >>> though, since it means i have to remember to update these copies >>> manually, when i update heartbeat. >>> >> >> Not necessarily ... >> >> >>> Is there an alternative way? >>> >>> I have tried so far without success: >>> 1) Symlinking: >>> cd /usr/lib/heartbeat >>> ln -s pingd pingdnet1 >>> ln -s pingd pingdnet2 >>> >> >> ... you can try with hard links. >> > You are right, that should work and solve my update issue. Thanks! >> >>> 2) Using just one copy of pingd and configuring ha.cf like this: >>> respawn root /usr/lib/heartbeat/pingd -a pingdnet1 -m 100 -d 5s -p >>> /var/run/pingdnet1.pid -h a.a.a.a -h b.b.b.b -h c.c.c.c >>> respawn root /usr/lib/heartbeat/pingd -a pingdnet2 -m 100 -d 5s -p >>> /var/run/pingdnet1.pid -h x.x.x.x -h y.y.y.y -h z.z.z.z >>> >> >> Is this a typo: You specified the same pid file for both.
oops ;) > Yes it is a typo, originating from the webpage mentioned above. Maybe it > made its way into my actual configuration, i'll go and try this again. > I'm still wondering: Why does that guide suggest to make copies of the > pingd binary in the first place? Why not specify multiple respawn > directives with the same program and different arguments? Maybe that's > just not the way how respawn works? Well, not that I'm saying I remembered exactly, but I'm sure I tried other ways before writing that document. Today, there are other options to achieve what the howto's goal is. You don't have to copy/rename/link the executable any more. crm configure primitive pingdnet1 ocf:pacemaker:pingd params host_list=10.2.50.11 name=pingdnet1 pidfile=/var/run/pingdnet1.pid multiplier=100 clone cl-pingdnet1 pingdnet1 meta globally-unique=false primitive pingdnet2 ocf:pacemaker:pingd params host_list=10.2.60.11 name=pingdnet2 pidfile=/var/run/pingdnet2.pid multiplier=100 clone cl-pingdnet2 pingdnet2 meta globally-unique=false commit quit The constraints should still be valid. We'd have to agree on whether that should go into that howto or on the clusterlabs wiki. Regards Dominik _______________________________________________ Linux-HA mailing list [email protected] http://lists.linux-ha.org/mailman/listinfo/linux-ha See also: http://linux-ha.org/ReportingProblems
