--On February 14, 2008 12:21:00 PM +0000 hyc@symas.com wrote:
Pierangelo Masarati wrote:
hyc@OpenLDAP.org wrote:
Another possibility would be to filter out any entries whose entryCSNs are newer than the contextCSN in the LDIF before trying to slapadd it.
Should slapadd take care of it (perhaps if instructed to do so)?
Of course it might be better to change the delta-sync consumer to check the target's entryCSN after a modification fails, to see if it matches the current modification attempt. If so, then the failure can be safely ignored. --
Note:
It should be if it matches or is greater. For example, if it was the very last entry in the DB, thus the last to be added to the resulting LDIF, it is entirely possible that multiple modifications could be done from the time the dump started and the dump ended, meaning the CSN would be greater than the one encountered in the accesslog DB.
--Quanah
--
Quanah Gibson-Mount Principal Software Engineer Zimbra, Inc -------------------- Zimbra :: the leader in open source messaging and collaboration