2014-09-22 17:46 GMT+02:00 Norberto Altalef <[email protected]>:
> Hi Clément. Many thanks for your answer. > > >> > >> What happen if I have an update (following the example log) at 13:47:05 > >> Is it catched ? I think is out of scope of both filters. > >> > > > > Indeed. Can you confirm that LSC is running on the same host that the > > directory? Else, are you sure both hosts have the same time? > > > > lsc is running in the destination host, and you are rigth the > destination host was 4 sec ahead ! > Now the filters using modifyTimestamp are correct to catch all the updates. > > Although this should not happen again, I think that will be better run > lsc in the source host. Am I right? > There is no problem to run it on a different host, it just requires NTP on the two host to have clock sync. > > > > >> > >> Event based ldap source service would be a best option? > >> But 389ds unfortunately is not listed as supported. > >> Since 389DS comes from Netscape DIrectory Server. Can I use it as > >> <serverType> ? > >> > > > > > > You can try to use "SunDS", but we have a little issue with it, as is > does > > not perform the full sync before starting on-the-fly modifications (see > > http://tools.lsc-project.org/issues/597) > > > > > Do you recommend to use asyncLdapSourceService ? > What are the advantages and disadvantages? > > asyncLdapSourceService is real time, as it get events on the fly. But we mainly support it for OpenLDAP. Clément.
_______________________________________________________________ Ldap Synchronization Connector (LSC) - http://lsc-project.org lsc-users mailing list [email protected] http://lists.lsc-project.org/listinfo/lsc-users
