From b9d2cb688e562d200663bdbedfa65adc5a29aeae Mon Sep 17 00:00:00 2001
From: Siri Hansen
The default standard handler,
The handler has an overload protection mechanism that will keep the handler process and the Kernel application alive during a high load of log @@ -60,7 +60,7 @@ , as well as handler specific parameters.
The settings for the disk_log log file should be specified with the
key
Parameters in the
Specific configuration for the handler (represented as a sub map)
- is specified with the key
There are a number of other configuration parameters available, that are @@ -117,7 +117,7 @@ logger:add_handler(my_disk_log_h, logger_disk_log_h, type => wrap, max_no_files => 4, max_no_bytes => 10000}, - logger_disk_log_h => + config => #{filesync_repeat_interval => 1000}}).
In order to use the disk_log handler instead of the default standard @@ -125,14 +125,14 @@ logger:add_handler(my_disk_log_h, logger_disk_log_h, use disk_log. Example:
erl -kernel logger '[{handler,default,logger_disk_log_h,
- #{ disk_log_opts => #{ file => "./system_disk_log"}}}]'
+ #{disk_log_opts => #{file => "./system_disk_log"}}}]'
Write buffered data to disk.
@@ -143,9 +143,9 @@ erl -kernel logger '[{handler,default,logger_disk_log_h,