View Single Post
Old 08-08-2014, 04:37 AM   #7
chaley
Grand Sorcerer
chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.
 
Posts: 12,345
Karma: 8012652
Join Date: Jan 2010
Location: Notts, England
Device: Kobo Libra 2
Quote:
Originally Posted by kovidgoyal View Post
grep the code for reopen() and check_if_modified()

Edit: Line 53 of server/utils.py and Line 126 of db/legacy.py
Thanks. Tracing that back through expose(), the server dispatch controller, and endpoint management was fun.

I note that the old DB didn't do the reopen. Instead db2.check_if_modified() did a cache refresh, which is the behavior I was seeing when I first set this up (calibre v0.9 releases). The new DB does it right.

If I was not copying the DB then I could let calibre do the timestamp check instead of monit. However, as I want to keep copying the DB to eliminate any chance that dropbox will be "conflicted", monit has to stay.
chaley is offline   Reply With Quote