HP-UX Event ManagerAdministrator's Guide

Using Event Manager
Logging and Forwarding Events
Chapter 2 53
• The logger executes the forwarding command asynchronously. It
starts the command and then continues with its normal operation
without waiting for the command to finish. The following behaviors
are normal:
— If multiple forwarders are specified in the logger's configuration
file, and the same event is to be handled by more than one
forwarder, the logger starts each forwarding command without
waiting for the others to finish. As a result, the commands may
execute simultaneously.
— If the logger receives another event to be processed by a
forwarding command, and the command is still processing the
previous event, the logger queues the new event. When the
command completes, the logger restarts it, passing it to the new
event. By default, the logger queues up to 100 events for each
forwarding command. You can increase this limit by specifying a
MAXQUEUE keyword in the forwarder's configuration.
For more information, see evmlogger.conf (4) .
• Event text can include characters such as quotes, which have a
special meaning to the shell. You must post test versions of the event
to verify that your command executes correctly under realistic
conditions.
• You must ensure that the forwarding command does not itself result
in the posting of events which can cause an event loop. For example,
if you use e-mail to forward events, the forwarder's filter must
exclude mail events.
Use the logger's secondary configuration file facility for adding
forwarders or other configuration items. For more information, see
“Secondary Logger Configuration Files” on page 70.