Thread: Simple Approach to an External Library and Server using 3.14.0
View Single Post
Old 12-28-2017, 10:17 PM   #9
davidfor
Grand Sorcerer
davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.
 
Posts: 24,905
Karma: 47303824
Join Date: Jul 2011
Location: Sydney, Australia
Device: Kobo:Touch,Glo, AuraH2O, GloHD,AuraONE, ClaraHD, Libra H2O; tolinoepos
Quote:
Originally Posted by BetterRed View Post
@davidfor - the first post has this



I interpret that as saying the Mac install of calibre is accessing a library on the server, which is presumably running Ext3 or Ext4. When calibre-server is run at the server it presumably uses the same library.
I misread the first post. And based on the comments made since calibre v3 was released I'm surprised it works. The OP seems to have two instances of calibre (one for the server, one for the GUI) running at the same time on the same library. I'm surprise it is working. If the OP was stopping the server before opening the GUI, then the only concern would be the file systems.
Quote:
My question would be - will the files calibre creates and maintains from the MAC client, be named according to Ext3/4 rules (case sensitive) or HFS+ rules (case insensitive). I have no idea, so I would do some experiments
Whether that is an issue depends on how the MAC is mounting the share from the server. It should be mounting it as a networked file system, not a native file system such as HFS+ or an EXT variant. I know Windows has no issues mounting EXT3/4 shares and using them. I can't check now, but I'm reasonably sure there is no way to tell what the remote file system is. It's probable that the client OS concerned won't support the full function of the underlying physical file system used on server, but the server should be returning errors to the client OS when it does something it shouldn't. The differences in case sensitivity mentioned by Kovid are a good example of this, and I don't remember how Windows handles this. If the server has files with the same name but different cases, I don't know if Windows will show in a directory listing. I have played with this in the past, but I don't remember exactly what happen, and I'm away from home and can't test what happens.

It will also be different depending on how the remote drive is accessed. Samba, NFS, FTP or something else will probably all give slightly different results.
davidfor is offline   Reply With Quote