Quote:
Originally Posted by kenmac999
a poor man's hack around this might be to install calibre on each client and ensure library location is consistance, ie c:\mylibrary then creat a script would test for a network temp.lck file and if not found create it, copy the network copy of your calibre library to local location then run calibre. have script delete the temp.lck file after calibre is shut down. I do not have home network to test this on but have used similiar scripts in linux to automate backups of my libraries.
|
I do not know if this may work in all scenario's. I succesfully run calibre over the network but are making sure the user has read-only permissions. This works.
If in read-write mode, the problem starts when changing metadata because not only the database file is updated, also files and folders are moved, changed, renamed etc. The funny thing is that this does not work correctly over the network because of the way calibre does its file access. You would think simple file moves/copy/deletes etc are fairly standard operations over the network but this is not the case for calibre. It only works correctly on the local filesystem not on the (windows) network. This cannot easily be solved in the current implementation.
So when I modify the database I run calibre on the server itself using remote desktop and for the rest the family has read-only access.
Your suggestion may work but you have to copy ALL files and folders to a local drive, do your changes and then move the complete database structure (all files/folders) back to the network drive. With a large library this may take some time. So in principle, yes this may work but maybe it is not that practical for a large library