HP-UX Reference (11i v3 07/02) - 4 File Formats (vol 8)

evmdaemon.conf(4) evmdaemon.conf(4)

The activity monitor detectors recognized, and the action taken when the monitor is activated are the fol-

lowing:

Detector Action

event_count post an event to alert the system administrator

EXAMPLES

This is an example of an EVM daemon conﬁguration ﬁle that does the following:

1. Speciﬁes that event templates are found in the directory

/usr/share/evm/templates

2. Starts the EVM Logger and the EVM Channel Manager as synchronized clients when the daemon is

started.

3. Deﬁnes a service available through the EVM daemon.

4. Establishes an activity monitor that will alert the system administrator if 500 events occur in any 10

minute span. Once the system administrator has been alerted, the activity monitor will remain dor-

mant for four hours.

# Event template directory:

sourcedir "/usr/share/evm/templates"

# Start the EVM Logger as a synchronized client:

start_sync "/usr/sbin/evmlogger \

-o /var/run/evmlogger.info \

-l /var/evm/adm/logfiles/evmlogger.log"

# Start the EVM Channel Manager as a synchronized client:

start_sync "/usr/sbin/evmchmgr \

-l /var/evm/adm/logfiles/evmchmgr.log"

# Event retrieval service definition:

service { name event_get

command "/usr/sbin/evmget_srv"

}

# Set up an activity monitor.

activity_monitor {

name event_count # currently the only supported monitor

period 10 # count over a 10 minute period

threshold 500 # perform action after 500 events

holdoff 240 # wait 4 hours before resuming

}

FILES

/etc/evm.auth Location of the EVM authorization ﬁle.

/etc/evmdaemon.conf

Location of the EVM daemon conﬁguration ﬁle.

/etc/services Deﬁnition of the sockets and protocols used for Internet services.