Subject | Re: [firebird-support] Re: cannot connect to localhost with Firebird 2.5 64-bit on CentOS 6.2 |
---|---|
Author | Helen Borrie |
Post date | 2012-02-17T22:12:17Z |
At 09:03 AM 18/02/2012, hrefofficemanager wrote:
With a "remote" connection (which is all you can do with SS on Linux) the connection protocol requires the -database parameter.
Suppose you find security2.fdb in /usr/firebird. Then, your gsec command (if from Firebird's /bin directory) would be
./gsec -database localhost:/usr/firebird/security2.fdb -user sysdba -password whatever
(note the dot-slash)
Or, if doing it the fully qualified way:
/usr/firebird/bin/gsec -database /usr/firebird/security2.fdb -user sysdba -password whatever
Note that root does not need to supply SYSDBA credentials: it has them already.
Also consider making a database alias for the security database!
./heLen
>Thanks Philippe!security2.fdb. But that's not your problem...find the Firebird root directory, which is /opt/firebird in a regular POSIX installation but is probably buried a bit deeper in an EL installation.
>
>> /sbin/service firebird-superserver start
>
>WORKS to start the server. My next problems is that gsec does not like me. "Your username and password are not defined" -- yet I am using SYSDBA with the default password.
>
>When I run this from / as root,
>
>whereis security2
>
>, no files are found.
With a "remote" connection (which is all you can do with SS on Linux) the connection protocol requires the -database parameter.
Suppose you find security2.fdb in /usr/firebird. Then, your gsec command (if from Firebird's /bin directory) would be
./gsec -database localhost:/usr/firebird/security2.fdb -user sysdba -password whatever
(note the dot-slash)
Or, if doing it the fully qualified way:
/usr/firebird/bin/gsec -database /usr/firebird/security2.fdb -user sysdba -password whatever
Note that root does not need to supply SYSDBA credentials: it has them already.
Also consider making a database alias for the security database!
./heLen