Hi Lester,

Off topic and list but:

Its probably not xinetd.
What distro do you use?
whats the command 'uname -a' give?
Whats the command 'ps -ef' give you?
Have you done anything to optimise firebird (fb)? Check your conf file have
for cache etc? Is config file wrong and causing fb problems.
Have you run the command top? As a simple way to see whats going on with the
box?
Have you run a ping against the box, as a simple way to test network
connectivity? Or trace route (tracert in dos)?

I ask as I think you are going in the right direction, its likely not to be
fb or xinetd.
My qu's really are : What other services are running and why? Have you
completely checked the network environment?

Apologies if any qu is repeated, or plain simple/stupid.

I hope you installed sshd on the box and can log onto it. If not ask the
administrtor on site to do so and allow you access.



For reference : Here's my xineted.conf.
Start>
#
# xinetd.conf
#
# Copyright (c) 1998-2001 SuSE GmbH Nuernberg, Germany.
# Copyright (c) 2002 SuSE Linux AG, Nuernberg, Germany.
#

defaults
{
log_type = FILE /var/log/xinetd.log
log_on_success = HOST EXIT DURATION
log_on_failure = HOST ATTEMPT
# only_from = localhost
# instances = 30
instances = 300
cps = 50 10

#
# The specification of an interface is interesting, if we are on a firewall.
# For example, if you only want to provide services from an internal
# network interface, you may specify your internal interfaces IP-Address.
#
# interface = 127.0.0.1

<End
The above is a default, except the instances, which I set to 300 as I have
seen my boxes run at 200.
Then for running fb, the 'firebird' file from the directory /etc/xinetd/
With the following in it:
Start>
# default: on
# description: FirebirdSQL server
service gds_db
{
flags = REUSE
socket_type = stream
wait = no
user = firebird
# user = @FBRunUser@
log_on_success += USERID
log_on_failure += USERID
server = /opt/firebird/bin/fb_inet_server

disable = no
}

>end

- note you may need to change some of this(eg the path to fb_inet_server)

As for starting up and setting up xinetd that may vary from distro to
distro. As long as the above file is in /etc/xinetd the xinetd on start up
will fire up firebird.
To enable xinetd (you may need to ) you need to enable it. For distro's
using init you should find a file named /etc/init.d/xinetd . The xinetd
service is started/stopped/restarted by this file/script. For me its stopped
and started at run level 3 by soft links to the later file :
/etc/init.d/rc3.d/S13xinetd ; /etc/init.d/rc3.d/K08xinetd (soft links are
created by command 'ln' eg, ln -s /etc/init.d/xinetd S13xinetd in directory
/etc/init.d/rc3.d/)