Automatic master/consumer initialization
>_______________________________________
>From: 389-users-bounces@lists.fedoraproject.org [389-users-bounces@lists.fedoraproject.org] on behalf of Rich Megginson [rmeggins@redhat.com]
>Sent: 24 August 2010 02:31
>To: General discussion list for the 389 Directory server project.
>Subject: Re: [389-users] Automatic master/consumer initialization
>
>Gerrard Geldenhuis wrote:
>> Hi
>> Is there any difference between right clicking on a replication agreement just created and selecting the Initialize Consumer or letting "nature" go its course and >>letting replication happen in the next "cycle".
>>
>> Up until now I have created replication agreements using the GUI, but I have now started doing it via ldif files. If I don't immediately run:
>> dn: cn=%repl-agreement-name%,cn=replica,cn=dc3dCompany,cn=mapping tree,cn=config
>> changetype: modify
>> replace: nsds5beginreplicarefresh
>> nsds5beginreplicarefresh: start
>>
>> It seems to start on its own anyway. Having checked the data nothing looks wrong so I thought I would just double check.
>>
>Doing nsds5beginreplicarefresh: start does a replica init. A consumer
>must be initialized before a supplier can begin updating it. If you
>have already initialized a consumer from another supplier/master, you
>don't need to initialize it again.
Thanks, I just realized that I was seeing the same data on all servers because of the way that I accessed the console remotely, which is why I thought that it had automatically initialized itself.
Regards
__________________________________________________ ______________________
In order to protect our email recipients, Betfair Group use SkyScan from
MessageLabs to scan all Incoming and Outgoing mail for viruses.
__________________________________________________ ______________________
--
389 users mailing list
389-users@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/389-users
|
