Issue #729 has been updated by Norberto Altalef.
Hi. OK. Thanks for your effort. I think (without a technical justification) that 389DS may have a buffer mechanism also to record parameters such modifyTimestamp. One sec is very little in certain conditions, but may be affecting in this case. I'm still not sure, but may be I need to revert origin and destination in the future, in which case we will see if OpenLDAP acts different. Thanks again. Norberto ---------------------------------------- Bug #729: fail to sync in async mode http://tools.lsc-project.org/issues/729 Author: Norberto Altalef Status: Assigned Priority: Normal Assigned to: Raphaël Ouazana Category: Core Target version: Not planned Problem in version: I founded a difference between the exact time LSC does the request, and the time used to compute modifyTimeStamp filter in async mode. The search interval is not always 5 sec, but the modifyTimeStamp keeps always in 5 sec before the request time. In this condition some updates are not synced. Example (389ds as source -> OpenLDAP as destination): A password change with modifyTimestamp Sep 23,2014 6:58:56 PM ART (20140923215856Z) was no updated in the destination server. 23/Sep/2014:18:58:56 -0300] conn=5357120 op=30052 SRCH base="ou=people,dc=xx,dc=com" scope=2 filter="(modifyTimestamp>=20140923215852Z)" .... [23/Sep/2014:18:59:02 -0300] conn=5357120 op=30060 SRCH base="ou=people,dc=xx,dc=com" scope=2 filter="(modifyTimestamp>=20140923215857Z)" .... -- You have received this notification because you have either subscribed to it, or are involved in it. To change your notification preferences, please click here: http://tools.lsc-project.org/my/account
_______________________________________________________________ Ldap Synchronization Connector (LSC) - http://lsc-project.org lsc-dev mailing list [email protected] http://lists.lsc-project.org/listinfo/lsc-dev
