Hi, This is to let you know what we do certain migration situations when the etags on the server are lost or scrambled. I would like to know if anyone is having a similar practice or if client developers see any problem with that (and are aware that we use this as a feature of the system).
We simply stop the client, delete te .csync_journal.db and restart the client. Without .csync_journal.db the client will fall-back on comparing mtimes of local vs remote files. If size and mtime matches (within a second resolution) then they assume all is good and the client will update its .csync_journal.db with etags provided by the server. We also have a comprehensive test-case for this which shows various conflict scenarios with and without .csync_journal.db: https://github.com/cernbox/smashbox/blob/master/lib/test_basicSync.py kuba --
_______________________________________________ User mailing list [email protected] http://mailman.owncloud.org/mailman/listinfo/user
