[pkg-firebird-general] Database file ownership in classic server

[Damyan Ivanov]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi, Aldo,

- -=| Aldo Caruso, 12.03.2007 19:20 |=-
>    While in the super server version the restored database belongs to
> firebird user and group, in the classic server version, the restored
> database belongs to the user who run gbak ( i.e. root ).
> 
>    The obvious solution was to do chown firebird:firebird <database file
> name> after restoring, but should'n gbak take care of that, as in the
> super-server version ?

When using super-server gbak, invoking "gbak db.fbk /path/to/db.fdb"
internally converts this to "gbak db.fbk localhost:/path/to/db.fdb",
meaning that the server process itself creates the database file. This
is not the case when using classic gbak, when the gbak itself creates
the file.

To achieve the same result with classic, explicitly add localhost: in
front of the path. Of course, this removes one of the greatest benefits
of classic - direct access to the database file (instead via tcp socket).

Classic is actually 2-in-1: server, implemented via
inetd/xinetd+fb_inet_server - acting as a "server" in the classical
sense that there are separate server and client processes; and embedded
- - when each "client" has direct access to the database files.

If you mix the two approaches, you have to take care of the caveats. :)


	dam
- --
Damyan Ivanov                           Modular Software Systems
phone +359(2)928-2611, 929-3993              fax +359(2)920-0994
mobile +359(88)856-6067              JID dam at jabber.minus273.org
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFF9bWwHqjlqpcl9jsRAgTIAKC7nDc2b0xgVj7c3wUMhGz8wb64LgCgjiXp
tH2OvQN7xrA9jZ2bCHoNdbw=
=y8eu
-----END PGP SIGNATURE-----