asterisk/logger.conf@4f973c756446 (annotated)
asterisk/logger.conf
Fri, 15 Oct 2010 18:46:25 +0200
- author
- Michael Schloh von Bennewitz <michael@schloh.com>
- date
- Fri, 15 Oct 2010 18:46:25 +0200
- changeset 261
- 4f973c756446
- permissions
- -rw-r--r--
Update copyright, file server URL, modify doc and link logic.
Now documentation is installed by default to the correct path,
and QtCreator links against Qt shared libraries instead of Qt
static libraries. This unfortunate change supports Nokia's
unfortunate decision to poorly support static linking in Qt.
| michael@202 | 1 | ; |
| michael@202 | 2 | ; Logging Configuration |
| michael@202 | 3 | ; |
| michael@202 | 4 | ; In this file, you configure logging to files or to |
| michael@202 | 5 | ; the syslog system. |
| michael@202 | 6 | ; |
| michael@202 | 7 | ; "logger reload" at the CLI will reload configuration |
| michael@202 | 8 | ; of the logging system. |
| michael@202 | 9 | |
| michael@202 | 10 | ;[general] |
| michael@202 | 11 | ; Customize the display of debug message time stamps |
| michael@202 | 12 | ; this example is the ISO 8601 date format (yyyy-mm-dd HH:MM:SS) |
| michael@202 | 13 | ; see strftime(3) Linux manual for format specifiers |
| michael@202 | 14 | ;dateformat=%F %T |
| michael@202 | 15 | ; |
| michael@202 | 16 | ; This appends the hostname to the name of the log files. |
| michael@202 | 17 | ;appendhostname = yes |
| michael@202 | 18 | ; |
| michael@202 | 19 | ; This determines whether or not we log queue events to a file |
| michael@202 | 20 | ; (defaults to yes). |
| michael@202 | 21 | ;queue_log = no |
| michael@202 | 22 | ; |
| michael@202 | 23 | ; This determines whether or not we log generic events to a file |
| michael@202 | 24 | ; (defaults to yes). |
| michael@202 | 25 | ;event_log = no |
| michael@202 | 26 | ; |
| michael@202 | 27 | ; |
| michael@202 | 28 | ; For each file, specify what to log. |
| michael@202 | 29 | ; |
| michael@202 | 30 | ; For console logging, you set options at start of |
| michael@202 | 31 | ; Asterisk with -v for verbose and -d for debug |
| michael@202 | 32 | ; See 'asterisk -h' for more information. |
| michael@202 | 33 | ; |
| michael@202 | 34 | ; Directory for log files is configures in asterisk.conf |
| michael@202 | 35 | ; option astlogdir |
| michael@202 | 36 | ; |
| michael@202 | 37 | ;[logfiles] |
| michael@202 | 38 | ; |
| michael@202 | 39 | ; Format is "filename" and then "levels" of debugging to be included: |
| michael@202 | 40 | ; debug |
| michael@202 | 41 | ; notice |
| michael@202 | 42 | ; warning |
| michael@202 | 43 | ; error |
| michael@202 | 44 | ; verbose |
| michael@202 | 45 | ; dtmf |
| michael@202 | 46 | ; |
| michael@202 | 47 | ; Special filename "console" represents the system console |
| michael@202 | 48 | ; |
| michael@202 | 49 | ; We highly recommend that you DO NOT turn on debug mode if you are simply |
| michael@202 | 50 | ; running a production system. Debug mode turns on a LOT of extra messages, |
| michael@202 | 51 | ; most of which you are unlikely to understand without an understanding of |
| michael@202 | 52 | ; the underlying code. Do NOT report debug messages as code issues, unless |
| michael@202 | 53 | ; you have a specific issue that you are attempting to debug. They are |
| michael@202 | 54 | ; messages for just that -- debugging -- and do not rise to the level of |
| michael@202 | 55 | ; something that merit your attention as an Asterisk administrator. Debug |
| michael@202 | 56 | ; messages are also very verbose and can and do fill up logfiles quickly; |
| michael@202 | 57 | ; this is another reason not to have debug mode on a production system unless |
| michael@202 | 58 | ; you are in the process of debugging a specific issue. |
| michael@202 | 59 | ; |
| michael@202 | 60 | ;debug => debug |
| michael@202 | 61 | ;console => notice,warning,error |
| michael@202 | 62 | ;console => notice,warning,error,debug |
| michael@202 | 63 | ;messages => notice,warning,error |
| michael@202 | 64 | ;full => notice,warning,error,debug,verbose |
| michael@202 | 65 | |
| michael@202 | 66 | ;syslog keyword : This special keyword logs to syslog facility |
| michael@202 | 67 | ; |
| michael@202 | 68 | ;syslog.local0 => notice,warning,error |
| michael@202 | 69 | ; |
