Issue #472 has been updated by Sébastien Bahloul.
I agree that checking that the main org.lsc.Launcher is running is not the way it should be checked : I would say that if at least a event-based sync is used, LSC should be binded to a local TCP port to enable remote commands. Thus, if the port is already binded, the LSC instance should not be started. If only periodical synchronization tasks are run, several instances could be run simoultaneously. ---------------------------------------- Bug #472: LSC start script should not check if LSC is already running http://tools.lsc-project.org/issues/472 Author: Clément OUDOT Status: Assigned Priority: Normal Assigned to: Clément OUDOT Category: Core Target version: 2.0 Problem in version: In LSC start script we have: <pre> # check if LSC is not already running if [ $(ps aux | grep -a org.lsc.Launcher | grep -av grep | wc -l) -ne 0 ] then # LSC already running fatal "LSC already running - launch aborted" # since LSC already running, don't launch and exit exit 1 fi </pre> First, this does not work, as we now pass the java classpath before the org.lsc.Launcher in the java command, so it does not appear in ps aux, and so this test never work. But this test should no more be here, as we plan to install one LSC program on a server with several configurations for sync and async connectors. So we need to be able to launch several LSC connectors from the same lsc start script. Do you agree? -- You have received this notification because you have either subscribed to it, or are involved in it. To change your notification preferences, please click here: http://tools.lsc-project.org/my/account
_______________________________________________________________ Ldap Synchronization Connector (LSC) - http://lsc-project.org lsc-dev mailing list [email protected] http://lists.lsc-project.org/listinfo/lsc-dev
