Thanks for the quick answer. What do you mean by that ? Does that mean I shouldn’t launch lsc with –all but rather with different cron tasks having “lsc –s –dest1”, “lsc –s –dest2”, etc so that each task only tries to contact one dest?
De : Clément OUDOT [mailto:[email protected]] Envoyé : jeudi 4 décembre 2014 11:47 À : FOUCHET, Alexandre Cc : lsc-userslsc-users Objet : Re: [lsc-users] What happens when one destination server is down ? 2014-12-04 11:40 GMT+01:00 FOUCHET, Alexandre <[email protected]<mailto:[email protected]>>: Hi, I have one source LDAP and about 15 dest LDAP. I’m using lsc –c all and lsc –s all every 5 seconds to synchronize it all. So far so good, I tried to turn off one of the dest LDAP (let’s say dest5) server to see what happens. I thought lsc would just say that Dest5 is unreachable and that it would skip it to do the next task on dest6. But it seems that LSC just stops all the tasks as soon as one server is not responding. Can you confim that ? Is there a way to obtain the behavior I’m describing above ? Hi, I confirm this behavior, LSC first check all connections before launching the tasks. The only solution for now is to have a lsc configuration per directory. Clément. This message contains information that may be privileged or confidential and is the property of the Capgemini Group. It is intended only for the person to whom it is addressed. If you are not the intended recipient, you are not authorized to read, print, retain, copy, disseminate, distribute, or use this message or any part thereof. If you receive this message in error, please notify the sender immediately and delete all copies of this message.
_______________________________________________________________ Ldap Synchronization Connector (LSC) - http://lsc-project.org lsc-users mailing list [email protected] http://lists.lsc-project.org/listinfo/lsc-users
