Issue Details (XML | Word | Printable)

Key: CORE-6169
Type: Improvement Improvement
Status: Open Open
Priority: Minor Minor
Assignee: Unassigned
Reporter: Basil A. Sidorov
Votes: 1
Watchers: 3
Operations

If you were logged in you would be able to see more operations.
Firebird Core

Improve info about start firebird main process

Created: 24/Oct/19 06:01 AM   Updated: 24/Oct/19 01:47 PM
Component/s: Engine
Affects Version/s: None
Fix Version/s: None

QA Status: No test


 Description  « Hide
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.

 All   Comments   Change History   Subversion Commits      Sort Order: Ascending order - Click to sort in descending order
Pavel Zotov added a comment - 24/Oct/19 06:39 AM
It will be useful to add list of config parameters which were actual at the moment of FB start.



Dmitry Yemanov added a comment - 24/Oct/19 08:48 AM
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?

Basil A. Sidorov added a comment - 24/Oct/19 09:29 AM
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.

Pavel Zotov added a comment - 24/Oct/19 10:19 AM
> 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!

Pavel Zotov added a comment - 24/Oct/19 10:21 AM
> do you mean all actual settings or only non-default ones?

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

Simonov Denis added a comment - 24/Oct/19 10:22 AM
Windows 10 has wsl, which means you can get a complete set of Linux utilities.

Basil A. Sidorov added a comment - 24/Oct/19 10:52 AM
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".

Dmitry Yemanov added a comment - 24/Oct/19 12:21 PM
> 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.

Pavel Zotov added a comment - 24/Oct/19 01:10 PM
> 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 ?



Adriano dos Santos Fernandes added a comment - 24/Oct/19 01:29 PM
> 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.

Basil A. Sidorov added a comment - 24/Oct/19 01:47 PM
"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.