Linux running gui and using calibredb at the same time

[razmichael]

In part for the fun and challenge of learning how Linux and bash scripting works, I've set up a Raspberry pi, installed Calibre and set up the content server to run at bootup (no GUI) with a single library. I have a "Autoadd" folder on the Pi (shared on the network through SAMBA) along with a crontab running every 3 minutes that checks the folder for files and, if it finds any, runs a script that, along with some basic checking and logging, does this:

calibredb add --with-library=/home/calibre/Calibre_Library/ --recurse /home/calibre/AutoAdd/

and then archives the added files in a backup folder. I can remotely (SSH) check the status, view the logs, toggle the crontab off/on, stop/start the server etc through a script I wrote. Over all it works great! From any computer (and phone) in the house I can drop books into the folder and at most 3 minutes later they appear in the library through the content server. I use NordVPN's MeshNet so all this is also available external to my network.

So what's my question? If I have the gui open on the Pi and run the calibredb add, I get the following:

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 understand the basis of this (multi users on the DB) but am wondering how much of an issue is it really under my circumstances? My Add Books script currently checks if the GUI is open and will not run the 'calibredb add' if it is. Although my intention is not to have the gui up on the Pi often, I'm wondering, given the fairly limited environment how likely is running a Command Line calibredb (especially only adding a few books), problems will result? My instinct is to allow the background add to occur regardless of whether the gui is open on the Pi.

EDIT: I think I was confused during testing and it looks like the Calibredb WILL NOT add the new book(s) when the GUI is open anyway. Not sure if there is a way to force it to ignore the warning and process the new books.

Thanks

[kovidgoyal]

Run the content server in the gui, then have calibredb connect to the server, and you can add books and do other operations. See the docs for calibredb on how to specify a server to connect to.

[razmichael]

[EDIT]: Solved the 'issue'. As the current crontab (runs every 3 minutes) checks if the GUI is open and does not even try to run calibredb to add any files found in the autoadd folder, this can continue to run (without trying to add anything) even when the GUI is open. By setting up the GUI to use the same autoadd folder it means that either way (no gui, running silent/headless, VNC window and running the GUI ...), any books dropped in the folder will be added - just by one or the other mechanisms. So basically a seamless adding of books from any authorized device.[End EDIT]

Thanks for the response. The goal is to rarely have the GUI up unless really needed (VNC into the Pi) while the scripting along with calibredb will add any books in the background that are dropped in this network shared directory/folder. As it looks like there is no way to "tell" calibredb to ignore the "another calibre program is..." warning and continue to add books (if found) I'll just let the background process continue but it will skip any new books until the GUI is closed (what I do now). Other than this minor limitation, the process works great anyway - put a book in the folder from anywhere conputers, phone, outside the home network for devices with authorization) and a few minutes later it is readable with the web interface.

Thanks for all your work with Calibre.