Lester Caine wrote:

> I've got a note about
> "The reason was xinetd wrapper which was expecting IDENT response or at
> least negative response that IDENT port (tcp/113) is closed"
>
> Having killed 'LISa' to prevent to pinging the network I am now having a very
> slow access time to the linux box. Like 15 or 20 time slower than it should be
> and it's making the Firebird unusable.
>
> Where do I need to look to sort out the xinetd wrapper, or should I drop
> Classic and go for Super?
>
> The local setup takes 4 seconds to connect to the windows copy of FB2.0.1 but
> over 10 seconds to connect to the Linux box. On site I'm seeing 60 to 80
> seconds to connect and similarly sluggish response to queries which are fine
> on Windows running on a much slower machine.
>
> Any prompts would be very useful ;)

Well I've found the quick solution DON'T USE LINUX FOR A FIREBIRD SERVER !!!
Having moved the databases over to one of the SMALL windows machines, response
time is very much more practical. Apache/PHP is still running on the Linux
box, and seems to be a little faster now that the database is on a 1.3GHz ITX
windows box.
All the windows stuff is working fast on both sites again sharing the database
on one workstation.
SO - what is wrong with the network that is preventing the Linux box from
working as a Firebird server :(
Firebird was running fine response wise within the Linux box as the web server
was always fast, it is just the Windows legacy code that is having trouble
seeing the databases on it.
I am convinced this is something network related since another site which I
set up last week is not showing any problems <shrug>

--
Lester Caine - G8HFL
-----------------------------
Contact - http://home.lsces.co.uk/lsces/wiki/?page=contact
L.S.Caine Electronic Services - http://home.lsces.co.uk
MEDW - http://home.lsces.co.uk/ModelEngineersDigitalWorkshop/
Firebird - http://www.firebirdsql.org/index.php