United States-English |
|
|
HP-UX Reference > Eevmfilterfile(4)HP-UX 11i Version 3: February 2007 |
|
NAMEevmfilterfile — Event Manager filter file SYNOPSISfilter { name filter_name valuex filter_value include filter_element exclude filter_element title filter_title } DESCRIPTIONA filter file contains one or more filter descriptions, which can be referenced through certain EVM commands by using indirect filter syntax. An indirect filter specifier has the following form: @filename[:filter_name] In the previous indirect filter specifier, filename is the name of a filter file, and filter_name is the name of a filter contained in the file. If no filter_name is specified, the first filter in the file is used. By convention, filter file names should have the suffix .evf. If a command cannot find the file with the name as specified, it appends .evf and tries again. If a relative pathname is given for a file, commands search for the file in each location specified by the EVM_FILTERDIR environment variable if it is present. Otherwise the search is performed in the following standard locations in turn, stopping as soon as the file is found:
Several supplied filter files, containing shortcut filters for many system events, can be found in the directory /usr/share/evm/filters. System administrators should place site-specific filter files in /var/evm/adm/filters. The filter file is made up of a series of keyword/value and keyword/group pairs. Values containing spaces must be enclosed in double quotes. Strings may be continued across a newline by finishing the line with a backslash character. Any portion of a line from an unquoted number sign (#) to the end of line is a comment. Blank lines are ignored. The following keywords are recognized:
The include and exclude keywords can appear multiple times in a filter group, allowing you to build and maintain a filter in simple single-line increments. Each filter_element must be a valid filter string, conforming to the syntax described in the EvmFilter(5) manpage. A complete filter string is assembled by surrounding the initial filter with parentheses and appending the filter_elements to it, separating each with a logical OR (for include) or AND NOT (for exclude) operator. For example: value "[priority >= 200]" include "[name *.mylog]" exclude "[name *.oldlog]" The previous filter lines are equivalent to this more complex single filter line: value "([priority >= 200]) OR [name *.mylog] AND NOT [name *.oldlog]" The first line selects all events with a priority of 200 or greater, the next modifies this by selecting all events from mylog regardless of their priorities, and the last line excludes all oldlog events regardless of their priorities. If you prefer, you can omit the value command, and build the complete filter string from include and exclude lines. NotesIf you are concerned with allowing your file to be used on other systems that support EVM in the future, you should use the built-in macro @SYS_VP@ in place of the first two components (sys.unix) of the name of any system event. This will make it unnecessary to change the file if the other system uses a different event name prefix. EXAMPLES
FILES
SEE ALSORoutinesEvmFilterCreate(3), EvmFilterDestroy(3), EvmFilterIsFile(3), EvmFilterReadFile(3), EvmFilterSet(3), EvmFilterTest(3). |
Printable version | ||
|