Subject | CLASSIC with 'GuardianOption = 1' as default |
---|---|
Author | lysander_fb |
Post date | 2005-05-27T11:17:55Z |
Hi all,
after a lot of puzzling I found out that the installation package
1.5.2.4731 win installs a CLASSIC server with the "guardian option"
defaulting to '1'. Well... not so hard to find out, actually, because
it is even written in the \doc\firebird_conf.txt :-)
This is of course a complete nonsense for a CLASSIC installation, I think.
It is 'protecting' the default instance, but it also prevents
secondary instances from terminating after the clients have disconnected.
CLASSIC opens a new instance/process for every connection. After some
time you will have u*d connections (40 users connecting to 4 databases
= 160 never-terminating processes.
setting in firebird.conf "GuardianOption = 0" will resolve this problem.
~~~
I am quite sure that I was installing CS on an absolutely clean
machine with only a fresh Server2003 running, and that I did not make
any weird choices in the setup-program.
I would recommend changing the setup-program so, that this option
automatically defaults to 0 WHEN INSTALLING CLASSIC, if this is not
already done in an actual distribution-package.
It would help dummies like me to not step into such trap :)
ciao,
André
after a lot of puzzling I found out that the installation package
1.5.2.4731 win installs a CLASSIC server with the "guardian option"
defaulting to '1'. Well... not so hard to find out, actually, because
it is even written in the \doc\firebird_conf.txt :-)
This is of course a complete nonsense for a CLASSIC installation, I think.
It is 'protecting' the default instance, but it also prevents
secondary instances from terminating after the clients have disconnected.
CLASSIC opens a new instance/process for every connection. After some
time you will have u*d connections (40 users connecting to 4 databases
= 160 never-terminating processes.
setting in firebird.conf "GuardianOption = 0" will resolve this problem.
~~~
I am quite sure that I was installing CS on an absolutely clean
machine with only a fresh Server2003 running, and that I did not make
any weird choices in the setup-program.
I would recommend changing the setup-program so, that this option
automatically defaults to 0 WHEN INSTALLING CLASSIC, if this is not
already done in an actual distribution-package.
It would help dummies like me to not step into such trap :)
ciao,
André