self could implement this better. A flag `csync2 -o` (for
"others") could send a simple message to all other reachable servers in the
group in turn, requesting them to sync back to me please. This would of
course be guarded by the group's shared key, and if necessary it could be
guard
lowing line be changed:
http://git.linbit.com/csync2.git/blob/HEAD:/update.c#l553
from
if ((localdata > remotedata) ==
to:
if ((localdata >= remotedata) ==
which is to say, if the timestamps on the two sides are the same it
considers itself to have won the conflict and proceeds to sync
isn't.
I'll try upgrading and see if it changes anything.
*Marcus Downing*
mar...@bang-on.net
___
Csync2 mailing list
Csync2@lists.linbit.com
http://lists.linbit.com/mailman/listinfo/csync2
e conflict: Lost 'younger/older' test.
So why is that file generated simultaneously on both nodes?
In case my question wasn't clear: the file is identical on both sides
because csync2 synchronised it, and adjusted the copy's dates as it did. No
other process would be capab
