A couple of things:
I did understand that. I am confused at your suggestion that /opt/calibre/calibre-server (or wherever) is locking the database, as that is against what I have come to expect -- the server is read-only access to the database, so as far as I know, it doesn't lock the db. It has been used successfully at the same time as /opt/calibre/calibre
You want a plugin that will ssh into another computer and kill the calibre-server process? Aint happening. You can however, make a script to do that, and use it in the startup script.
However, it's worth noticing that running both at the same time will not break anything, it will merely leave the server out of date until it restarts.
I would try the WSGI plugin to apache (or whatever server) since it should re-initialize calibre-server on each access, as needed, and stay up-to-date.
Or script a bat script to do the windows equivalent of "ssh my-NAS; killall calibre-server; calibre-server; exit" which will restart calibre-server on demand. If your db is being locked up by /opt/calibre/calibre-server, then I think something is wrong.
Last edited by eschwartz; 02-12-2014 at 11:40 PM.
|