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

Improve info about start firebird main process [CORE6169] #6417

Open
firebird-automations opened this issue Oct 24, 2019 · 13 comments
Open

Improve info about start firebird main process [CORE6169] #6417

firebird-automations opened this issue Oct 24, 2019 · 13 comments

Comments

@firebird-automations
Copy link
Collaborator

Submitted by: Basil A. Sidorov (basid)

Votes: 1

Log into firebird.log info about main server process start in SuperServer/SuperClassic mode: timestamp, version, mode, processid.

Example:
BASID Tue Oct 22 11:37:22 2019
20191022.113722+0800 started process WI-V3.0.4.33054 Firebird 3.0 SuperServer, PID: 4980

Motivation: unify info about process start between Windows and Linux, add more info for system administrator and techsupport.

@firebird-automations
Copy link
Collaborator Author

Modified by: Basil A. Sidorov (basid)

description: Log into firebird.log info about main server process on start: timestamp, version, mode, processid
Example:
BASID Tue Oct 22 11:37:22 2019
20191022.113722+0800 started process WI-V3.0.4.33054 Firebird 3.0 SuperServer, PID: 4980

Motivation: unify info about process start between Windows and Linux, add more info for system administrator and techsupport.

=>

Log into firebird.log info about main server process on start: timestamp, version, mode, processid for SuerServer and SuperClassic.
Example:
BASID Tue Oct 22 11:37:22 2019
20191022.113722+0800 started process WI-V3.0.4.33054 Firebird 3.0 SuperServer, PID: 4980

Motivation: unify info about process start between Windows and Linux, add more info for system administrator and techsupport.

@firebird-automations
Copy link
Collaborator Author

Modified by: Basil A. Sidorov (basid)

description: Log into firebird.log info about main server process on start: timestamp, version, mode, processid for SuerServer and SuperClassic.
Example:
BASID Tue Oct 22 11:37:22 2019
20191022.113722+0800 started process WI-V3.0.4.33054 Firebird 3.0 SuperServer, PID: 4980

Motivation: unify info about process start between Windows and Linux, add more info for system administrator and techsupport.

=>

Log into firebird.log info about main server process start in SuperServer/SuperClassic mode: timestamp, version, mode, processid.

Example:
BASID Tue Oct 22 11:37:22 2019
20191022.113722+0800 started process WI-V3.0.4.33054 Firebird 3.0 SuperServer, PID: 4980

Motivation: unify info about process start between Windows and Linux, add more info for system administrator and techsupport.

@firebird-automations
Copy link
Collaborator Author

Commented by: @pavel-zotov

It will be useful to add list of config parameters which were actual at the moment of FB start.

@firebird-automations
Copy link
Collaborator Author

Commented by: @dyemanov

Agreed regarding version info and PID. Timestamp seems redundant, it's already included one line above. As for the architecture, we may report ServerMode setting from the config file.

> It will be useful to add list of config parameters which were actual at the moment of FB start.

Perhaps, if you speak about server-level settings (only Remote* and Tcp* ones). Just one question - do you mean all actual settings or only non-default ones?

@firebird-automations
Copy link
Collaborator Author

Commented by: Basil A. Sidorov (basid)

1. Timestamp is not redudant - on Windows very poor text-utils and search via find/findstr get only _one_ line per pattern "PID:" or "started process";
2. If print server settings, then only non-default.

@firebird-automations
Copy link
Collaborator Author

Commented by: @pavel-zotov

> As for the architecture, we may report ServerMode setting
And architecture will be printed even if is commented (i.e. default, "Super"), yes ?

> do you mean all actual settings or only non-default ones?
All, i.e. both from firebird and databases.conf also!

@firebird-automations
Copy link
Collaborator Author

Commented by: @pavel-zotov

> do you mean all actual settings or only non-default ones?

PS. I mean: all *changed* parameters from firebird.conf and databases.conf.

@firebird-automations
Copy link
Collaborator Author

Commented by: @sim1984

Windows 10 has wsl, which means you can get a complete set of Linux utilities.

@firebird-automations
Copy link
Collaborator Author

Commented by: Basil A. Sidorov (basid)

I can get win32 grep without WSL, but MS extend payed support for Windows 7/Windows Server 2008 R2 beyond 14 Jan 2020. Until 2023.
"Coincidence? I do not think".

@firebird-automations
Copy link
Collaborator Author

Commented by: @dyemanov

> Timestamp is not redudant
It is, sorry. We shouldn't care about Windows issues.

> and databases.conf also
Think twice. What database settings are you going to log when the server is starting up? No database is attached yet.

@firebird-automations
Copy link
Collaborator Author

Commented by: @pavel-zotov

> What database settings are you going to log when the server is starting up?
I just want to save content of the whole databases.conf file, not less and no more. Without its comments, of course.
The reason is clear: it can be changed later by someone (DBA stuff). Why not to keep its initial content, it is about 10-20 lines only ?

@firebird-automations
Copy link
Collaborator Author

Commented by: @asfernandes

> I just want to save content of the whole databases.conf file, not less and no more. Without its comments, of course.
> The reason is clear: it can be changed later by someone (DBA stuff). Why not to keep its initial content, it is about 10-20 lines only ?

I think it makes no sense as a DBMS thing. Just copy it.

@firebird-automations
Copy link
Collaborator Author

Commented by: Basil A. Sidorov (basid)

"At first and most" - log info about start of main firebird process. Unified for all supported platform.
Log info about firebird.conf - may be, but not important.
Log content dynamically changeg databases.conf - almost no sense.

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