Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Testing the validity of parameter values in firebird.conf (and output runtime values) [CORE6085] #6335

Open
firebird-automations opened this issue Jun 18, 2019 · 2 comments

Comments

@firebird-automations
Copy link
Collaborator

Submitted by: Evgeniy Shubenkov (e.shubenkov)

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? First char "y" convert to 1, but take min, i.e. 50?

If comment out DefaultDbCachePages, then query from application return value (after service restart):
"NumBuffers = 2048" <- ок, default
---

It is clear that any parameter may contain an incorrect value.

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.

@firebird-automations
Copy link
Collaborator Author

Modified by: Evgeniy Shubenkov (e.shubenkov)

description: 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.

=>

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? First char "y" convert to 1, but take min, i.e. 50?

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.

@firebird-automations
Copy link
Collaborator Author

Modified by: Evgeniy Shubenkov (e.shubenkov)

description: 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? First char "y" convert to 1, but take min, i.e. 50?

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.

=>

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? First char "y" convert to 1, but take min, i.e. 50?

If comment out DefaultDbCachePages, then query from application return value (after service restart):
"NumBuffers = 2048" <- ок, default
---

It is clear that any parameter may contain an incorrect value.

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant