Thanks Rob for your answer so far. Concerning the replication process,
we where thinking about using something like heartbeat to monitor the
service. Once the master has been found inoperative, heartbeat should
promote one of the replica as master, by running a script to restart the
replica in
On Mon, 24 Feb 2003, Etienne Goyer wrote:
Thanks Rob for your answer so far. Concerning the replication process,
we where thinking about using something like heartbeat to monitor the
service. Once the master has been found inoperative, heartbeat should
promote one of the replica as master,
Greeting again,
I would have another question concerning MUPDATE. The white-paper on
Cyrus imapd Murder hinted about the possibility(1) of having your MUPDATE
server replicating. If it is available, I would like to replicate the
MUPDATE server for both scalability and automatic failover,
On Fri, 21 Feb 2003, Etienne Goyer wrote:
I would have another question concerning MUPDATE. The white-paper on
Cyrus imapd Murder hinted about the possibility(1) of having your MUPDATE
server replicating. If it is available, I would like to replicate the
MUPDATE server for both scalability
