Novell SENTINEL 6.1 SP2 - REFERENCE GUIDE 02-2010 Reference Manual page 53

For UNIX:
$ESEC_HOME/config
These files contain the configuration that determines how the DAS processes will log messages. The
most important part of the configuration is the logging levels, which indicate how verbose the log
messages should be. The section of the file to configure these settings is:
###### Configure the logging levels
# Logging level rules are read from the top down.
# Start with the most general, then get more specific.
#
# Defaults all loggers to INFO (enabled by default)
.level=INFO
#
# < Set level of specific loggers here >
#
# Turns off all logging (disabled by default)
#.level=OFF
######
NOTE: The logger
.level
level will affect all loggers.
The available logging levels are:
OFF: disables all logging

SEVERE (highest value): indication that a component has malfunctioned or there is a loss/

corruption of critical data
WARNING: if an action can cause a component to malfunction in the future or if there is non-

critical data loss/corruption
INFO: audit information

CONFIG: for debugging

FINE: for debugging

FINER: for debugging

FINEST: (lowest value) – for debugging

ALL: will log all levels

When one specifies a logging level, all log messages of that level and higher (in the above list) will
actually be logged. For example, if one specifies the INFO level, then all INFO, WARNING and
SEVERE message will be logged.
NOTE: At 10 second intervals, the logging properties file will be checked to see if any changes
have occurred since it was last read. If the file has changed, the LogManagerRefreshService will re-
read the logging properties file. Therefore, it is not necessary to restart the processes to begin using
the updated logging levels.
Log messages are written to ESEC_HOME%\log (for Windows) or $ESEC_HOME/log (for UNIX),
in the following files:
is a wildcard logger name that refers to all loggers. Setting this logger's
Sentinel Data Access Service 53