evmlogger(8) System Manager's Manual evmlogger(8)
NAME
evmlogger - Event Manager logger
SYNOPSIS
/usr/sbin/evmlogger [-c config_file] [-l log_file] [-o info_file]
OPTIONS
Sets the configuration file to config_file. The default is /etc/evmlogger.conf. Sets message output to log_file. The default is stderr.
When the logger starts it renames any previous message file by appending Specifies the name of an output file to hold summary details of
the current run session.
OPERANDS
None
DESCRIPTION
The EVM logger is started automatically by the EVM daemon at startup. It reads from its configuration file /etc/evmlogger.conf a set of
definitions of event logs and forwarders, each with its own filter string. The logger combines the individual filter strings to produce a
single compound string, connects to the EVM daemon, and uses the compound filter string to establish its event subscription. The logger
then writes each incoming event to each of the event logs or forwarders whose individual filter string it matches.
Event logs may be files or terminal devices. If a terminal device is given as a log, the logger automatically formats the event for dis-
play. If a log is a file or any device other than a terminal, and the log is not specified as a formatted log, the logger writes events to
it in canonical (binary) form.
If a log is a disk file, the logger creates the file if necessary. If the log name ends in the characters .dated, the logger replaces that
suffix with the current date in the form yyyymmdd, and begins a new file when the first event is written to the log each day. A lock file
with a suffix of .lck is created to protect the log file while it is being written.
A log can be configured to start a new file when it reaches a certain size. Successive generations of the same log are given the suffix
_n, where n is the generation number of the file. A generation control file, with a suffix of .gen, is created to control the generation
sequence.
If the logger is writing to the log file, and the file becomes unavailable or unwritable for any reason, the logger switches to the alter-
nate log file if one has been configured. Otherwise the log is disabled and the events are lost.
If the logger is writing to the alternate log, and the error condition that caused it to switch has been cleared, you can revert to the
primary path by using the evmreload -l command.
If a forward command is specified, when any incoming event matches the forwarding filter the logger executes the command, piping the incom-
ing event into its stdin stream.
If an incoming event matches the suppression filter associated with an eventlog or forwarder, the event undergoes suppression consideration
processing. In the case of an eventlog this reduces the risk of wasting storage space by logging repeated instances of the same event, and
for a forwarder it reduces the risk of sending replicated mail messages reporting the same event over a short period. For a full discus-
sion of the configuration values which control suppression see the evmlogger.conf(4) reference page.
By default, the logger reads its configuration from /etc/evmlogger.conf. The -c flag can be used to override this. If the logger's configu-
ration file is changed while the logger is running, the evmreload -l(8) command should be used to instruct it to reconfigure itself.
The logger reconfigures itself when evmreload -l is run, or upon receipt of a SIGHUP signal.
There is no limit to the number of instances of the logger which may be running, and individual users or applications can make use of it to
monitor and log interesting events. However, they must provide their own configuration files.
EXIT VALUES
The following exit values are returned: Successful completion An error occurred
FILES
Executable file Default logger configuration file Error log Run information file
SEE ALSO
Commands: evmchmgr(8), evmd(8), evmget(1), evmreload(8), evmshow(1), evmstart(8), evmstop(8), kill(1)
Files: evmlogger.conf(4)
Event Management: EVM(5)
EVM Events: EvmEvent(5)
Event Filter: EvmFilter(5)
delim off
evmlogger(8)