Quote:
Originally Posted by adv_dp_fan
Never seen that. How is using an SMB share under Windows different than using a non-shared Windows drive?
|
Well, mainly the "networked filesystem" part, but there's also the part where the file system is networked.
Oh, fine.
Your computer doesn't "own" the filesystem.
And the underlying protocol used to communicate with the filesystem is totally different.
As the FAQ link I posted warns, networked filesystems might have issues hardlinking, or locking files, or they might just be flaky. For a program that has to synchronize numerous files, there is no automatic guarantee that things will work.
Quote:
|
If the network drive is a Windows file system, just shared over the network, why wouldn't that work? Especially if only one person ever accesses it at any time. We just want to share a subset of each of our libraries with other systems here so I created another library on a shared drive we can all copy to. I know just enough networking to be dangerous but not enough to understand why it might not work.
|
It has nothing to do with how many people access the NAS at a time -- that only matters in terms of clobbering the database. You can do the same thing if two users try starting the same calibre library running on the local disk.
Quote:
|
Oh well, if Calibre doesn't support that then it doesn't. I'll just have to figure out some other solution.
|
Just use Synctoy or something to
mirror-sync the library onto the NAS.
Or you can try a NAS anyway. calibre does not officially support it, and you will get no help from the developer, but some people say they've gotten it to work. Maybe they will find this thread and offer a suggestion.
But then you really are on your own.
Much easier to simply sync a copy to the NAS.
