#
# /etc/ha.d/ha.cf
# 
# ha.cf file to configure two nodes connected by ethernet (eth0) and
# a null modem (/dev/ttyS0). 
#
# Based on sample ha.cf shipped with heartbeat
#
# Prepared: April 2000
#


#
#	There are lots of options in this file.  All you have to have is a set
#	of nodes listedJ {"node ...}
#	and one of {serial, udp, or ppp-udp}
#
#	Note on logging:
#	If any of debugfile, logfile and logfacility are defined then they
#	will be used. If debugfile and/or logfile are not defined and
#	logfacility is defined then the respective logging and debug
#	messages will be loged to syslog. If logfacility is not defined
#	then debugfile and logfile will be used to log messges. If
#	logfacility is not defined and debugfile and/or logfile are not
#	defined then defaults will be used for debugfile and logfile as
#	required and messages will be sent there.
#
#	File to wirte debug messages to
debugfile /var/log/ha.d/debug
#
#
# 	File to write other messages to
#
logfile	/var/log/ha.d/log
#
#
#	Facility to use for syslog()/logger 
#
#logfacility	local0
#
#	keepalive: how many seconds between heartbeats
#
keepalive 2
#
#	deadtime: seconds-to-declare-host-dead
#
deadtime 5
#	hopfudge maximum hop count minus number of nodes in config
#hopfudge 1
#	
#	serial	serialportname ...
serial	/dev/ttyS0
#
#	Only for serial ports.  It applies to both PPP/UDP and "raw" ports
#
#	This means run PPP over ports ttyS1 and ttyS2
#	Their respective IP addresses are as listed.
#	Note that I enforce that these are local addresses.  Other addresses
#	are almost certainly a mistake.
#ppp-udp	/dev/ttyS1 10.0.0.1 /dev/ttyS2 10.0.0.2
#
#	Baud rate for both serial and ppp-udp ports...
#
baud	19200
#
#	What UDP port to use for udp or ppp-udp communication?
#
udpport	694
#
#	What interfaces to heartbeat over?
#
udp	eth0
#
#	Watchdog is the watchdog timer.  If our own heart doesn't beat for
#	a minute, then our machine will reboot.
#
#watchdog /dev/watchdog
#
#	Nice_failback sets the behavior when performing a failback:
#
#	- if it's on, when the primary node starts or comes back from any
# 	  failure and the cluster is already active, i.e. the secondary
# 	  server performed a failover, the primary stays quiet, acting as a
# 	  secondary.  This way some operations like syncing disks can be
# 	  easily done.  
#	- if it's off (default), the primary node will always be the
#	  primary, whenever it's powered on.
#
nice_failback off
#
#	Tell what machines are in the cluster
#	node	nodename ...	-- must match uname -n
node	balancer01.directadvice.com
node	eabalancer.directadvice.com