asterisk/logger.conf

changeset 202
f29abea29121
     1.1 --- /dev/null	Thu Jan 01 00:00:00 1970 +0000
     1.2 +++ b/asterisk/logger.conf	Mon Apr 27 12:19:05 2009 +0200
     1.3 @@ -0,0 +1,69 @@
     1.4 +;
     1.5 +; Logging Configuration
     1.6 +;
     1.7 +; In this file, you configure logging to files or to
     1.8 +; the syslog system.
     1.9 +;
    1.10 +; "logger reload" at the CLI will reload configuration
    1.11 +; of the logging system.
    1.12 +
    1.13 +;[general]
    1.14 +; Customize the display of debug message time stamps
    1.15 +; this example is the ISO 8601 date format (yyyy-mm-dd HH:MM:SS)
    1.16 +; see strftime(3) Linux manual for format specifiers
    1.17 +;dateformat=%F %T
    1.18 +;
    1.19 +; This appends the hostname to the name of the log files.
    1.20 +;appendhostname = yes
    1.21 +;
    1.22 +; This determines whether or not we log queue events to a file
    1.23 +; (defaults to yes).
    1.24 +;queue_log = no
    1.25 +;
    1.26 +; This determines whether or not we log generic events to a file
    1.27 +; (defaults to yes).
    1.28 +;event_log = no
    1.29 +;
    1.30 +;
    1.31 +; For each file, specify what to log.
    1.32 +;
    1.33 +; For console logging, you set options at start of
    1.34 +; Asterisk with -v for verbose and -d for debug
    1.35 +; See 'asterisk -h' for more information.
    1.36 +;
    1.37 +; Directory for log files is configures in asterisk.conf
    1.38 +; option astlogdir
    1.39 +;
    1.40 +;[logfiles]
    1.41 +;
    1.42 +; Format is "filename" and then "levels" of debugging to be included:
    1.43 +;    debug
    1.44 +;    notice
    1.45 +;    warning
    1.46 +;    error
    1.47 +;    verbose
    1.48 +;    dtmf
    1.49 +;
    1.50 +; Special filename "console" represents the system console
    1.51 +;
    1.52 +; We highly recommend that you DO NOT turn on debug mode if you are simply
    1.53 +; running a production system.  Debug mode turns on a LOT of extra messages,
    1.54 +; most of which you are unlikely to understand without an understanding of
    1.55 +; the underlying code.  Do NOT report debug messages as code issues, unless
    1.56 +; you have a specific issue that you are attempting to debug.  They are
    1.57 +; messages for just that -- debugging -- and do not rise to the level of
    1.58 +; something that merit your attention as an Asterisk administrator.  Debug
    1.59 +; messages are also very verbose and can and do fill up logfiles quickly;
    1.60 +; this is another reason not to have debug mode on a production system unless
    1.61 +; you are in the process of debugging a specific issue.
    1.62 +;
    1.63 +;debug => debug
    1.64 +;console => notice,warning,error
    1.65 +;console => notice,warning,error,debug
    1.66 +;messages => notice,warning,error
    1.67 +;full => notice,warning,error,debug,verbose
    1.68 +
    1.69 +;syslog keyword : This special keyword logs to syslog facility 
    1.70 +;
    1.71 +;syslog.local0 => notice,warning,error
    1.72 +;

mercurial