Clément "KPTN" OUDOT
Clément "KPTN" OUDOT
See https://lsc-project.org/documentation/latest/upgrade#long_task Try to set -i option with a duration that is higher than the duration of your sync
As written in upgrade notes, in LSC 2.1 we now close connections at the end of the task. In executable connections are managed in your scripts, LSC can't close them.
If you don't configure -i option, the connections will be closed after 1h. This is the intended behavior.
Thanks for the proposition. For the moment, I generate several status file by running them separately in cron, for example: ``` 0 * * * * lsc [ -x /usr/bin/lsc...
Set to 2.2 because it changes log format.
@floriancaillet Hello, sorry to come back after so many years. We will apply your code to master branch. Could you merge the new perl script inside the original one? There...
Could you verify that the value of the member is exactly the same in source and destination (check spaces for example) ?
An issue is opened about this: #54 Could you see if the issue you have is linked to that, or if this is a different issue?
Could you provide the LSC configuration? Do you know how to reproduce this?
At least, remove the parameter in 2.2 See if we open a new feature for Future version