hello, I have a lsc script running as a service, in asynchronous mode. because of latency (or ghosts? who knows) when VM backups are ran at night, the connection with the LDAP server seems to be broken.
every morning, lsc no longer synchronize because somehow it does not detect the link have been dead, and no longer receive notification of objects modifications I "solved" the problem by restarting lsc with a cron every night after the backups but I wonder if it is possible for lsc to detect that a long running search is no longer valid, and restart it? or maybe configure it to restart the search at specified interval? One could say this is no big deal: just restart lsc every day and be done with it, but I feel like I don't solve the problem, just work around it. thanks in advance. best regards, -- Jephté Clain Direction des Systèmes d'Information et des Usages Numériques - 2IG Tél. 0262 93 86 31 Fax. 0262 93 81 06 _______________________________________________________________ Ldap Synchronization Connector (LSC) - http://lsc-project.org lsc-users mailing list [email protected] http://lists.lsc-project.org/listinfo/lsc-users
