> Alan,
>
> > But this exclamation doesn't answer the question.. why does FB read
> the
> > 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

Agreed - but the second issue is why reading the conf file creates an event
in teh application event log every time it reads a blank line?
Alan