View Single Post
Old 08-08-2014, 12:32 AM   #4
kovidgoyal
creator of calibre
kovidgoyal ought to be getting tired of karma fortunes by now.kovidgoyal ought to be getting tired of karma fortunes by now.kovidgoyal ought to be getting tired of karma fortunes by now.kovidgoyal ought to be getting tired of karma fortunes by now.kovidgoyal ought to be getting tired of karma fortunes by now.kovidgoyal ought to be getting tired of karma fortunes by now.kovidgoyal ought to be getting tired of karma fortunes by now.kovidgoyal ought to be getting tired of karma fortunes by now.kovidgoyal ought to be getting tired of karma fortunes by now.kovidgoyal ought to be getting tired of karma fortunes by now.kovidgoyal ought to be getting tired of karma fortunes by now.
 
kovidgoyal's Avatar
 
Posts: 45,382
Karma: 27756918
Join Date: Oct 2006
Location: Mumbai, India
Device: Various
@chaley: Is restarting the server via monit really necessary? IIRC, any endpoint in the server uses check_if_modified() which checks the modified timestamp on metadata.db and if it is modified, it automatically closes and re-opens the connection to metadata.db

Since the check uses mtimes on the metadata.db path, it should not matter what technique the sync service uses to update the file.

EDIT: Although I have to say that if dropbox is doing a delete and then create, which is not atomic, as opposed to copy-sync-rename, which is, then re-opening the database connection with a partially synced metadata.db would cause bad things to happen.

Last edited by kovidgoyal; 08-08-2014 at 12:36 AM.
kovidgoyal is offline   Reply With Quote