Subject | Firebird in readonly root environment |
---|---|
Author | paul_lowman |
Post date | 2008-10-01T01:57:51Z |
I am attempting to get Firebird 2.0.3.12981-1 running on a linux from
scratch setup with a readonly root filesystem.
I have set s symbolic link for security2.fdb to a writeable mount
(/var/firebird) and also set the environment variable FIREBIRD_LOCK to
/var/firebird.
This enables firebird to run fine as long as I only try to connect to
local databases - if I try to connect to a remote database (even using
localhost) then firebird complains that it cannot attach to the
security database - it seems that firebird always creates the
isc_lock/init files in the firebird root folder if the attempted
connection is to a remote database and ignores the FIREBIRD_LOCK variable.
Is this the correct behaviour ?
If so then is there a recommended way to set up firebird to run in a
readonly root environment ?
Any advice welcome ...
scratch setup with a readonly root filesystem.
I have set s symbolic link for security2.fdb to a writeable mount
(/var/firebird) and also set the environment variable FIREBIRD_LOCK to
/var/firebird.
This enables firebird to run fine as long as I only try to connect to
local databases - if I try to connect to a remote database (even using
localhost) then firebird complains that it cannot attach to the
security database - it seems that firebird always creates the
isc_lock/init files in the firebird root folder if the attempted
connection is to a remote database and ignores the FIREBIRD_LOCK variable.
Is this the correct behaviour ?
If so then is there a recommended way to set up firebird to run in a
readonly root environment ?
Any advice welcome ...