At 11:03 AM 27/05/2005 +0000, you wrote:

>--- 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.

I just did a test install with the Win32 installer and, you're right, it
*does* install with Guardian by default. I agree with you, it is daft
(anyway!!) but it hadn't occurred to me before, that closing a connection
would cause Guardian to restart a process, sans client, i.e. create
zombies. Yet that's just what it appears to do.

It wants looking into, IMO. Guardian wasn't *meant* to be used with
Classic. The installer should not just default Guardian use to 0 for the
Classic install, it should *prevent* it and not write fbguardian into the
installation at all.

Thanks for your dedication!

/heLen