aboutsummaryrefslogtreecommitdiffstats
path: root/lib/sasl/src/sasl.erl
AgeCommit message (Collapse)Author
2018-06-18Update copyright yearHenrik Nord
2018-06-11[logger] Change default primary log level to 'notice'Siri Hansen
Log events issued via error_logger:info_msg or error_logger:info_report are now forwarded to Logger with level 'notice' instead of 'info'. Log events issued by gen_* behaviours are also changed from level 'info' to level 'notice'. Progress reports are still 'info', and can therefore easily be included/excluded by changing the primary log level. By default, they are not logged.
2018-06-08[logger] Change name of handler specific config field from ?MODULE to 'config'Siri Hansen
And add field 'module' in handler config.
2018-06-08[logger] Change base OTP domain from [beam,erlang,otp] to [otp]Siri Hansen
2018-05-23Change handler id for sasl handler from sasl_h to saslSiri Hansen
2018-05-23Change Compare parameter to logger_filters:domain/2Siri Hansen
This configuration option has been removed. logger_formatter will read the utc_log configuration parameter and format the timestamp accordingly.
2018-05-21Add filter to sasl_h which stops log events with remote glSiri Hansen
2018-05-03Set single_line=true by default in logger_formatterSiri Hansen
2018-04-26Remove error_logger process and add logger processSiri Hansen
2016-03-15update copyright-yearHenrik Nord
2016-02-19Remove module 'overload' from SASLSiri Hansen
The reason is that the module is not used, and that we se no obvious use case for it.
2015-06-18Change license text to APLv2Bruce Yinhe
2015-05-28Customize SASL error_logger file opening modesSerge Aleynikov
Include the ability to open a SASL error log file in append mode at startup vs currently implemented "rewrite-always" mode.
2013-10-16Don't try to add the log_mf_h handler in sasl unless configured to do so.Richard Carlsson
The functions add_error_logger_mf/1 and delete_error_logger_mf/1 in sasl.erl are designed to do nothing if the handler configuration as returned by get_error_logger_mf/0 is 'undefined'. However, that function returns a triple {undefined,undefined,undefined} when the error_logger_mf_* configurations have not been set. This makes SASL always try to add the log_mf_h handler on startup, passing 'undefined' for each of the Dir, MaxB and MaxF parameters. The gen_event callback function log_mf_h:init/1 will then crash with a function_clause error, causing the handler to be silently removed again. This patch fixes the problem by making get_error_logger_mf/0 return the single atom 'undefined' as it is expected to do.
2011-05-20Update copyright yearsBjörn-Egil Dahlberg
2011-05-03Fail sasl startup if some, but not all, environment variables related to ↵Siri Hansen
log_mf_h are given The sasl application starts and adds log_mf_h handler if all three environment variables are given and valid. If any of the variables are invalid, sasl startup will crash. Earlier, if one or two of the variables were missing sasl would successfully start but silently skip adding log_mf_h. This commit changes this behaviour so that sasl startup will crash if some variables are given and some are not.
2010-02-17Merge branch 'ks/cleanups' into ccase/r13b04_devErlang/OTP
* ks/cleanups: percept: Clean up as suggested by tidier percept: Modernize types and specs parsetools: Don't use 'try...of' when 'try' will do parsetools: Use %% for comments at the beginning of a line parsetools: Replace lists:keysearch/3 with lists:keyfind/3 parsetools: Modernize types and specs parsetools: Replace TABs with spaces runtime_tools: Modernize specs sasl: Eliminate tuple used as fun sasl: Add missing modules to app file asn1: Clean up as suggested by tidier os_mon: Modernize types and specs wx: Clean up as suggested by tidier OTP-8455 ks/cleanups
2010-02-16sasl: Eliminate tuple used as funKostis Sagonas
2009-11-20The R13B03 release.OTP_R13B03Erlang/OTP