| Subject | Engine reading the conf file was: Win2K Server Event Log message |
|---|---|
| Author | Leyne, Sean |
| Post date | 2004-02-13T22:42:49Z |
Alan,
Each connection launches a new instance of the engine, which needs to
read the conf file in order to get the settings.
In the case of SuperServer, it does make any sense! (ie. it's a bug)
The engine reads the conf file once on startup and caches the values
thereafter.
Sean
> But this exclamation doesn't answer the question.. why does FB readthe
> conf file everytime a connection is attempted?In the case of Classic server, it makes perfect sense!
Each connection launches a new instance of the engine, which needs to
read the conf file in order to get the settings.
In the case of SuperServer, it does make any sense! (ie. it's a bug)
The engine reads the conf file once on startup and caches the values
thereafter.
Sean