View Single Post
Old 03-25-2021, 05:18 PM   #10
mbovenka
Wizard
mbovenka ought to be getting tired of karma fortunes by now.mbovenka ought to be getting tired of karma fortunes by now.mbovenka ought to be getting tired of karma fortunes by now.mbovenka ought to be getting tired of karma fortunes by now.mbovenka ought to be getting tired of karma fortunes by now.mbovenka ought to be getting tired of karma fortunes by now.mbovenka ought to be getting tired of karma fortunes by now.mbovenka ought to be getting tired of karma fortunes by now.mbovenka ought to be getting tired of karma fortunes by now.mbovenka ought to be getting tired of karma fortunes by now.mbovenka ought to be getting tired of karma fortunes by now.
 
Posts: 2,079
Karma: 14079267
Join Date: Oct 2007
Location: Almere, The Netherlands
Device: Kobo Sage
Quote:
Originally Posted by theducks View Post
Fun things happened when screen savers or auto logout happened while full locks were in use.
Thank goodness they had tools to see which user placed locks, so all you had to do was find the user.
I know Been there, done that, used said tools...

I understand the reasons why using two instances of Calibre on the same library at the same time is asking for major trouble; exactly because the DB backend does not have said locking protocols. I also understand (or at least accept; my knowledge of file system semantics does not reach to really understanding it) that having your metadata.db on an SMB share isn't a good idea, even if it seems to work fine for months or even years.

But that doesn't make 'using a file' on said share 'risky'. Like I said, people have been doing it for years. Yes, it's not the same as local storage, but that's not local storage vs. network storage, that's single user vs. multi-user (or just multi-process). Having your stuff on a local disk isn't inherently safer than having it on a remote share of some sort.
mbovenka is offline   Reply With Quote