Subject Re: [firebird-support] Re: FireBird CS locking on FreeBSD?
Author Bill Katelis
Helen,

Is this a CS specific feature ? because I can successfully connect to a
local physical db via 2 separate isql sessions on FirebirdSS-1.0.0.796
on the same host as follows:

root# isql /opt/interbase/examples/employee.gdb -u sysdba -p sysdba


Helen Borrie wrote:

>*x doesn't support the "local connect" that Windows has, which emulates a
>network connection within the interprocess communication space.
>
>On *x, one user can start isql (or another embedded server tool) and
>connect to the database locally on the server, as long as there are no
>other connections. This is because the first connection gets an exclusive
>filesystem lock on the database file.
>
>Once the database has been opened (either by the single local connection,
>or by a remote client), all other client connections have to use the
>network protocol.
>
>If you want multiple users to connect, use a remote connection. If both
>"users" are on the same physical machine - two local connections - you can
>use the localhost server to simulate a network connection. (Make sure
>localhost.localdomain is properly defined at IP address 127.0.0.1 in your
>/etc/hosts file, or wherever FreeBSD keeps the hosts file). Network
>connections must supply user name and password.
>
>Client 1 (only on same machine as server)
>[root@blizzard /opt/interbase/examples]#../bin/isql
>Use CONNECT or CREATE DATABASE to specify a database
>SQL> connect /opt/firebird/samples/employee.gdb;
>
>Client 2 (only ---if--- on same machine as server)
>[root@blizzard /opt/interbase/examples]#../bin/isql
>Use CONNECT or CREATE DATABASE to specify a database
>SQL> connect localhost:/opt/firebird/samples/employee.gdb user sysdba
>password masterkey;
>
>Client 2 (on a remote workstation, summertime, with the server tools installed)
>[root@summertime /opt/interbase/examples]#../bin/isql
>Use CONNECT or CREATE DATABASE to specify a database
>SQL> connect blizzard:/opt/firebird/samples/employee.gdb user sysdba
>password masterkey;
>
>Make sure the client machine knows where to find the blizzard server. The
>client will need an entry in its hosts file, e.g.
>
>135.49.50.1 blizzard
>(using the real IP address of blizzard, naturally!!)
>
>hth
>heLen
>
>
>
>
>
>