For some months now, I've been uploading books to the Linux box that I keep my Calibre library on, shutting down calibre-server, running calibredb to add the book, and then starting up calibre-server again.
If I didn't shut down calibre-server first, I'd get an error:
Quote:
|
Another calibre program such as calibre-server or the main calibre program is running. Having multiple programs that can make changes to a calibre library running at the same time is a bad idea. calibredb can connect directly to a running calibre content server, to make changes through it, instead. See the documentation of the --with-library option for details.
|
I'd tried running calibredb with --with-library, but I'd get "refused" errors. I finally figured out why, I had to add --enable-local-write when I ran calibre-server. With that in place, I can run calibredb --with-library without problems.
But I am still having to shutdown calibre-server in order to run the main calibre UI. Even when I run it with the same --with-library argument that made calibredb work, I get the same error message when I run the calibre command.
Does the main calibre UI work, when run with --with-library pointing to an instance of calibre-server?
Is it intended to?
I find having access to my libraries from my mobile devices very convenient. Having to shutdown calibre-server every time I run the local UI much less so.