Hi all- I'd like to run LSC in async mode listening for updates and acting on them, as opposed to polling, however a couple things I've noticed:
-Clean doesn't get run at all while in async mode, why? Can I enable it? -I have OpenLDAP 2.4.28, and my async ldap source service configured, but when I watch debug logging, it looks like it is still polling every 10 seconds as opposed to being triggered based on changes, why? Also, when I run "sudo lsc -t 1 -s all -c all", I'm seeing the following errors printed in the log: Aug 20 15:38:45 - ERROR - There is no future associated with operation message ID 15, perhaps the operation would have been completed Aug 20 15:38:45 - ERROR - There is no future associated with operation message ID 15, perhaps the operation would have been completed Aug 20 15:38:45 - ERROR - There is no future associated with operation message ID 20, perhaps the operation would have been completed Aug 20 15:38:45 - ERROR - There is no future associated with operation message ID 20, perhaps the operation would have been completed Can these be ignored? And if so, are they going to be fixed? I'd like to turn my logging to error only and have it email me in the event of an error, and if these are being printed on every run that won't work. Thanks, David
_______________________________________________________________ Ldap Synchronization Connector (LSC) - http://lsc-project.org lsc-users mailing list [email protected] https://lists.lsc-project.org/cgi-bin/mailman/listinfo/lsc-users
