only perform a local (embedded or XNET) backup of the security database; embedded mode requires filesystem access rights to the database file; XNET (Windows only) requires username and password. 2. (only databases) Install Firebird 5 (see later sections) 3. Note down the permissions, ownership and filesystem access rights of security5.fdb 4. Rename the existing security5.fdb for safekeeping 5. Restore (as this would require the security database to exist, and it would lock the file). 6. Change filesystem access rights/permissions to match the original security5.fdb For a Firebird 4 security database

fast, direct I/O to database files for local connections on Linux. The client process must have filesystem-level access rights to the database for this to work. On Linux, all local connections are made You cannot locate components of the server, or any database, on a mapped drive, a filesystem share or a network filesystem. Note You can mount a read-only database on a CD-ROM drive but you cannot run server from one. Installation script or program Although it is possible to install Firebird by a filesystem copying method – such as “untarring” a snapshot build or decompressing a structured .zip archive

You cannot locate components of the server, or any database, on a mapped drive, a filesystem share or a network filesystem. Firebird 1.0 Quick Start Guide 6 Note You can mount a read-only database on server from one. Installation script or program Although it is possible to install Firebird by a filesystem copying method – such as “untarring” a snapshot build file or decompressing a structured WinZip TCP/IP connection string: the server name and the disk/filesystem path. Its format is as follows: • For a Linux server: servername:/filesystem-path/database-file Example on a Linux or other Posix server

there doesn't seem to be a better answer as long as you have ".gdb" files located in the general filesystem. 34 Chapter 4 Installing on POSIX Platforms Please read the first two chapters before you set had quite wide-ranging ability to read, create and delete database files anywhere on the POSIX filesystem. For security reasons, the service should have a more limited ability to read/delete and create

file system tools.  Use of BEGIN BACKUP and END BACKUP and copying the database files with filesystem tools, is not safe with multi-file databases! Use this method only on single-file databases. CURRENT_ROLE variable. CURRENT_USER Same as global CURRENT_USER variable. DB_FILE_ID Unique filesystem-level ID of the current database. DB_GUID GUID of the current database. DB_NAME Canonical name (persistent until restore/fixup) MON$FILE_ID VARCHAR(255) Unique ID of the database file at the filesystem level MON$NEXT_ATTACHMENT BIGINT Current value of the next attachment ID counter MON$NEXT_STATEMENT

of file system tools.  Use of BEGIN BACKUP and END BACKUP and copying the database files with filesystem tools, is not safe with multi-file databases! Use this method only on single-file databases.