@SD, You are right in that the issue of embedded and server mode was raised but nothing was said about having to use server/TCP mode. I’ve copied out the text from those earlier Conversations and, as I’m using localhost, I could already been using server/TCP now (unless I’ve missed something. You can see below the relevant text).
If server/TCP mode is best then I’m very happy to use it. In this case I installed everything using default values and got to where I am. If I need to change something in the installation to create it as server/TCP then I’m happy to do so and would be happy to get guidance on how to do this.
Similarly I would be happy to get guidance on how to change the result of what I have now to make it work.
If it helps then I’ve found this https://firebirdsql.org/manual/qsg25-config.html and in particular the Section “Disable Classic local mode on Linux” which says “the so-called local or embedded access mode of the Firebird Classic and SuperClassic servers on Linux. Here too, users must have proper access rights to the database file itself. They also need read access to the security database security2.fdb. If this worries you (and it probably should), reserve filesystem access to the security database (and other databases, while you're at it) to the server process only. Users are then obliged to connect via the network layer. ” (my underlining.) It’s on version 2.5 but is this relevant?
Thanks
Nick
Comments from earlier Conversations
If you use embedded mode, then the access rights of *your* user applies. If you connect through the server, the access rights of the *service* user (e.g. the user firebird) applies.
Embedded means that
application loads the Firebird database engine and
uses that to
read the database in the same process. Server mode is
application
connects (using TCP/IP) to the server running on localhost
(or
on a remote server), and the database is accessed by the Firebird
server.
Since Firebird 3, it is basically, if you
only provide a filename, then
you're probably using Firebird
embedded (this is not 100% guaranteed,
for example if the
client library can't load the database engine, it
will try to
connect to the server on localhost).
So if you connect
using '/some/path/to/database.fdb', you're probably
using
embedded. If you're connecting using an URL like one of the
following, you're connecting through the server:
-
localhost:/some/path/to/database.fdb
-
localhost/3050:/some/path/to/database.fdb
-
inet://localhost//some/path/to/database.fdb
-
inet://localhost:3050//some/path/to/database.fdb
-
inet:///some/path/to/database.fdb
- (and variants with inet4://
or inet6://, or a host name other than
localhost)
--
You received this message because you are subscribed to the Google Groups "firebird-support" group.
To unsubscribe from this group and stop receiving emails from it, send an email to firebird-suppo...@googlegroups.com.
To view this discussion on the web, visit https://groups.google.com/d/msgid/firebird-support/b5ed9d8b-834f-4fbf-88b6-29404363f331n%40googlegroups.com.
To view this discussion on the web, visit https://groups.google.com/d/msgid/firebird-support/d836a53a-d60b-4bd9-a59e-8f7ab3a6dce8n%40googlegroups.com.