Quote:
Originally Posted by theducks
I always specified the port as well as the library.
BTW I would use the full path to the Library
Some systems want you to avoid Port 80  |
isn't /calibre/library/ a full path to library directory? Or should I have specified metadata file as well?
And I have elevated CAP_NET_BIND_SERVICE capability in systemd .service file to allow non-root account bind to port <1024, and in fact verified both ports 80 and 8080 were properly bound by respective instances.
Quote:
Originally Posted by kovidgoyal
If for some reason you really want to run two different servers on a single machine and dont want to use the env var, use different user accounts. Though the single instance mutex is there for your protection, working around it is not a good idea. It doesnt just prevent multiple instances of the server, it also prevents other tools such as calibredb and the GUI from running. You basically cannot have more than one thing that can alter a database running.
|
My only reason for asking for 2 instances is to have anonymous accessible library with fewer books than the one which needs login and which would also include work-in-progress books.
I was under impression that giving two instances 2 different paths to 2 different libraries would prevent more than one thing touching any of those libraries, I am confused as to what other resource those 2 instances could be sharing given that I gave them different ports, different libraries and different pid files.
But I agree, I am uncomfortable with using that environment variable override, I will definitely try using 2 different accounts, thanks for suggestion!