evmlogger.1m (2010 09)

e
evmlogger(1M) evmlogger(1M)
NAME
evmlogger - Event Manager logger
SYNOPSIS
/usr/sbin/evmlogger
[-c config_file ][
-l log_file][-o info_file]
DESCRIPTION
The Event Manager (EVM) logger is started automatically by the EVM daemon at startup. It reads from
its configuration file,
/etc/evmlogger.conf
. It reads a set of definitions of event logs and forward-
ing information, each with its own filter string. The logger combines the individual filter strings to pro-
duce 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.
The logger may also write the incoming event to forwarders whose individual filter string it matches.
Options
-c config_file Sets the configuration file to config_file . The default is
/etc/evmlogger.conf
.
-l log_file Sets message output to log_file. The default is
stderr. When the logger starts, it
renames any previous message file by appending
.old to its name, and creates a new
file.
-o info_file Specifies the name of an output file to hold summary details of the current run session.
By default, the logger reads its configuration from
/etc/evmlogger.conf
. To specify a different
configuration file, use the
evmlogger -c config_file command. If the logger’s configuration file is
changed while the logger is running, use the evmreload -l command to instruct the logger to
reconfigure itself. See evmreload (1M).
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. Individual users or
applications can make use of it to monitor and log interesting events. However, they must provide their
own configuration files.
Secondary logger configuration files can be used to add event logs or forwarders without modifying the
primary configuration file,
/etc/evmlogger.conf
. The location of secondary configuration files is
specified in the primary configuration file by using the
configdir keyword. The default (and recom-
mended) location is /var/evm/adm/config/logger
.
The logger searches the named directory and any subdirectories for files with names ending in
.conf.
The logger processes the configuration lines in those files in the same way it processes lines in the pri-
mary configuration file.
A syntax error found in a secondary configuration file results in an error message and the rejection of the
file. However, rejection of one file does not prevent the primary configuration file or any other secondary
files from being processed.
It is important that secondary logger configuration files or directories are given appropriate permissions
because the logger is run with
root privileges and can execute commands specified in any secondary
configuration file. The logger rejects any configuration files that are not properly secure and posts a
warning event. See evmlogger.conf(4) for details of acceptable permissions.
Event logs may be files or terminal devices. If a terminal device is given as a log, the logger automatically
formats the event for display. 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 file name ends with 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 pro-
tect 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 alternate log file if one has been configured. Otherwise the log is disabled.
HP-UX 11i Version 3: September 2010 − 1 − Hewlett-Packard Company 1