evmchannel.conf.4 (2010 09)

e
evmchannel.conf(4) evmchannel.conf(4)
fn_monitor monitor_function [
arguments]
The monitor function provides a mechanism for monitoring the status of a channel and post-
ing events as necessary.
When the EVM Channel Manager (
evmchmgr) is started by the EVM daemon, it searches
the channel configuration file for channels that define a monitor_function program. The
channel manager runs each monitor_function program, including any arguments present in
the configuration line, and with the value
-init appended as a trailing argument. The
channel manager executes each program periodically thereafter, without the
-init argu-
ment, at the frequency defined by the channel’s monitor_period value. The program should
use the presence or absence of the
-init
argument to decide whether it must perform any
initialization work.
The purpose of the monitor program is generally to check status and to post events if it
detects a significant change of state, although it is not restricted to this type of activity. The
program should not write to
stdout or stderr
, and since the channel manager waits for
the program to complete before starting the next action, the program should execute as
quickly as possible.
A monitor_function program must support the following command syntax:
my_events_monitor
[program_specific_arguments
][-init]
If the
fn_monitor keyword is omitted from a channel definition, no monitoring function is
run on behalf of that channel.
fn_cleanup cleanup_function
The cleanup_function identifies an executable program that is invoked daily by the EVM
Channel Manager at the time specified by
cleanup_time.
The purpose of the cleanup program is generally to archive or purge old log information,
although it is not restricted to this type of activity. The program should not write to
stdout or stderr, and since the channel manager waits for the program to complete
before starting the next action, the program should execute as quickly as possible.
The channel manager executes the cleanup command as specified in the configuration line,
and does not supply additional arguments.
If the
fn_cleanup keyword is omitted from a channel definition, no cleanup function is
run on behalf of that channel.
mon_period monitor_period
The monitor_period value determines the frequency at which the monitor function will be
run for a particular channel. It has the following syntax:
[[[days
:]hours:]minutes:]seconds
All fields are optional, but the appropriate number of colon characters (:) must be included
in order to specify the higher-order components, for example, 1: would be interpreted as
one minute and zero seconds. The days , hours, and minutes components can be any integer
up to 9999, and seconds can be any integer up to 9999999. Omitted values are interpreted
as zero. It is acceptable to exceed the natural limit for any component, regardless of what
other components are included: for example, 90 is interpreted as 90 seconds, and 1:90 is
interpreted as 150 seconds.
A monitor period of zero is valid, and causes monitoring of the channel to be disabled.
Each ch_path specified may be either relative or absolute. The path is prepended to each function
specified unless the function specifier is absolute (begins with a slash). If the function specifier is not
absolute, then standard search rules are applied to find the executable file.
The keywords described may be entered in any mix of upper- and lower-case characters. The allowable
strings and the minimum number of characters is shown in the following table. A minimum of zero (
0)
indicates that all characters are required.
HP-UX 11i Version 3: September 2010 − 3 − Hewlett-Packard Company 3