Firebird Documentation IndexFirebird 1.5.6 Release NotesI N S T A L L A T I O N   N O T E S → POSIX Platforms
Firebird Home Firebird Home Prev: I N S T A L L A T I O N   N O T E SFirebird Documentation IndexUp: I N S T A L L A T I O N   N O T E SNext: Configuring the Port Service on Client and Server

POSIX Platforms

(Originally by Mark O'Donohue, revised for 1.5)

Installing on Linux
Testing your Linux installation
Utility Scripts
Linux Server Tips
Uninstalling on Linux

The Firebird server comes in two forms, Classic, which runs as a service, and SuperServer, which runs as a background daemon. Classic is the more traditional UNIX service, while Superserver uses threads, rather than processes. For the user just starting out with Firebird, either will do, although the Classic server is likely to prove a better platform for initially experimenting with Firebird.


  • You will need to be root user to install Firebird.


  • Installation on Linuxen requires a glibc package installed that is equal to or greater than glibc-2.2.5 and a equal to or greater than libstdc++-5.0.


  • For a rough evaluation of compatible Linuxen, refer to the section Linux Compatibilities, but don't take it as the "last word". Linux binary distros out-of-the-box can vary depending on where and when they were built.


  • Ensure that the 'ed' and 'vim' editor packages are installed on your system. If the required editor is not present, the package will install but the installation scripts will fail.


    This dependency may in future be replaced by 'sed'.

Installing on Linux

The following instructions describe the Classic installation. For installation of Superserver the "CS" in the package name is repaced by "SS". For example, the package FirebirdCS-1.5.0-nnnn.i686.rpm is replaced by FirebirdSS-1.5.0-nnnn.i686.rpm.

Log in as root, or open a root shell. In the example filenames below, replacy nnnn with the build number of the kit you actually have.

RPM Installer

For the RPM installer, type:

  $rpm -ivh FirebirdCS-1.5.0-nnnn.i686.rpm

Installing the Tarball

To install the tarball, place the ".tar.gz" file and type:

  $tar -xzf FirebirdCS-1.5.0-nnnn.tar.gz
  $cd FirebirdCS-1.5.0-nnnn.i686

What the Linux install scripts will do

The Linux install scripts will

  1. Attempt to stop any currently running server


  2. Add the user 'firebird' and the group 'firebird' if they do not already exist.


  3. Install the software into the directory /opt/firebird and create links for libraries in /usr/lib and header files in /usr/include


  4. Automatically add gds_db for port 3050 to /etc/services if the entry does not already exist


  5. Automatically add localhost.localdomain and HOSTNAME to /etc/hosts.equiv


    1. SuperServer only installs a /etc/rc.d/init.d/firebird server start script.

    2. Classic server installs a /etc/xinetd.d/firebird start script or, for older inetd systems, adds an entry to the /etc/inetd file


  6. Specific to SuSE, a new rcfirebird link is created in /usr/bin for the init.d script and an /etc/rc.config Firebird entry is created.


  7. Starts the server/service. Firebird should start automatically in runlevel 2, 3 or 5


  8. Generates and sets a new random SYSDBA password and stores it in the file /opt/firebird/SYSDBA.password.


  9. Adds an entry to aliases.conf for the sample database, employee.fdb.

Testing your Linux installation

Step 1 - Accessing a database

In a shell:

 $cd /opt/firebird/bin
 $./isql -user sysdba -password <password>1

 SQL>connect localhost:employee.fdb /* this is an aliased path */

 SQL>select * from sales;
 SQL>select rdb$relation_name from rdb$relations;



1A password has been generated for you on installation. It can be obtained from the /opt/firebird/SYSDBA.password file, located in the Firebird root directory.

Step 2 - Creating a database

From version 1.5 onward, the Firebird server runs by default as the user 'firebird'. While this has always been the recommended configuration, the previous default was for the server to run as 'root' user. When running as root user, the server 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 files.

While the new configuration is better from a security perspective, it requires some special considerations to be taken into account for creating new databases:

  1. the user 'firebird' has to have write permission to the directory in which you want to create the database.


  2. the recommended value of the DatabaseAccess attribute in the /opt/firebird/firebird.conf file should be set to None, to permit access only through entries in the aliases.conf file.


  3. use entries in aliases.conf to abstract users from the physical locations of databases. More notes on aliases are to be found in the topic Database File Aliasing.

Procedures for creating a new database can vary with different configurations but the following configuration and steps are recommended:

  1. If a directory that is owned by the user 'firebird' does not exist, then change to root user and create the directory:

     $su - root
     $mkdir -p /var/firebird
     $chown firebird:firebird /var/firebird


  2. Create a new physical database and set up an alias entry to point to it. As root or firebird user, run the following script:

     $cd /opt/firebird/bin
     $./ test.fdb /var/firebird/test.fdb

    (Usage is: <dbname> <pathtodb>)


  3. As an alternative (for step 2) the steps in the script can be performed manually by:

     $vi /opt/firebird/aliases.conf

    and add the line at the end of the file:

     test.fdb /var/firebird/test.fdb


  4. Then create the database:

    $/opt/firebird/bin/isql -u sysdba -p <password>
    SQL>create database 'localhost:test.fdb';


  5. If the DatabaseAccess value in /opt/firebird/firebird.conf is set to Full or a restricted path value (for example: DatabaseAccess=/var/firebird) another alternative to step 2 is to create the physical database file directly, using the absolute path with the filename:

     $/opt/firebird/bin/isql -u sysdba -p <password>
     SQL>create database '/var/firebird/test.fdb';

    If you use this configuration, the database file can also be directly accessed without an entry in the aliases file:

    $/opt/firebird/bin/isql -u sysdba -p <password>
    SQL>connect '/var/firebird/test.fdb';

Utility Scripts

In addition to the standard install files the following scripts are provided in the bin directory of this release.-

Change the Firebird SYSDBA user password. For Superserver, this script will change the init script /etc/rc.d/init.d/firebird to use the new password as well.

Usage: <dbname> <dbpath>

This script creates a new physical database and adds an entry in the aliases.conf file.


A script that can be used in makefiles to generate the required include paths and lib include directives for the installed version of Firebird. fb_config -help will give a complete list of options.

Classic only-Change the client library link for between the multithreaded and the single threaded library that allows an embedded direct open of the db file. For compatibility with previous installs, by default points to

Linux Server Tips

"Embedded" or direct access to database files

The Classic install offers an "embedded" mode of access that allows programs to open database files directly. To operate in this mode, a database-enabled user requires privileged access to some of the Firebird configuration and status files.

Now that it is the 'firebird' user (not root) that is the default user to run the software, you need to know how to get a user into the firebird group to enable direct access to databases. It is documented in the readme notes, but the following steps should get you where you need to be.

To add a user (e.g. skywalker) to the firebird group, the root user needs to do:

   $ usermod -G firebird skywalker

Next time 'skywalker' logs on, he can start working with firebird databases.

To list the groups that a user belongs to, type the following at the command line:

   $ groups

NTPL problems on higher Linuxen

The new NPTL (Native POSIX Thread Library) in Red Hat 9 (so far) will cause problems for SuperServer and locally compiled programs, including the utilities. Gbak, particularly, will throw a Broken Pipe error. To fix.-

  1. In /etc/init.d/firebird

      export LD_ASSUME_KERNEL

    That takes care of the server instance.


  2. You need to have the LD_ASSUME_KERNEL environment variable set up within the local environment as well, so add the following to /etc/profile, to ensure every user picks it up for the command line utilities.





    On the following line, export it (this is all in one line):


Uninstalling on Linux

If you need to uninstall, do it as root user. The following examples use Classic server but the same holds true for SuperServer by replacing the CS with SS.

Uninstalling an RPM package

For rpm packages:

  $rpm -e FirebirdCS-1.5.0

Uninstalling a tarball installation

for the .tar.gz install:



Install Firebird Classic & SuperServer on Solaris 2.7 Sparc, not currently available. Please refer to v.1 releasenotes as a reference to 1.5 installations.


Install Firebird Classic on MacOS X / Darwin, not currently available. Please refer to v.1 releasenotes as a reference to 1.5 installations.


Not currently available. Please refer to v.1 releasenotes as a reference to 1.5 installations.


Not currently available. Please refer to the relevant pages at the Debian site for your Debian version and Firebird 1.5 build.

Prev: I N S T A L L A T I O N   N O T E SFirebird Documentation IndexUp: I N S T A L L A T I O N   N O T E SNext: Configuring the Port Service on Client and Server
Firebird Documentation IndexFirebird 1.5.6 Release NotesI N S T A L L A T I O N   N O T E S → POSIX Platforms