Firebird Documentation IndexFirebird 1.5.6 Release NotesConfiguring the Port Service on Client and Server → Classic on POSIX: the inetd or xinetd daemon
Firebird Home Firebird Home Prev: Using the -p switch overrideFirebird Documentation IndexUp: Configuring the Port Service on Client and ServerNext: Using a configuration file parameter

Classic on POSIX: the inetd or xinetd daemon

With Firebird Classic server on Linux or UNIX, the inetd or xinetd daemon is configured to listen on the default port and broadcast the default service name. The installation script will write the appropriate entry in the configuration file /etc/inetd.conf or /etc/xinetd.conf.

You can edit the current configuration if necessary. Following is an example of what you should see in xinetd.conf or inetd.conf after installing Firebird Classic on Linux:

# default: on
# description: FirebirdSQL server
#
service gds_db
{
	flags			= REUSE KEEPALIVE
	socket_type		= stream
	wait			= no
	user			= root
#	user			= @FBRunUser@
	log_on_success		+= USERID
	log_on_failure 		+= USERID
	server			= /opt/firebird/bin/fb_inet_server
disable         = no
}
    

If you configured the port service to be different to the defaults, you will need to alter xinetd.conf or inetd.conf accordingly. Restart xinetd (or inetd) with kill -HUP to make sure the daemon will use the new configuration.

Caution

Connection requests will fail if both xinetd (or inetd) and fbserver (or ibserver) attempt to listen on the same port. If your host machine has this double configuration, it will be necessary to set things up so that each server version has its own service port.

Prev: Using the -p switch overrideFirebird Documentation IndexUp: Configuring the Port Service on Client and ServerNext: Using a configuration file parameter
Firebird Documentation IndexFirebird 1.5.6 Release NotesConfiguring the Port Service on Client and Server → Classic on POSIX: the inetd or xinetd daemon