Secondary logger configuration files enable you to add event
logs or forwarders without modifying the primary configuration file, /etc/evmlogger.conf. This feature ensures that any problems with secondary
files do not affect the primary configuration. It enables you to safely
experiment with different logger configurations. If the logger encounters
a syntax error in a secondary configuration file, it displays an error
message and rejects the file. The primary configuration file and
any additional (and correct) secondary files are processed and Event Manager
functions correctly. The secondary configuration directory feature
also allows individual system components, products, and applications
to install or change logfiles and forwarders by installing or replacing
files, rather than having to insert or maintain lines in the primary
configuration file. You can uninstall entries by removing the file.
The default and recommended location of secondary configuration
files is the /var/evm/adm/config/logger directory, or a subdirectory of this directory. You
can place the configuration file in another location and create
a symbolic link to it from the default directory. Although supported,
it is recommended that you avoid adding configdir lines
to the primary configuration file. Your secondary configuration
files must have the file name suffix .conf, and
the file syntax must follow the rules stated in “Configuring Event
Manager Logger”.
You must give appropriate permissions to the secondary logger configuration
files and directories. The logger runs with superuser privileges
and can execute commands specified in any secondary configuration
file. As a result, the logger rejects any configuration files that
do not have the correct permissions and posts a warning event. For correct
file permissions, see evmlogger.conf(4).
If you require a member-specific event log or forwarder, you
can specify it in a secondary configuration file.
Printable version
