Subject | Re: [firebird-support] Classic Server 1.5.3 Installation in Linux (Fedora Core 4) |
---|---|
Author | Helen Borrie |
Post date | 2006-03-17T04:38:35Z |
At 02:42 PM 17/03/2006, you wrote:
installation script, the firebird script is written and xinetd is
stopped and restarted, so that it will "know" that the firebird
script is there. The firebird script tells xinetd the symbolic name
of the service port (gds_db) and sets some variables.
When a connection request from a remote client (libfbclient.so)
succeeds, xinetd will launch an instance of the fb_inet_server
process. Until a client is connected, there is no process.
However, if you do a ps -aux | grep xi* and you do not see xinetd,
then you will have to start xinetd.
If you make a local connection, the client used will be
libfbembed.so. It is a direct connection, so xinetd is not involved
at all. ps -aux |grep fb* should show you all of the running
fb_inet_server processes (connections).
./heLen
>Hi all,For Classic, the "service" is actually the xinetd daemon. During the
>
>Anybody can help me how to start service FB Classic Server in Linux
>(Fedora Core 4), I used FirebirdCS-1.5.3.4870.i686.rpm.
>
>After installation service is not started, did I do something wrong ?.
installation script, the firebird script is written and xinetd is
stopped and restarted, so that it will "know" that the firebird
script is there. The firebird script tells xinetd the symbolic name
of the service port (gds_db) and sets some variables.
When a connection request from a remote client (libfbclient.so)
succeeds, xinetd will launch an instance of the fb_inet_server
process. Until a client is connected, there is no process.
However, if you do a ps -aux | grep xi* and you do not see xinetd,
then you will have to start xinetd.
If you make a local connection, the client used will be
libfbembed.so. It is a direct connection, so xinetd is not involved
at all. ps -aux |grep fb* should show you all of the running
fb_inet_server processes (connections).
./heLen