Jump to content United States-English
HP.com Home Products and Services Support and Drivers Solutions How to Buy
» Contact HP
More options
HP.com home
HP-UX Event ManagerAdministrator's Guide: HP-UX 11i v3 Edition 1 > Chapter 3 Configuring Event Manager

Configuring Event Manager Daemon

» 

Technical documentation

Complete book in PDF
» Feedback
Content starts here

 » Table of Contents

 » Index

The daemon reads the /etc/evmdaemon.conf configuration file at system startup and whenever you issue a reload request by using the evmreload command. For a complete description of the contents and syntax for the configuration file, see evmdaemon.conf(4). Example 3-1 “Sample Daemon Configuration File Entries” shows some sample entries in the daemon configuration file.

Example 3-1 Sample Daemon Configuration File Entries

		 	 # Event template directory:
	 	 /* This statement identifies the top of the directory 	 	 	 	 	 	 	 	 	 	 	 		 	 	hierarchy for all 		event template files.*/
sourcedir "/usr/share/evm/templates" /* These commands start the evmlogger and the evmchmgr components as synchronized clients, ensuring that both clients complete their subscription requests before the daemon accepts any events from posting clients. The command line options for these commands define the clients' log files and, in the case of the logger, an output file that is used to make operational details available to the evmlog event channel functions. */
	 	 # Start the Event Manager Logger 	 	 start_sync "/usr/sbin/evmlogger -o /var/run/evmlogger.info \
-l /var/evm/adm/logfiles/evmlogger.log"

# Start the Event Manager Channel Manager start_sync "/usr/sbin/evmchmgr -l \/var/evm/adm/logfiles/evmchmgr.log" /* These statements define the event_get event retrieval service, which the evmget command uses to retrieve events. */
# Event retrieval service definition: service {
name event_get
command "/usr/sbin/evmget_srv"
}
/* These statements define an activity monitor. In this example, if 500 or more events are received during any ten minute period, the daemon posts a high-priority event to alert the system administrator. Activity monitoring (counting of events) is then suspended for the hold-off period of four hours (240 minutes). */
# Set up an activity monitor: activity_monitor {
name event_count
period 10
threshold 500
holdoff 240
}

If you make any changes to the configuration file, you must enter the evmreload command to inform the daemon of these changes. For more information, see evmreload(1M).

Printable version
Privacy statement Using this site means you accept its terms Feedback to webmaster
© 2007 Hewlett-Packard Development Company, L.P.