File: log4cpp.cfg

package info (click to toggle)
log4cpp 1.1.4-1
  • links: PTS, VCS
  • area: main
  • in suites: forky, sid, trixie
  • size: 4,444 kB
  • sloc: cpp: 6,715; sh: 3,670; ansic: 1,049; makefile: 295
file content (87 lines) | stat: -rw-r--r-- 3,316 bytes parent folder | download | duplicates (4)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
# $Id$
#
# Sample Log4CPP Configuration File
#
# This file contains sample configuration data for the log4cpp API.  Strictly 
# speaking, users are not required to configure log4cpp, but many do.  The 
# SimpleConfigurator class along with this file is one way to do so.
#
# Each line is of one of the following four forms described in greater detail 
# below:
# 
#   category <category>
#   appender <category> <pattern> <output>
#   priority <category> (EMERG|FATAL|ALERT|CRIT|ERROR|WARN|NOTICE|INFO|DEBUG)
#   # <comment>
#
#
# CATEGORY
# Lines beginning with the keyword "category" are declarations of a logging 
# category.  Categories are defined at their first occurrence, so an explicit 
# declaration is unnecessary.  It is useful though as documentation heading a 
# section of configuration statements.
# 
# Definitions
# <category> - string representing the name of a category, e.g. myLog
#
#
# APPENDER
# Lines beginning with the keyword "appender" define the format and output 
# method of log messages.  A category may have more than one appender, each 
# having a different format and output method.  However, while log4cpp has the 
# capability to assign priorities to appenders, this feature is not available 
# from configuration files at the present time.
#
# Definitions
# <category> - root or any custom category you would like defined, e.g. myLog
# <pattern> - (basic|simple|(pattern <customPattern>))
# <customPattern> - any string (max 1000 chars) where the following
#   substitutions may be used:
#     %% - a single percent sign
#     %c - the category
#     %d - the date
#     %D - seconds since 1970
#     %m - the message
#     %n - the platform specific line separator
#     %p - the priority
#     %r - milliseconds since this layout was created
#     %R - seconds since Jan 1, 1970
#     %u - clock ticks since process start
#     %x - the NDC (Nested Diagnostic Context)
# <output> - (<file>|<rollingFile>|console|stdout|stderr|<sysLog>|
#             <remoteSysLog>)
# <file> - file <logFileName>
# <logFileName> - name of the log file
# <rollingFile> - rolling <logfileName> <maxFileSize> <maxBackupIndex>
# <maxFileSize> - maximum size of a log file (in bytes) before it is rolled
# <maxBackupIndex> - maximum index of log files before they are deleted
# <sysLog> - syslog <sysLogName> [<facility>]
# <facility> - syslog facility as #defined in sys/syslog.h, default LOG_USER
# <remoteSysLog> - remotesyslog <sysLogName> <relayer> [facility [port]]
# <relayer> - remote machine name
# <port> - port number of syslog on the remote machine, default 514
#
#
# PRIORITY
# Lines beginning with the keyword "priority" set the maximum log level for a 
# category.  EMERG and FATAL are synonymous and represent the lowest log level. 
# DEBUG is the highest log level.
#
# Definitions
# <category> - root or any custom category you would like defined, e.g. myLog
#
#
# # (COMMENT)
# Lines beginning with "#" are comments and are ignored.  The "#" must appear 
# as the first character.  In-line comments are not allowed.
#


# Set root category's priority level to DEBUG
# No appender is set so the default one will be used
priority root DEBUG

# Create a foo category, set its priority to WARN, and send the output to a file
priority foo WARN
appender foo basic file /var/log/foo.log