evmdaemon.conf man page on HP-UX

Printed from http://www.polarhome.com/service/man/?qf=evmdaemon.conf&af=0&tf=2&of=HP-UX

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

NAME
       evmdaemon.conf - EVM daemon configuration file

SYNOPSIS
DESCRIPTION
       The  Event Manager (EVM) daemon configuration file, is a text file that
       contains commands used to configure and start the Event	Manager.   Any
       portion	of a line from an unquoted number sign to the end of line is a
       comment.	 Blank lines are ignored.  The following commands  are	recog‐
       nized:

       Names  the  directory  that  is	used  to hold temporary authentication
       files.
		 The default is

       Names the root of the directory structure that should be searched for
		 event template files.	The default is

       Time to wait for a newly established client to respond to an
		 authentication request.  The default is 10 seconds.

       Time within which a synchronized client must achieve synchronization
		 completing a connection request and subscribing  for  events.
		 The default is 30 seconds.

       The complete command line for programs that should be started as
		 synchronized  clients	when  the daemon starts.  This command
		 should be enclosed in double quotation marks (").

       The maximum number of bytes the daemon will accept from any connection
		 in a single message.  If a client attempts to send a  message
		 that  is  longer  than the specified size, the daemon immedi‐
		 ately terminates the connection without reading the  message.
		 This  keyword	can  be used to limit the sizes of events that
		 can be posted, to prevent the daemon from consuming excessive
		 amounts of memory or CPU time by handling very large events.

		 Note:	Setting	 this  value too low may prevent normal system
		 events from being posted.

		 If this keyword is not specified, a default value of 2 Mbytes
		 is  used.  If the keyword is specified and the supplied value
		 is less than 200 Kbytes or greater than 10 Mbytes, it is  set
		 automatically to the closest of those values.

		 The  daemon  accepts messages up to 200 bytes longer than the
		 specified size to allow for communication protocol overhead.

       A colon-separated list of directories to be searched for	 filter	 files
       in
		 place	of  the	 standard locations.  If specified, the daemon
		 uses this value internally to evaluate	 filter	 strings  that
		 reference  pre-created	 filter	 files,	 and also passes it to
		 service programs such as the event retrieval service program,
		 by  exporting	the  environment  variable This makes the path
		 available to the event channels' get-function	scripts.   The
		 default  value	 for  this keyword is See the evmfilterfile(4)
		 manpage for more information.

		 If this keyword is not specified, a default value of 2 Mbytes
		 is  used.  If the keyword is specified and the supplied value
		 is less than 200 Kbytes or greater than 10 Mbytes, it is  set
		 automatically to the closest of those values.

		 The  daemon  accepts messages up to 200 bytes longer than the
		 specified size to allow for communication protocol overhead.

       A parameter group that controls a daemon event monitoring facility.
		 An definition consists of:

		 The type of detector controlled by the group parameters.

		 The size, in minutes, of a periodically sliding  time	window
		 over which
			   events will be counted.

		 The  number  of  events  that	will  activate	the monitor if
		 counted in

		 The time delay, in minutes, after activation of the  activity
		 monitor
			   occurs  before  monitoring is resumed.  The command
			   will reset the delay.

       Defines services that are available through the daemon.
		 A service definition consists of the name of the service  and
		 the  command  line  that will be invoked when this service is
		 requested.  User-defined  services  are  not  currently  sup‐
		 ported.

		 A service definition consists of:

		 The name given to the service.

		 The command to be invoked when this service is requested.
			   This command should be enclosed in double quotation
			   marks (").

       The keywords described may be entered  in  a  case-insensitive  manner.
       The  allowable strings and the minimum number of characters is shown in
       the following table.  A minimum of zero indicates that  all  characters
       are required.

       Keyword		  Minimum
       ───────────────────────────
       activity_monitor	     0
       authtimeout	     8
       command		     4
       filterdir	     7
       holdoff		     0
       max_msg_size	     7
       name		     0
       period		     0
       service		     7
       sourcedir	     7
       start_sync	     0
       synctimeout	     8
       threshold	     0

       The  activity  monitor  detectors recognized, and the action taken when
       the monitor is activated are the following:

	Detector			 Action
       ──────────────────────────────────────────────────────────────
       event_count   post an event to alert the system administrator

EXAMPLES
       This is an example of an EVM daemon configuration file  that  does  the
       following:

       1. Specifies that event templates are found in the directory

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

       3. Defines a service available through the EVM daemon.

       4. Establishes an activity monitor that will alert the system  adminis‐
	  trator  if  500 events occur in any 10 minute span.  Once the system
	  administrator has been alerted, the  activity	 monitor  will	remain
	  dormant for four hours.

FILES
       Location of the EVM authorization file.

       Location of the EVM daemon configuration file.

       Definition of the sockets and protocols used for Internet services.

SEE ALSO
   Commands
       evmd(1M), evmreload(1M).

   Files
       evmfilterfile(4), services(4).

   Event Management
       EVM(5).

							     evmdaemon.conf(4)
[top]

List of man pages available for HP-UX

Copyright (c) for man pages and the logo by the respective OS vendor.

For those who want to learn more, the polarhome community provides shell access and support.

[legal] [privacy] [GNU] [policy] [cookies] [netiquette] [sponsors] [FAQ]
Tweet
Polarhome, production since 1999.
Member of Polarhome portal.
Based on Fawad Halim's script.
....................................................................
Vote for polarhome
Free Shell Accounts :: the biggest list on the net