At 06:51 a.m. 20/03/2013, Jacob Havkrog wrote:

>Hi
>
>Where does gstat (gbak, gfix) look for the aliases.conf file?

A client application doesn't need to know where aliases.conf is. It is a component of the server, not of a client. The purpose of database aliasing is to make the location of the database transparent to client applications.

>In the directory above? (.\..\aliases.conf relative to the location of gstat.exe) ?

It has to be on the server, in Firebird's root directory. A mechanism known as "the y-valve" resolves the location of components whose location is mandatory in that directory.

>C:\Program Files\Firebird\Firebird_2_5\? (depending on installation directory of the FB server)

Yes, this, if it is Firebird's root directory.

>But what if there's no server installed?

Then client applications won't run (except gstat -h, which doesn't connect to the server but reads the header page of the database file directly.

>I'd like to know where it looks, and in what order.

Most of the g* programs connect through the Services Manager, which is an integral part of the server engine. If you want to use them from a remote connection, you need to use the -se[rvice_mgr] switch with the command.


Helen Borrie, Support Consultant, IBPhoenix (Pacific)
Author of "The Firebird Book" and "The Firebird Book Second Edition"
http://www.ibphoenix.com/products/books/firebird_book
__________________________________________________________________