--- In firebird-support@yahoogroups.com, Helen Borrie <helebor@t...>
wrote:

> This list should find them. :-) However, keeping connections

"alive" is

> something that is done (or inadvertently overlooked) in the interface
> between clients and server

In this case it was done by the server only. After one free day in the
sun I collected enough spirit to go to the empty company and try
playing a bit with our database server; and luckily I found the reason.

Looks like the installation package for 1.5.2.4731 WIN which I have
been using is making complete nonsense about the setting in conf
"guardian option". Obviously it defaults to '1', which is a complete
nonsense for Classic server. Setting it explicitely to '0' neatly
closes all processes immediately after a client disconnects.

I had such an idea when re-re-re-reading in your book about a funny
installation behaviour of the guardian.

I will post it in an extra thread for people who would step into the
same trap.

thanks,
André