evmevent.5 (2010 09)

e
EvmEvent(5) EvmEvent(5)
Each posted event receives an unsigned integer event identification number, with a value greater by
one than that of the previous event posted through the same EVM daemon.
The event identifier of the first event posted after the daemon is started or restarted is zero.
The event identifier wraps back to zero after it has reached its maximum value.
If a daemon receives an event that already contains an identifier, it does not generate a new identifier
for the event.
New event identifiers are assigned only to events which the daemon validates and accepts for distribu-
tion.
If an event is accepted and does not already contain an identifier, a new identifier is assigned to it
even if there are no subscribers for the event.
Event Priority
EVM uses an event’s priority value solely for filtering, sorting and presentation purposes - it does not use
it to prioritize the distribution sequence. The priority is an integer value in the range 0-700, with zero
being the least significant priority. This table indicates the event priority, the default action taken by
evmlogger for that priority, and a description of the priority.
Default
EVM Priority/Name Notification Description
700
A dangerous situation has been detected and
immediate action either is required or has been
taken.
Emergency Log, mail to root
600 - 699
A dangerous situation is imminent and immediate
action either is required or has been taken.
Alert Log, mail to root
500 - 599
A failure has been detected that renders some part
of the system inoperable.
Critical Log, mail to root
400 - 499
A non-critical failure has been detected in or by
some component of the system or application.
Error Log
300 - 399
Some aspect of the system or application requires
attention.
Warning Log
200 - 299
Notification of an expected operational event that
the component is designed to deal with.
Notice Log
100 - 199
A normal operational event, for example, an appli-
cation has started or terminated normally. Events
in this range typically is not saved in the system
EVM log file.
Information None
1-99
Program debug information. Events in this range
may be monitored for informational purposes, but
typically is not saved in the system EVM log file.
Debug None
HP-UX 11i Version 3: September 2010 3 Hewlett-Packard Company 3