|
> I've heard some reports of problems with this. The ldirectord.cf
> rereading code works by making a checksum of the file and rereading
> it if the checksum changes. This should be pretty foolproof, but
> perhaps there is a bug.
>
> I am assuming you have autoreload = yes in the ldirectord.cf file
> when you start up ldirectord.
Horms, can you think of any reason why autoreload SHOULD be set to yes in a
production environment? Sending a -HUP signal seems to be a better solution
all around?
/etc/ha.d/update
#!/bin/sh
# next, scp the ldirectord.cf file over to the other director
scp /etc/ha.d/conf/ldirectord.cf LVS2:/etc/ha.d/conf/.
# reload ldirectord
killall -HUP ldirectord
P
|
