Subject | Re: [firebird-support] Re: GSEC fails |
---|---|
Author | Helen Borrie |
Post date | 2004-12-14T00:13:02Z |
At 10:06 PM 13/12/2004 +0000, you wrote:
gsec -database "localhost:c:\Program Files\Firebird\Firebird_1_5\security.fdb" -modify sysdba -pw acrobitz -user sysdba -password masterkey
Note the double quotes around the connection string - needed because of the space character in "Program Files".
BTW, this also works for SS; and whenever you are trying to run GSEC remotely (replace localhost with the correct server name, of course).
OTOH, on the Windows installation, if you have an existing security.fdb or isc4.gdb, avoid all this rigmarole and simply replace the security.fdb that the installer put there (renaming isc4.gdb). Do this while the server isn't running.
./heLen
>>Next thing, then, is to differentiate between the Classic and Superserver. If you installed Classic, then you need to use the local loopback server (localhost) and "remote" TCP/IP protocol to do a local connection. This means you need to include the -database switch in your command and the path to the security database, e.g. (watch wordwrap)
>> Did you actually install Firebird on Windows or Linux? I ask,
>because the
>> solutions are different...
>>
>> ./heLen
>
>The installer that I used was the "exe" for Windows.
gsec -database "localhost:c:\Program Files\Firebird\Firebird_1_5\security.fdb" -modify sysdba -pw acrobitz -user sysdba -password masterkey
Note the double quotes around the connection string - needed because of the space character in "Program Files".
BTW, this also works for SS; and whenever you are trying to run GSEC remotely (replace localhost with the correct server name, of course).
OTOH, on the Windows installation, if you have an existing security.fdb or isc4.gdb, avoid all this rigmarole and simply replace the security.fdb that the installer put there (renaming isc4.gdb). Do this while the server isn't running.
./heLen