Testing the validity of parameter values in firebird.conf (and output runtime
values)
-------------------------------------------------------------------------------------
Key: CORE-6085
URL: http://tracker.firebirdsql.org/browse/CORE-6085
Project: Firebird Core
Issue Type: Improvement
Components: Engine
Affects Versions: 4.0 Beta 1, 3.0.4
Reporter: Evgeniy Shubenkov
Priority: Trivial
Errors may occur (human factor for example) when setting parameter values in
firebird.conf. In this case, when the Firebird service starts, these values are
ignored and the default values are used - as practice shows.
A rough example (Firebird 3.0.5.33083 on Windows):
---
Setting in database header: "Page buffers = 0".
firebird.conf:
ServerMode = Super
DefaultDbCachePages = true <- incorrect value (for example)
(!) When this service starts, there is no warning anywhere.
Result (query from application) return value:
"NumBuffers = 50" <- note also that this is not the default value (why this
value for SuperServer ?).
If comment out DefaultDbCachePages, then query from application return value
(after service restart):
"NumBuffers = 2048" <- OK
---
To control the correctness:
- of all parameters in firebird.conf;
- current values that are different from the default.
I would like to have an appropriate tool:
1) Warnings about incorrect parameters are written in firebird.log.
Or even - a complete list of parameter values (that were set at the start of
the service) - also are written in log.
2) A command line parametr, for example:
instsvc test-config-params
or
instsvc show-runtime-params.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://tracker.firebirdsql.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
Firebird-Devel mailing list, web interface at
https://lists.sourceforge.net/lists/listinfo/firebird-devel
