Hi. I'm using lsc to sync data between 389DS as source and OpenLDAP as destination. lsc is working as service in async mode.
Every thing is working fine, but sometimes I'm missing updates. Let me point that I have 6000 users an the idea is to have the data updated in the destination ldap as soon as possible it has modified in the source directory. Looking for access in the source ldap I founded entries like this. [21/Sep/2014:13:47:02 -0300] conn=5219872 op=7183 SRCH base="ou=xx,dc=yy,dc=com" scope=2 filter="(modifyTimestamp>=20140921164701Z)" attrs="cn objectClass javaSerializedData javaClassName javaFactory javaCodebase javaReferenceAddress javaClassNames javaremotelocation" [21/Sep/2014:13:47:07 -0300] conn=5219872 op=7190 SRCH base="ou=xx,dc=yy,dc=com" scope=2 filter="(modifyTimestamp>=20140921164706Z)" attrs="cn objectClass javaSerializedData javaClassName javaFactory javaCodebase javaReferenceAddress javaClassNames javaremotelocation" My question are: 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. Is the async mode the best way to run lsc in this scenario ? 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> ? Many thanks in advance Regards Norberto _______________________________________________________________ Ldap Synchronization Connector (LSC) - http://lsc-project.org lsc-users mailing list [email protected] http://lists.lsc-project.org/listinfo/lsc-users
