On Sat, 2016-02-06 at 12:26 +0000, Graham Cobb wrote: > On 06/02/16 09:56, deloptes wrote: > > It does now exit, but staying there after > > > > Synchronization successfull > > Changes applied .... > > Data modified .... > > *** @..../addressbook *** > > no changes > > I assume you meant "It does NOT exit". In my experience, the appearance > of syncevolution not exiting is often due to the "changes" perl script > which, in may case, can take a VERY long time. I don't remember the > name of the script offhand but while it is "hung" you may want to see if > there is a process running perl on your system. > > I recommend that while initially testing you set "printChanges=0" (if > you have a lot of data you may want to set dumpData=0 as well, except > when you really want to save the data). Turning off both those at least > means you are really just testing the sync code. > > That may not be your problem at all, but it is worth checking.
Agreed. In addition, running with SYNCEVOLUTION_DEBUG=1 syncevolution --daemon=no loglevel=10 .... is also recommended. This keeps all operations inside a single process (nice for running under gdb), without suppressing any debug output that might come from inside the libraries that are getting called. -- Best Regards, Patrick Ohly The content of this message is my personal opinion only and although I am an employee of Intel, the statements I make here in no way represent Intel's position on the issue, nor am I authorized to speak on behalf of Intel on this matter. _______________________________________________ SyncEvolution mailing list [email protected] https://lists.syncevolution.org/mailman/listinfo/syncevolution
