Closed darlac closed 5 years ago
The reason I put the lock system in place is to prevent corruption from starting another sync of the same targets while a prior big/long sync is still in progress. Consider editing out the lock code at the bottom of the script, but beware... files can be deleted or replicated if concurrent runs of the same trees are running.
Thanks for the box feedback.
The reason I put the lock system in place is to prevent corruption from starting another sync of the same targets while a prior big/long sync is still in progress. Consider editing out the lock code at the bottom of the script, but beware... files can be deleted or replicated if concurrent runs of the same trees are running.
HI, thanks for the prompt response - I thought that running different folders (not a duplicate instance of the same sync) would be fine, but it is not - should I try to put the lock file in another folder (so there is no interaction)?
There won't be a conflict if there is no overlap in folders. The lock filename could be updated to include the path1/2 string's, as an enhancement. In the mean time just edit out the lock mechanism. Should be a simple edit.
Yep, I just updated the lock filename and works fine!
I'll leave this open as an enhancement.
Updated the lock filename in v2.7. Thanks.
Hi there, just wanted to confirm that the sync works with box cloud service - tested with both arch and debian. question: I want to sync 3 different folders - how can I do it in parallel? rclonysync_LOCK prevents that