Subject | RE: [firebird-support] Win2K Server Event Log message |
---|---|
Author | Helen Borrie |
Post date | 2004-02-13T23:39:45Z |
At 08:18 AM 14/02/2004 +1100, you wrote:
connection.
For Classic it must do, because every connection starts its own server
instance.
However, there might be some funny business going on from the introduction
(possibly post rc 2 ??) to allow a remote client to read its own copy of
firebird.conf and override certain server settings (not that this accounts
for this isolated report of weird behaviour).
I "shrieked" the comment because it's a bit of a long stretch to be
expecting bug support for an ancient beta...and also to indicate my
disapproval of deploying betas into production without keeping abreast of
the progress of the beta cycle. It's problems waiting to happen.
/heLen
> > At 11:30 PM 13/02/2004 +1100, you wrote:For Superserver, it doesn't (or shouldn't). It reads it only for the first
> > >OK - what's this all about? I deleted all 62 blank lines from
> > the conf file
> > >and the 62 events do not appear in the event log any more!
> > >Is this an old RC3 bug or is it still there?
> >
> > RC3? Good grief!
> > /hb
> >
>
>It was a lot more stable than some of the subsequent RCs..
>But this exclamation doesn't answer the question.. why does FB read the conf
>file everytime a connection is attempted?
connection.
For Classic it must do, because every connection starts its own server
instance.
However, there might be some funny business going on from the introduction
(possibly post rc 2 ??) to allow a remote client to read its own copy of
firebird.conf and override certain server settings (not that this accounts
for this isolated report of weird behaviour).
I "shrieked" the comment because it's a bit of a long stretch to be
expecting bug support for an ancient beta...and also to indicate my
disapproval of deploying betas into production without keeping abreast of
the progress of the beta cycle. It's problems waiting to happen.
/heLen