[Csync2] synchronizing file deletions

Michael Johnson mikjo.sas at gmail.com
Wed May 22 23:00:54 CEST 2013


I, fixed all the other noise.  Now I get to seeing a useful
error message:

# err: Do not auto-resolve conflict: This is a removal.
# err: File stays in dirty state. Try again later...

I don't see documentation on what cases will refuse to sync.

In my case, I want to always succeed, no matter what.
What I want is "if you know what is newer, choose that;
otherwise, fall back to some other specified policy, but
in any case get back in sync". The other specified policy
in my case would be either left, right, or first (I still need
to think about whether it even matters).

To do that, perhaps it would make sense for the configuration
to be able to say

auto younger first;

and it would try younger, and fall back to first.

Does this seem crazy to you?


More information about the Csync2 mailing list