Craig Worgan wrote:

Is it possible that modifyTimestamp is only changed on the server that the mod occurs? This would assume that mods over syncrepl to the consumers don't trigger a change to that particular operational attribute on the consumer (s) in a multi-master setup. Just a thought.

The modifyTimestamp is usually replicated along with everything else. (Assuming it wasn't excluded in the list of attrs to replicate.)

Craig

---

*From:* openldap-technical-bounces+worganc=nortel.com@openldap.org [mailto:openldap-technical-bounces+worganc=nortel.com@openldap.org] *On Behalf Of *Bad Guy *Sent:* Wednesday, June 17, 2009 6:30 AM *To:* openldap-technical@openldap.org *Subject:* N-way Master synchronization

Dear all,

I am using a 4-way LDAP servers version 2.4.11. (type=refreshOnly, interval="00:00:00:30",attrs="*,+")

Everyday, there will be some records updated in any of the servers.

...

From time to time, I will dump the records in all 4 servers and

checked the modifyTimestamp attribute. I find that there is some records where the modifyTimestamp attribute value are different from other 3 servers. But the other content seems synced. Only differ by the modifyTimestamp attribute.

Any idea of how come such situation occur ?

Thanks

---

來看看 Windows Live 的其他功能除了寄信 Windows Live 還有更多功能 立即升 級 Windows Live Hotmail http://mail.live.com