Logtool Specifications

Hewlett-Packard STM: Logtool ERS * Revision 1.17
- Page 10 - Printed: 02/04/99 3:38 PM
In addition to the various filters implemented by Logtool, the STM Logger process
also has the capability to filter log data based on certain criteria. This enables the user
to "turn off" logging of entries that are of no interest. Entries that are filtered out via
the logger process are discarded and not placed in the raw log file, thus saving disk
space. This filter can be modified by editing the logger configuration file.
The Logger process also enables the user to invoke specific programs when particular
entries are logged. The program that is invoked will be passed the raw log entry on
which it will presumably do some special case processing. An example of a practical
application of this feature could be to monitor log entries from a particular device
and generate messages to the system console if critical errors are detected. It should
be noted that the Logger process will log the entry as usual after passing it to the
specified program. The user can specify which programs to invoke for which log
entries in the logger configuration file.
Refer to Appendix B for details on the logger configuration file.
2.5. Log File Naming Conventions
Raw log files have names of the form logn.raw, where n is a number that starts at one
and is incremented each time a new log file is created via the Switch Log command.
The exception to this is the log file to which the logger is currently logging which is
called logn.raw.cur. Formatted log files have names of the form logn.fmtn where the
first number matches that of the raw log file from which it was generated and the
second number starts at one and is incremented by one for each new formatted file
that is generated from the same raw log file. In the case where multiple files were
selected to be formatted together, the filename will have a plus sign, “+”, in it. For
example, log1.raw and log2.raw would be formatted in to the file log1+.fmt1.
On HP-UX systems, the default directory of the system log files is /var/stm/logs/os.
Formatted log files will be stored in the same directory by default. The memory log
file, memlog, is also located in the /var/stm/logs/os directory.
2.6. Log Entry Types
The actual contents of the I/O error logs is system dependent. The logs currently
contain the following types of entries:
• I/O Errors (logged by drivers)
• LPMC
• System Overtemp
• LVM Errors (logged by LVM system)
• Logger Events