|
Thanks for the feedback guys.
@eschwartz - While I agree the calibre-server is a read-only process, python still locks the db when it is opened for reading and that is the observed behaviour. Which is the reason why I have to shut down the content server on the linux box every time I need to make changes.
@theducks. Thanks for your advise. I can see how there might be problems as you mentioned, but in my case I let calibre do the work. I have set up a directory that calibre monitors and I am careful to add books that have a specific name convention. The eBook is dropped into the directory and Calibre does the rest. The eBook is automatically pulled into calibre, file name parsed, renamed and stored in the library. In the 9 months I have been using this particular set-up I have never had any problems. In fact the whole system (apart from the Content-server shut-down problem) works like a dream. When I get a new book I rename it drop it to the monitored directory, wait a few seconds, it then disappears and next it is in the library complete with metadata (some times I will need to edit the metadata manually)... it's great! so easy.
@PeterT - Thanks for the links - Some good information there and some good ideas. However for my purposes they are a little too convoluted. It has given me some ideas though. I think now that I understand that the content-server does not respond to any commands I think I will knock up a simple plugin that uses ssh (possibly PuTTY CLI or openSSH) to remotely run a script on the Linux box to shut-down the content server when I fire up calibre on my laptop and then let the plugin fire off another script to start the server when I shut-down calibre.
So once again thanks for your help, patience, and most importantly your valuable feedback.
Cheers
Bick
|