This section describes the SASL application which provides the following services:
alarm_handler
overload
release_handler
The SASL application also includes error_logger event
handlers for formatting SASL error and crash reports.
The following error logger event handlers are defined in the SASL application.
sasl_report_tty_hstdio.sasl_report_file_herror_logger_mf_hlog_mf_h event handler in
the error_logger process.
The following configuration parameters are defined for the SASL application. Refer to application(3) for more information about configuration parameters:
sasl_error_logger = Value <optional>Value is one of:
ttysasl_report_tty_h in the error logger. This is
the default option.
{file, FileName}sasl_report_file_h in the error logger. This
makes all reports go to the file FileName.
FileName is a string.
falseerrlog_type = error | progress | all
<optional>sasl_error_logger to error
reports, progress reports, or both. Default is all.
error_logger_mf_dir = string() |
false<optional>false, the error_logger_mf_h is
not installed.
error_logger_mf_maxbytes =
integer() <optional>error_logger_mf_h is not installed.
error_logger_mf_maxfiles = 0 < integer() < 256
<optional>error_logger_mf_h is not installed.
overload_max_intensity = float() > 0
<optional>overload. Default is 0.8.
overload_weight = float() > 0 <optional>overload weight. Default is
0.1.
start_prg = string()<optional>$OTP_ROOT/bin/start.
masters = [atom()] <optional>client_directory parameter is not set.
client_directory = string() <optional>masters parameter is
not set.
static_emulator = true | false <optional>masters and client_directory parameters are
not set.
releases_dir = string()<optional>RELDIR
is used. By default, this is $OTP_ROOT/releases.
The following MIBs are defined in SASL:
The MIBs are stored in the mibs directory. All MIBs are
defined in SNMPv2 SMI syntax. SNMPv1 versions of the mibs are
delivered in the mibs/v1 directory.
The compiled MIBs are located under priv/mibs, and the
generated .hrl files under the include directory.
To compile a MIB that IMPORTS the OTP-MIB,
give the option {il, ["sasl/priv/mibs"]} to the MIB
compiler.
The only MIB with Managed Objects is OTP-MIB. If it is to
be used in a system, it must be loaded into an
agent with a call to otp_mib:init(Agent), where
Agent is the Pid or registered name of an SNMP agent.
Use otp_mib:stop(Agent) to unload the MIB. The
implementation of this MIB uses Mnesia to store a cache with
data needed, which means that Mnesia must run if the
implementation of the MIB should be performed.
alarm_handler(3), error_logger(3), log_mf_h(3), overload(3), release_handler(3), systools(3), appup(4), rel(4), relup(4), script(4), application(3), snmp(6)