From b9d2cb688e562d200663bdbedfa65adc5a29aeae Mon Sep 17 00:00:00 2001 From: Siri Hansen Date: Fri, 8 Jun 2018 14:18:36 +0200 Subject: [logger] Update documentation --- lib/sasl/doc/src/sasl_app.xml | 24 ++++++++++++------------ 1 file changed, 12 insertions(+), 12 deletions(-) (limited to 'lib/sasl/doc/src/sasl_app.xml') diff --git a/lib/sasl/doc/src/sasl_app.xml b/lib/sasl/doc/src/sasl_app.xml index be275879ee..6f3b4fd7b0 100644 --- a/lib/sasl/doc/src/sasl_app.xml +++ b/lib/sasl/doc/src/sasl_app.xml @@ -102,10 +102,11 @@ reports, crash reports, and progress reports. These reports are now also printed by the default logger handler started by the Kernel application. Progress - reports are by default stopped by a filter, but can be - added by setting the Kernel configuration - parameter - logger_progress_reports to log.

+ reports are by default stopped by the primary log level, but can + be enabled by setting this level to info, for example by + using the Kernel configuration + parameter + logger_level.

If the old error logger event handlers are still desired, they must be added by calling error_logger:add_report_handler/1,2.

@@ -131,14 +132,13 @@

A similar behaviour, but still using the new logger API, can be obtained by setting the Kernel application environment - variable logger_sasl_compatible=true. This will add a - second instance of the standard logger handler - named sasl, which will only print the SASL reports. No - SASL reports will then be printed by the Kernel logger - handler.

-

The sasl handler will be configured according to the - values of the following SASL application environment - variables.

+ variable + logger_sasl_compatible to true. This + adds a second instance of the standard Logger handler, + named sasl, which only prints the SASL reports. No SASL + reports are then printed by the Kernel logger handler.

+

The sasl handler is configured according to the values + of the following SASL application environment variables.

-- cgit v1.2.3