On 11/08/2011 06:11 PM, Tom Tucker wrote:
You might be able to enable some sort of changelog on the SunDS, or enable the audit log. Both of these will allow you to grab only the changes, in LDIF format, which you can then use ldapmodify to apply to your 389 server. When a client attempts to update a read-only replica, the replica sends back a referral to one of the masters. The client has to be able to follow the referral to the master. Alternately, you could configure the consumer to use chain on update http://directory.fedoraproject.org/wiki/Howto:ChainOnUpdate
|
-- 389 users mailing list 389-users@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/389-users