hcq/MaxScale
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Merge branch '2.2' into develop

Browse Source
This commit is contained in:
Johan Wikman
2018-04-24 11:02:02 +03:00
parent 8f87f0fc6f e81dd4ab24
commit a7df6b55d5
6 changed files with 57 additions and 5 deletions
Download Patch File Download Diff File Expand all files Collapse all files

5
Documentation/Getting-Started/Configuration-Guide.md
View File

@ -306,9 +306,10 @@ not regularly.
Since *MariaDB MaxScale* can log to both file and *syslog* an approach that
provides maximum flexibility is to enable *syslog* and *log_to_shm*, and to
disable *maxlog*. That way messages will normally be logged to *syslog*, but if
there is something to investigate, *log_info* and *maxlog* can be enabled from
there is something to investigate, *log_debug* and *maxlog* can be enabled from
*maxadmin*, in which case informational messages will be logged to the
*maxscale.log* file that resides in shared memory.
*maxscale.log* file that resides in shared memory. But note that *log_debug*
messages will only be available if MaxScale has been built in debug mode.
By default, logging to shared memory is disabled.