ACC Utilities Reference Guide

ZMLOG - Diagnostic Message Logging
ZCOM Diagnostic Message Logging Mechanism
Chapter 6 153
and utility programs, or by application programs. The ZCOM software
library supplies the routines that may be called by application programs
to log messages.
The messages are written by the drivers or programs in a binary form
which is passed to ZMLOG via the device file /dev/zmlog. The messages
can be optionally logged in the binary form or converted to text using the
message file, and then either logged to a file or displayed to a device.
The messages are time stamped by the LDM at the time they are
generated. The time stamped messages are written to the appropriate
text or binary log file, and optionally written to one or more device files.
The device files may be used to write to a hard copy log or to display the
messages for the system monitoring.
The text and priority of the error messages are customizable. The user
can set up customer specific message information into the message file
(or one of its include files). For detailed information, see the Setting Up
Customized or Application Specific Messages.
Daily Message Files
The messages are saved into daily files. Each file contains messages
generated on a particular day. These files are kept in the directory
/var/opt/acc/log. There are 28 possible log files in this directory, one for
each weekday in both binary and text formats plus an .old version of
each.
Usually, the text log files are: mon.tlog, tue.tlog, wed.tlog, thu.tlog,
fri.tlog, sat.tlog, sun.tlog, and the binary log files are: mon.blog, tue.blog,
wed.blog, thu.blog, fri.blog, sat.blog, sun.blog. All files are recycled after
1 week.
As messages are logged, when a file grows to a pre-defined size limit, the
file is renamed to have an “.old” suffix (e.g. mon.blog.old, mon.tlog.old),
and the subsequent messages are logged into a new file with the original
name (i.e. mon.blog, or mon.tlog.old). If that new file exceeds the
limit again, it will be renamed to replace the .old file. This can
cause a loss of messages as the disk space is recycled. For a single
day, the total disk space used by all the binary or text log files could be up
twice the per-file limit. The file size limit of a single binary and text log
file can be set by the zmlog -B and -T options, respectively (with a default
of 1Gb). This provides a mechanism to control the maximum disk space
used by the message files.