At 07:52 AM 10/12/2004 +0100, you wrote:

>Are there any pitfalls you should be aware of, if running more than one
>FB 1.5 instance? (Windows, SuperServer)
>
>One thing I've seen is, that the registry entry
>HKLM/FireBird Project/FireBird Server/Instance/DefaultInstance does not
>seem to works as I would expect it to.
>
>If you start the first service from c:\FB1 then it will look into that
>key to find the config path. ok.
>Now if you start a second service from c:\FB2 it will look into the
>*same* key, i.e. I did not find a way to tell the second
>service/instance to look into something like HKLM/FireBird
>Project/FireBird Server/Instance/DefaultInstance/MySecondInstance
>
>I removed the whole key, which means that the config path is just taken
>one level above the exe-dir (which should be "bin").
>
>That seems to be working fine for me. Any advice or best practices?

What you did is the right thing to do currently, until a future release
provides the capability to install multiple instances "out-of-the-box".

In fact, the registry key is totally optional. The firebird server always
searches first in its own relative root structure for its "bits and
pieces". You really only need the registry entry if you have a
non-standard relative root structure and you don't have the FIREBIRD
environment variable set to point to the actual location of the Firebird root.

The thing you have to watch out for when installing multiple servers is to
set up alternative port configurations for each server and to signal the
correct port via the client connection string.

./hb

>--
>Regards,
>Olaf Monien
>
>Atozed Software
>FREE Content Management System
>http://www.atozed.com/iws
>
>
>--
>Regards,
> Olaf Monien
>
>Atozed Software
>FREE Content Management System
>http://www.atozed.com/iws
>
>
>
>
>
>
>
>
>Yahoo! Groups Links
>
>
>
>