> > I've been seeing a great many errors like this on both sides:
> > While syncing file
> > /var/www/htdocs/wp-content/themes/wireframe/widgets/search_widget.php:
> > ERROR from peer server1: File is also marked dirty here!
> > Do not auto-resolve 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 capable of producing an exactly identical timestamp.
On 3 November 2015 at 11:07, Marcus Downing <mar...@bang-on.net> wrote:
> On 3 November 2015 at 11:00, <csync2-requ...@lists.linbit.com> wrote:
>> If the stat information (as recorded by csync2) is identical,
>> *and* the content is identical, even if both sides are "marked dirty",
>> You will get "File is already up to date on peer.",
>> and the dirty flag is cleared (on both sides, for this host pair).
>> At least that is how it *should* be, and how it works for me.
>> So if that does not work for you, you may need to upgrade,
>> or come back with a test case to show how to reproduce the misbehaviour.
> That's what I'd expect to happen but isn't.
> I'll try upgrading and see if it changes anything.
> *Marcus Downing*
Csync2 mailing list