On Mon, 2010-06-07 at 14:42 +0100, Anssi Saari wrote:
Patrick Ohly <patrick.ohly(a)intel.com> writes:
> If the .server.ini file had been renamed before that sync, no such lines
> should be logged. Beware that removing that file and then doing normal
> syncs is
Is what exactly, bad?
Eh, sorry, must have gotten distracted. Yes, running a normal sync
without this meta information is likely to have all kind of weird
effects, like updates from phone to server not being possible.
Perhaps SyncEvolution should guard itself against such corruption. Right
now there are no such sanity checks.
>> BTW, now that I looked at the last log
>> (myphone-2010-06-07-13-29/syncevolution-log.html), it seems notes and
>> addressbook went to slow sync. Just to confirm, should I remove the
>> .server.ini for those two only and then do a slow sync to fix things?
> Yes, please. It seems that we still don't have both sides in true sync
> and/or the confusion around "refresh-from-server" and .server.ini left
> us in an unknown state.
I don't know what to think now. I renamed the notes and addressbook
.server.inis and did a slow sync. Then setup for two-way sync and
removed some of my duplicate notes on the laptop. The result was a
slow sync again. I also only got a log for the latter sync, not the
Do you have maxlogdirs=0 in your config, as mentioned in a former email?
Otherwise intermediate sessions may get removed. If the former sync in
this example did not modify data, then it is not unlikely that it was
I agree that this is something which is not intuitive. Perhaps instead
of removing the directory completely, only the .html log file and the
database dumps should be removed? Then the status.ini documents that
there was a session and what was done without costing disk space.
Senior Software Engineer
Open Source Technology Center
Pützstr. 5 Phone: +49-228-2493652