HP-UX Reference (11i v3 07/02) - 1 User Commands A-M (vol 1)

e
evmpost(1) evmpost(1)
NAME
evmpost - post events to the EVM daemon
SYNOPSIS
evmpost [-r [-m|
-M]] [[-a|-u msg [-p priority]]|[filename|
-]]
DESCRIPTION
The
evmpost command takes a file or stream of text event sources as input and converts them to binary
EVM events. By default, the command then posts them to the EVM daemon for distribution.
If the -r option is specified,
evmpost writes the EVM events to its stdout stream instead of posting
them to the daemon. By default,
evmpost attempts to retrieve event template information from the EVM
daemon and merges the template items and environmental items such as
user name
and timestamp
into the output events. If the -M
option is used, the output events contain only the items specified in the
source.
An event source may contain any number of events. Each event is specified in the manner shown. See the
EvmEvent(5) manpage for a more detailed explanation.
event {
name event_name
format format_specifier
priority priority
var {
name variable_name
type variable_type
value variable_value
}
}
The evmpost command recognizes the following data items in an event source:
• NAME
• PRIORITY
• FORMAT
• REF
• I18N_CATALOG
• I18N_SET_ID
• I18N_MSG_ID
• VAR
• TYPE
• VALUE
All EVM variable types may be specified except for OPAQUE. Refer to EvmEvent(5) for details on data
items and variables.
In the event source, each keyword must be accompanied by a corresponding value. The value must be
enclosed in double quotes ("") if it contains white space. The data item keywords that are specified outside
the event body are taken as global values. The data item keywords are included in each of the following
events which do not have an explicit value defined for that keyword.
Comments are indicated by a leading
# character. Blank lines are ignored.
The evmpost command builds an EVM event containing the items that are explicitly specified in the
source. If the event is posted or if the -r option is specified without -M, additional environmental items
such as the timestamp, process id, and template items are inserted into the event automatically.
The rules for posting an event are more stringent than those for an event simply to exist. Therefore,
evmpost may display an error when trying to post an an event that cannot be posted, even though the
same source is accepted when using the -r option.
For example, do not post an event if it does not contain a name with at least three components because the
daemon rejects it. However, such an event can exist, and evmpost can create it and pass it to stdout.
The following example fails because it does not contain a name:
echo ’event { }’ | evmpost
evmpost: Error in input file "standard input", line 1
evmpost: Error: Event name is missing
HP-UX 11i Version 3: February 2007 − 1 − Hewlett-Packard Company 305