On Jun 18, 2013, at 11:21 , Clément OUDOT <[email protected]> wrote:
> > > 2013/6/18 Christian Bösch <[email protected]> > Hi Sebastien, > > I resumed work on that issue after some time and I switched from ldaps to > ldap and captured traffic with tcpdump. > It seems that all changes are recognized on the lsc sync server, but I found > out that if I wait about 3 minutes between > disabling 2 users everything works fine. If I want to disable users > immediatly after each other, they weren't disabled in the target AD. > Is it possible that lsc scans the whole directory on each change and that in > series immediately changes aren't recognized? > > > > You may face a concurrency problem. > > Try to run LSC with -t 1 to force LSC to use only one thread. unfortunately the same result with -t 1 > > Clément.
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________________________ Ldap Synchronization Connector (LSC) - http://lsc-project.org lsc-users mailing list [email protected] http://lists.lsc-project.org/listinfo/lsc-users
