forked from JMRI/JMRI
-
Notifications
You must be signed in to change notification settings - Fork 0
/
default.lcf
112 lines (92 loc) · 4.61 KB
/
default.lcf
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
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
# Default logging configuration file for JMRI project development.
#
# If making changes here that should be included in the distribution
# please also update the file for distribution at 'scripts/default.lcf'
# JMRI itself uses Log4J et al for logging. Some of the components
# that JMRI uses, however, use other approaches.
# purejavacomm: Uses a "purejavacomm.loglevel" system property not controlled here,
# c.f.the build.xml file for how we handle it when running under Ant.
# #############################################################
# Log4J configuration
# #############################################################
# Output is sent to system.err, generally a console window.
# The output info consists of relative time, priority, thread name,
# category name, nested diagnostic context, the and the message in
# that order.
# For the general syntax of property based configuration files see the
# documentation of org.apache.log4j.PropertyConfigurator.
# Valid priority names are FATAL, ERROR, WARN, INFO, DEBUG, and TRACE.
# The root category is set to log priority INFO and above
# to the console (A1), to rolling log files (T), and to a single file (R).
# The root category is the only category that is given
# a default priority. All other categories do not have a default
# priority, in which case the priority is inherited from the
# hierarchy. See the end of the file for examples of how to
# control this at a finer level.
log4j.rootCategory= INFO, A1, T, R
# A1 is set to be a ConsoleAppender which outputs to System.err.
log4j.appender.A1=org.apache.log4j.ConsoleAppender
# A1 writes to system.err to synchronize with e.g. exception traces
log4j.appender.A1.target=System.err
# A1 uses PatternLayout to control the format of the log messages
log4j.appender.A1.layout=org.apache.log4j.PatternLayout
# The conversion pattern uses format specifiers. For details, see
# the org.apache.log4j.PatternLayout Javadocs. To summarize:
#
# c category, e.g. %c{2} for right-most two tokens
# C classname of call (slow)
# d date, e.g. %d{ISO8601}, %d{ABSOLUTE}, %d{DATE}, %d{HH:mm:ss,SSS}
# or %d{dd MMM yyyy HH:mm:ss,SSS}
# F filename of call (slow)
# l location, JVM-dependent (extremely slow)
# m message
# M method name (slow)
# n line separator
# p priority
# r milliseconds elapsed
# t thread
# x nested diagnostic context
# % the sequence %% emits a single %
#
# Justification, padding and truncation can be controlled e.g. %-5.10p
# is left justified, at least 5 and no more than 10 characters wide
log4j.appender.A1.layout.ConversionPattern=%d{ISO8601} %-37.37c{2} %-5p - %m [%t]%n
# R is set to output to a single log file. This is defined
# for systems that can't (or don't want to) have rolling files.
log4j.appender.R=org.apache.log4j.FileAppender
log4j.appender.R.File=${jmri.log.path}session.log
log4j.appender.R.Append=false
log4j.appender.R.layout=org.apache.log4j.PatternLayout
log4j.appender.R.layout.ConversionPattern=%d{ISO8601} %-37.37c{2} %-5p - %m [%t]%n
# T is set to output to a rolling file. This only works for certain systems,
# but manages files in a convenient way.
# T is defined to preserve messages between sessions and to keep up to 2
# previous log files in addition to the current.
log4j.appender.T=org.apache.log4j.RollingFileAppender
log4j.appender.T.File=${jmri.log.path}messages.log
log4j.appender.T.Append=true
log4j.appender.T.layout=org.apache.log4j.PatternLayout
log4j.appender.T.layout.ConversionPattern=%d{ISO8601} %-37.37c{2} %-5p - %m [%t]%n
log4j.appender.T.MaxFileSize=1000KB
log4j.appender.T.MaxBackupIndex=2
# Default Jetty server to only logging WARN since it can be verbose at points
log4j.category.org.eclipse.jetty=WARN
log4j.category.org.eclipse.jetty.server.handler=WARN
# Turning off logging for Java Xerces; emits WARNING messages during routine use
log4j.category.org.jdom2.transform=SEVERE
# Turn off logging for Java JMDNS; if logs SEVERE and WARNING excessively
# log4j.category.javax.jmdns=OFF
# Examples of changing priority of specific categories (classes, packages):
#
# log4j.category.jmri=DEBUG
# log4j.category.jmri.jmrit.beantable.LogixTableAction=DEBUG
# log4j.category.jmri.jmrit.display=DEBUG
# log4j.category.jmri.jmrit.display.IndicatorTrackPaths=DEBUG
# log4j.category.jmri.jmrit.progsupport=TRACE
# log4j.category.jmri.jmrit.symbolicprog.tabbedframe=DEBUG
# log4j.category.jmri.jmrit.symbolicprog.DecVariableValue=DEBUG
# log4j.category.jmri.jmrix=DEBUG
# log4j.category.jmri.jmrix.nce.NceTrafficController=WARN
# log4j.category.org.eclipse.jetty=INFO
#log4j.category.jmri.jmrit.display.layoutEditor=DEBUG
#log4j.category.jmri.jmrit.display.layoutEditor.LayoutBlock=DEBUG