Quote:
Originally Posted by Sirtel
Me, I will never allow an active library to reside on a networked drive, as you do.
|
Note that when using Windows networking (not just SMB/CIFS, but actual Windows on both client and server), the semantics of the connection are such that there is no difference between local and networked. Even the response to the write point becoming unavailable (e.g., remove a data cable from a local drive or pull the network cable) looks the same as far as the software is concerned.
As a matter of fact, if the software doing the writing (e.g., Calibre) doesn't do some serious low-level checking, the library could be on a network drive and the software has no clue, because of the ability to use symbolic links that point directories or files to another machine.
I wouldn't put my Calibre library on a network drive simply because there's no value in it...you can't run multiple instances of Calibre on the same database, so there's nothing to gain by making it available to multiple machines at the same time.