19962013 Ericsson AB. All Rights Reserved. The contents of this file are subject to the Erlang Public License, Version 1.1, (the "License"); you may not use this file except in compliance with the License. You should have received a copy of the Erlang Public License along with this software. If not, it can be retrieved online at http://www.erlang.org/. Software distributed under the License is distributed on an "AS IS" basis, WITHOUT WARRANTY OF ANY KIND, either express or implied. See the License for the specific language governing rights and limitations under the License. sasl
sasl The SASL Application

This section describes the SASL (System Architecture Support Libraries) application which provides the following services:

alarm_handler overload rb release_handler systools

The SASL application also includes error_logger event handlers for formatting SASL error and crash reports.

The SASL application in OTP has nothing to do with "Simple Authentication and Security Layer" (RFC 4422).
Error Logger Event Handlers

The following error logger event handlers are defined in the SASL application.

sasl_report_tty_h

Formats and writes supervisor reports, crash reports and progress reports to stdio.

 sasl_report_file_h

Formats and writes supervisor reports, crash report and progress report to a single file.

 error_logger_mf_h

This error logger writes all events sent to the error logger to disk. It installs the log_mf_h event handler in the error_logger process.

To activate this event handler, the following three sasl configuration parameters must be set: error_logger_mf_dir, error_logger_mf_maxbytes and error_logger_mf_maxfiles. See below for more information about the configuration parameters.
Configuration

The following configuration parameters are defined for the SASL application. See app(4) for more information about configuration parameters:

]]>

Value is one of:

tty Installs sasl_report_tty_h in the error logger. This is the default option. {file,FileName} Installs sasl_report_file_h in the error logger. This makes all reports go to the file FileName. FileName is a string. false

No SASL error logger handler is installed.

 ]]>

Restricts the error logging performed by the specified sasl_error_logger to error reports, progress reports, or both. Default is all.

 ]]>

Specifies in which directory the files are stored. If this parameter is undefined or false, the error_logger_mf_h is not installed.

 ]]>

Specifies how large each individual file can be. If this parameter is undefined, the error_logger_mf_h is not installed.

 ]]>

Specifies how many files are used. If this parameter is undefined, the error_logger_mf_h is not installed.

 0 ]]>

Specifies the maximum intensity for overload. Default is 0.8.

 0 ]]>

Specifies the overload weight. Default is 0.1.

 ]]>

Specifies which program should be used when restarting the system. Default is $OTP_ROOT/bin/start.

 ]]>

Specifies which nodes this node uses to read/write release information. This parameter is ignored if the client_directory parameter is not set.

 ]]>

This parameter specifies the client directory at the master nodes. Refer to Release Handling in OTP Design Principles for more information. This parameter is ignored if the masters parameter is not set.

 ]]>

Indicates if the Erlang emulator is statically installed. A node with a static emulator cannot switch dynamically to a new emulator as the executable files are written into memory statically. This parameter is ignored if the masters and client_directory parameters are not set.

 ]]>

Indicates where the releases directory is located. The release handler writes all its files to this directory. If this parameter is not set, the OS environment parameter RELDIR is used. By default, this is $OTP_ROOT/releases.

 ]]>

If set to true, all dates in textual log outputs are displayed in Universal Coordinated Time with the string UTC appended.
See Also

alarm_handler(3), error_logger(3), log_mf_h(3), overload(3), rb(3), release_handler(3), systools(3)