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)
Check Out this Related Man Page
evmreload(8) System Manager's Manual evmreload(8) NAME
evmreload - Reload Event Manager configuration files SYNOPSIS
/usr/sbin/evmreload [-d] [-a] [-c] [-l] [-n] OPTIONS
Reconfigures the EVM channel manager. Reconfigures the EVM daemon. Reconfigures the EVM logger. Syntax checks the event template files and reports errors, but does not make any changes effective. If a daemon reconfiguration is requested, the reconfiguration request will be sent even if there are errors in any template file. If errors exist, there is no guarantee that the new configuration will be accepted. OPERANDS
None DESCRIPTION
The evmreload command posts control events that instruct EVM resident components to reload their configuration files. It should be run to cause EVM to begin using the new configuration any time a configuration file has been changed. If no options are specified, the daemon, the channel manager, and the logger all reload their configurations. The daemon should be reconfigured any time its configuration file or event template database has changed. The logger should be reconfig- ured anytime its configuration has changed. The channel manager should be reconfigured anytime its configuration has changed. Resident EVM components also reload their configuration files on receipt of a SIGHUP signal. If an activity monitor is specified in the EVM daemon configuration file, all counts and timers associated with the monitor are reset. NOTES
The evmreload command uses the evmshow -verify command to check for errors in configuration files before sending a reload request to EVM. If errors are found, they are reported to stderr and no reconfiguration request is sent. This check does not find all possible errors, however, so you should take care to check for errors reported by the EVM components themselves. To do this, run the following command: evmget -A -f '[name *.evm] & [age < 5m]' -t '@timestamp @@' RESTRICTIONS
You must be user root to run this command. EXAMPLES
The following command will cause the EVM daemon to reconfigure itself: /usr/sbin/evmreload -d The following command will cause the EVM log- ger to reconfigure itself: /usr/sbin/evmreload -l The following command will cause the EVM channel manager to reconfigure itself: /usr/sbin/evmreload -c To syntax check the daemon configuration file without any reconfiguration actually occurring, enter the following command: /usr/sbin/evmreload -n To reconfigure both the EVM daemon and the EVM logger, enter the following command: /usr/sbin/evmreload -d -l To reconfigure the EVM daemon, the EVM logger, and the EVM channel manager, enter the following command: /usr/sbin/evmreload The follow- ing command will reconfigure the EVM daemon, the EVM logger, and the EVM channel manager even if there are errors in the template file. /usr/sbin/evmreload -a EXIT VALUES
The following exit values are returned: Successful completion An error occurred FILES
Executable file SEE ALSO
Commands: evmchmgr(8), evmd(8), evmlogger(8), evmpost(1) Files: evmchannel.conf(4), evmdaemon.conf(4), evmlogger.conf(4) Event Management: EVM(5) EVM Events: EvmEvent(5) delim off evmreload(8)