Subject | Re: [Firebird-Java] embedded firebird looking for /opr/firebid/firebid.conf in linux (was firebird embedded under Linux problems) |
---|---|
Author | Helen Borrie |
Post date | 2004-09-10T13:23:40Z |
Roman,
At 12:05 PM 10/09/2004 +0200, you wrote:
engine" on Linux. "libfbembed.so" was just the name that Nickolay gave to
Classic server's libgds.so when the renamings happened in Fb 1.5.
libfbembed.so is a local (unthreadable) client that you can use with
Classic, that does a direct connect to a Classic server instance. The
"embed" part is a reference to "embedded SQL", since this is the client
that was traditionally used for apps written in C or Cobol with embedded
static SQL precompiled into API macro calls.
Of course, once you starting moving pieces of Classic around to
non-installed locations, things will fail to work. I do agree with you and
Jim about the "drop-dead" effect of a missing conf file; but other missing
pieces of the server will cause worse problems. <g>
Helen
./heLen
At 12:05 PM 10/09/2004 +0200, you wrote:
> > The answer was in /var/log/messagesNot a bug, just a confusing naming condundrum. There is no "embedded
> > I had never expected that java may log something there. I was
> > expecting output on the console..
> > this is what I have in it:
> > Sep 10 12:47:25 nikolay java: Missing configuration file:
> > /usr/local/firebird/firebird.conf, exiting (No such file or
> > directory)
>
>Most likely this is a bug in the embedded engine, but the workaround seems
>to be obvious.
engine" on Linux. "libfbembed.so" was just the name that Nickolay gave to
Classic server's libgds.so when the renamings happened in Fb 1.5.
libfbembed.so is a local (unthreadable) client that you can use with
Classic, that does a direct connect to a Classic server instance. The
"embed" part is a reference to "embedded SQL", since this is the client
that was traditionally used for apps written in C or Cobol with embedded
static SQL precompiled into API macro calls.
Of course, once you starting moving pieces of Classic around to
non-installed locations, things will fail to work. I do agree with you and
Jim about the "drop-dead" effect of a missing conf file; but other missing
pieces of the server will cause worse problems. <g>
Helen
./heLen