View Single Post
Old 04-25-2016, 09:35 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,525
Karma: 8065948
Join Date: Jan 2010
Location: Notts, England
Device: Kobo Libra 2
Quote:
Originally Posted by johnelle View Post
I don't understand why you would copy the .db file every time you boot(?)
My library is synced by dropbox, so it can change at any time. I use monit to deal with restarting calibre whenever necessary, including at boot.

The reasons are both historical and from paranoia. The historical reason: calibre-server before V2 didn't see changes in the metadata.db file, so calibre *had* to be restarted to see changes. This isn't true now.

The paranoia reason: I don't want to get into situations where the server has a detached file. If dropbox uses "unlink and recreate" instead of "overwrite" then the server won't ever see changes. In addition, I don't want to deal will permission hassles or locking.
chaley is offline   Reply With Quote