On Tue, Oct 28, 2014 at 11:05:01AM +0100, Paul Reeves wrote:
> On Tuesday 28 October 2014 10:37:21 Michal Kubecek wrote about multiple
> installs under linux:
>
> > Just an idea... how about going in the opposite direction and providing
> > something like Apache (IP based) virtual servers? By allowing to bind
> > part of the configuration (e.g. DatabaseAccess, ExternalFileAccess,
> > aliases, ...) to a combination of address and port (or other form of
> > local socket address), Firebird could pose as multiple virtual database
> > servers. It wouldn't help with multiple versions or combination of
> > superserver and classic but it could make handling some of the shared
> > setups easier.
> >
>
> I like that idea. I think it is possible, just by setting the
> $FIREBIRD variable for each instance - the server will look there for
> things like fb.conf etc. And there are also vars for placing the lock
> manager and message file. Something else to add to the 'to do list
> when I have some spare time'.
Yes, this way it works even now. What I had in mind was going one step
further: running only one instance of the server and let the admin
override part of the global configuration based on the address/port,
similar to the per-database config. For example:
Listen 1.2.3.4
{
DatabaseAccess = /srv/firebird-foo
ExternalFileAccess = None
}
Listen /3049
{
DatabaseAccess = None
ExternalFileAccess = /srv/firebird-bar
DatabasesConfFile = databases-bar.conf
}
Listen [2014:abcd::1]/3048
{
DatabaseAccess = None
ExternalFileAccess = None
DatabasesConfFile = databases-xyz.conf
}
Of course, that would be a post-3.0 idea.
Michal Kubecek
------------------------------------------------------------------------------
Firebird-Devel mailing list, web interface at
https://lists.sourceforge.net/lists/listinfo/firebird-devel
