Quote:
Originally Posted by kovidgoyal
There's nothing to expand, network filesystems are all broken, they break various integrity guarantees that calibre makes use of for efficient file operations. So keeping the library on a network filesystem will eventually lead to data loss, because of bugs in the network filesystem drivers. Use the calibre content server if you want true networked access.
Networked filesystem basically work only if you restrict yourself to simple file copy operations and nothing else. calibre does much more than that.
|
No need to be snippy when someone
politely asks you for more information. Especially when the reasoning for such a sweeping statement wasn't part of your initial posting.
As for your suggestion, I
have been working on setting up calibre-server on a headless server. So, thanks for that. Unfortunately, through no fault of yours, I'm sure, the arm64 repos are out-of-date (as we discussed in the recent thread about calibredb throwing a python error).
And, even with current a version running on an x64 Windows 10 system I can't make it do what I want, so I'm left weighing how much time and effort will be needed to learn how to make the software do what I want (or if it's even possible at all).
So, again, thanks for your efforts in creating the software. Even if I don't end up using it, it's definitely a powerful piece of coding.