sys_attrs_kevm(5) [hpux man page]

sys_attrs_kevm(5)						File Formats Manual						 sys_attrs_kevm(5)

NAME

       sys_attrs_kevm - KEVM (Kernel Event Manager) subsystem attributes

DESCRIPTION

       This  manpage  lists  and describes attributes for the Kernel Event Manager subsystem.  See evm(5) for more information about Event Manager
       software.

       An asterisk preceding the name of an attribute in the following list means that the attribute can be configured at  run	time.	Values	of
       other attributes cannot be changed without rebooting the system.

       A value that can be used to reinitialize all of the
		 attributes.  Changing to any non-zero value causes all the attributes to be reset to zero, and then itself is automatically reset
		 to zero.

		 Default value: 0

		 Minimum value: 0

		 Maximum value: 2,147,483,647

		 If you use to change the value of the updated attribute values are not visible until you exit and restart

       The number of EVM events currently queued in kernel space for
		 collection by the EVM daemon.	This attribute is query only.

       The size (in bytes) of the fixed buffer used to queue any EVM events
		 that are posted while the kernel is executing at interrupt level.  Events are moved out of the  buffer  as  soon  as  the  system
		 returns to normal operating mode.  The default buffer size should be adequate for most systems.

		 Default value: 65, 536 (bytes)

		 Minimum value: 1

		 Maximum value: 1,844,674,407,370

       A value that indicates whether a process (such as
		 currently  has  or does not have the interface in an open state.  The value 1 means that a process has the interface open (always
		 the case if is running) and the value 0 means that no process has the interface open.	This attribute is query only.

       The major device number being used by the
		 interface.  This attribute is query only.

       The number of EVM events that have been posted in the kernel since the
		 the system was started or the counter was reset.  You can reset directly, or by changing to a non-zero value.

		 Minimum value: 0

		 Maximum value: 2,147,483,647

       The number of EVM events that have been read from kernel space by the
		 EVM daemon since the system was started or the counter was reset.  You can reset manually or by changing to a non-zero value.

		 Minimum value: 0

		 Maximum value: 2,147,483,647

       The highest number of EVM events that have been queued in kernel space
		 waiting to be collected by the EVM daemon since the system was started or the counter was reset.  You can reset  manually  or	by
		 changing to a non-zero value.

		 Minimum value: 0

		 Maximum value: 2,147,483,647

SEE ALSO

       evm(5).

   System Administration
																 sys_attrs_kevm(5)

syslog_evm.conf(4)					     Kernel Interfaces Manual						syslog_evm.conf(4)

NAME

       syslog_evm.conf - EVM syslog subscription configuration file

SYNOPSIS

       facility.priority

DESCRIPTION

       The  syslog_evm.conf file is a text file that specifies what syslog messages will be forwarded from the syslog daemon to the Event Manager,
       EVM,in the form of EVM events.  Those syslog messages are posted to the EVM daemon evmd by syslogd if the syslogd  forwarding  function	is
       turned on with the -e flag.  Events are posted with the EVM name of sys.unix.syslog.facility-name.

       This configuration file is read every time syslogd starts, or is restarted by a SIGHUP signal.  If the file does not exist, or if it exists
       but contains no subscription lines, no syslog messages will be posted to EVM.

       Each line in the file controls the forwarding of one syslog event.  Lines beginning with the # character are considered	comments  and  are
       ignored.  Only one subscription per line is permitted.  Mixing a subscription and a comment on the same line is not allowed.

       Each  line has the format facility.priority[+].	Specifies the part of the system that generated the message.  Legal values are the follow-
       ing: All messages.  Messages generated by the kernel.  Messages generated by user processes.  Messages generated by the mail system.   Mes-
       sages  generated  by  system  daemons.	Messages generated by the authorization system.  Messages generated internal to the syslog system.
       Messages generated by the line printer spooling system.	Messages generated by the system news command.	Messages generated by the UNIX	to
       UNIX  copy  system.   Messages  generated by the system clock daemon.  Messages generated by remote file systems.  Available for local use.
       Indicates the priority of the message.  If the priority is followed by a + character, events which are of the specified priority or  higher
       are forwarded; otherwise only events which exactly match the priority are forwarded.

	      The priority level must be one of the following: Forward messages of any priority.  Forward messages of emergency priority.  Forward
	      messages of alert priority.  Forward messages of critical priority.  Forward messages of error priority.	Forward messages of  warn-
	      ing priority.  Forward messages of notice priority.  Forward messages of information priority.  Forward messages of debug priority.

EXAMPLES

       This  example causes syslogd to forward events to EVM as follows: All messages of emergency priority are forwarded.  All messages generated
       in the kernel which have a priority of info or greater are forwarded.  All messages generated by users, by the mail  subsystem  or  by  the
       system daemons which have a priority of info or greater are forwarded.

       *.emerg kern.info+ user.notice+ mail.notice+ daemon.notice+

FILES

       Location  of the system logger configuration file.  Location of the EVM syslog subscription configuration file.	Location of the EVM logger
       configuration file.

SEE ALSO

       Commands: evmd(8), evmlogger(8), syslog(1), syslogd(8)

       Routines: syslog(3)

       Event Management: EVM(5)
       delim off

																syslog_evm.conf(4)