How do you do this? Do you alter the config file in majordomo or just change the aliases in the alias file in the backup machine so that the listname: listname@primary-mx.dom is achieved.
- Sujit
-----Original Message-----
From: Burt Juda [mailto:burt@juda.com]
Sent: Fri 06/06/2003 17:26
To: majordomo-users@greatcircle.com
Cc:
Subject: Re: Keeping lists in two machines in sync.
Then there is the possibility that a change could be made on each
server. One would be lost during the rsync. You can only do the rsync
in one direction at a time.
What I did in this situation is to run a script on the backup to rewrite
the majordomo list aliases to specifically point to the primary
machine. ie:
majordomo: majordomo@primary-mx.dom
listname: listname@primary-mx.dom
This would queue up any mail for majordomo or lists 'til the primary
came back online, but there was NO possiblilty of anything getting out
of sync.
- Burt
Deb wrote:
>Is there some reason you shouldn't/couldn't use rsync on *both* sides, to
>synchronize both servers? Use options to only update files that are newer...
>
>d
>
>Sujit Choudhury <S.Choudhury@westminster.ac.uk> had this to say,
>
>
>
>>Dear All,
>>We have two MTA - one the main one and the other the backup one. MX record for the main one is lower than the backup one. However we are running majordomo on both the machines. This causes one small problem. Sometimes the secondary MTA's majordomo files are updated if the request reaches the secondary MTA.
>>I use rsync to maintain any changes in the primary MTA's majordomo files are reflected in the secondary MTA, however have no idea how to keep both of them in sync.
>>
>>Any help would be appreciated.
>>
>>Many thanks
>>
>>Sujit Choudhury
>>
>>
>
>
>
Follow-Ups:
|
|
