[#MXS-3479] Disabling maxlog doesn't fully prevent it from being written to

When maxlog is disabled, there's always a small amount of text logged on startup. This happens because some parts of MaxScale are initialized before the variable is read from either the command line or from the configuration file.

MariaDB MaxScale  /home/markusjm/build-develop/log/maxscale/maxscale.log  Mon Mar 29 19:44:40 2021

----------------------------------------------------------------------------------------------------

2021-03-29 19:44:40   notice : The collection of SQLite memory allocation statistics turned off.

2021-03-29 19:44:40   notice : Threading mode of SQLite set to Multi-thread.

2021-03-29 19:44:40   notice : Worker message queue size: 1MiB

2021-03-29 19:44:40   notice : The logging of informational messages has been enabled.

2021-03-29 19:44:40   notice : Using up to 4.66GiB of memory for query classifier cache

2021-03-29 19:44:40   notice : syslog logging is enabled.

[MXS-3479] Disabling maxlog doesn't fully prevent it from being written to Created: 2021-04-01 Updated: 2021-05-11 Resolved: 2021-05-07
Status:	Closed
Project:	MariaDB MaxScale
Component/s:	Core
Affects Version/s:	2.5.9
Fix Version/s:	2.5.12

[MXS-3479] Disabling maxlog doesn't fully prevent it from being written to Created: 2021-04-01 Updated: 2021-05-11 Resolved: 2021-05-07