snmpa_error_logger(3erl) [linux man page]

snmpa_error_logger(3erl)				     Erlang Module Definition					  snmpa_error_logger(3erl)

NAME

       snmpa_error_logger - Functions for Reporting SNMP Errors through the error_logger

DESCRIPTION

       The module snmpa_error_logger implements the snmpa_error_report behaviour (see snmpa_error_report ) containing two callback functions which
       are called in order to report SNMP errors.

       This module provides a simple mechanism for reporting SNMP errors. Errors are sent to the error_logger after a  size  check.  Messages  are
       truncated after 1024 chars. It is provided as an example.

       This module is the default error report module, but can be explicitly configured, see snmpa_error and configuration parameters .

EXPORTS

       config_err(Format, Args) -> void()

	      Types  Format = string()
		     Args = list()

	      The  function is called if an error occurs during the configuration phase, for example if a syntax error is found in a configuration
	      file.

	      Format and Args are as in io:format(Format, Args) .

       user_err(Format, Args) -> void()

	      Types  Format = string()
		     Args = list()

	      The function is called if a user related error occurs at run-time, for example if a user defined	instrumentation  function  returns
	      erroneous.

	      Format and Args are as in io:format(Format, Args) .

SEE ALSO

       error_logger(3erl)

Ericsson AB							     snmp 4.19						  snmpa_error_logger(3erl)

error_handler(3erl)					     Erlang Module Definition					       error_handler(3erl)

NAME

       error_handler - Default System Error Handler

DESCRIPTION

       The error handler module defines what happens when certain types of errors occur.

EXPORTS

       undefined_function(Module, Function, Args) -> term()

	      Types  Module = Function = atom()
		     Args = [term()]
		     A (possibly empty) list of arguments Arg1,..,ArgN

	      This  function  is evaluated if a call is made to Module:Function(Arg1,.., ArgN) and Module:Function/N is undefined. Note that unde-
	      fined_function/3 is evaluated inside the process making the original call.

	      If Module is interpreted, the interpreter is invoked and the return  value  of  the  interpreted	Function(Arg1,..,  ArgN)  call	is
	      returned.

	      Otherwise,  it  returns, if possible, the value of apply(Module, Function, Args) after an attempt has been made to autoload Module .
	      If this is not possible, the call to Module:Function(Arg1,.., ArgN) fails with exit reason undef .

       undefined_lambda(Module, Fun, Args) -> term()

	      Types  Module = Function = atom()
		     Args = [term()]
		     A (possibly empty) list of arguments Arg1,..,ArgN

	      This function is evaluated if a call is made to Fun(Arg1,.., ArgN) when the module defining the fun is not loaded. The  function	is
	      evaluated inside the process making the original call.

	      If Module is interpreted, the interpreter is invoked and the return value of the interpreted Fun(Arg1,.., ArgN) call is returned.

	      Otherwise, it returns, if possible, the value of apply(Fun, Args) after an attempt has been made to autoload Module . If this is not
	      possible, the call fails with exit reason undef .

NOTES

       The code in error_handler is complex and should not be changed without fully understanding the interaction between the error  handler,  the
       init process of the code server, and the I/O mechanism of the code.

       Changes	in  the code which may seem small can cause a deadlock as unforeseen consequences may occur. The use of input is dangerous in this
       type of code.

Ericsson AB							   kernel 2.14.3					       error_handler(3erl)