LOGS(F) UNIX System V
Name
logs - MMDF log files
Syntax
System status, error, and statistics logging for MMDF
Description
MMDF maintains run-time log files at several levels of
activity. The primary distinction is among message-level,
channel-level, and link-level information. All logging
settings can be overridden by entries in the runtime tailor
file . In MMDF, that member is merged with /usr/mmdf/log to
determine the full pathname to the log. Logs are protected
so that any process may write into them, but only MMDF may
read them (i.e., 0622).
The logging files may be the source of some confusion, since
the llog package entails some complexity. Its three
critical factors are coordinated access, restricted file
length, and restricted verbosity.
The length of a logging file can be limited to 25-block
units. This is extremely important since files can grow
very long over a period of time, especially if there are
many long messages sent or very verbose logging.
Restricted verbosity is a way of easily tuning the amount of
text entered into the log. This is probably the one
parameter you need most to worry about. Set to full tilt
(level=FTR), MMDF get noticeably slower and I/O bound. It
also does a pretty good job of showing what it is doing and
hence helping you figure out the source of errors. When you
get to trust the code, setting the logging level down is
highly recommended. The lowest would be TMP or FAT, for
temporary or fatal errors. GEN will log errors and general
information. FST logs errors, general and statistics
information.
Specific Logs
Even with the listed divisions, the logs contain a variety
of information. Only the message-level log's format will be
explained in significant detail.
msg.log records enqueue and dequeue transitions, by
submit and deliver. Entries by a background
deliver process are noted with a ``BG-xxxx''
tag, where the x's contain the 4 least-
significant decimal digits of the daemon's
process id. This is to allow distinguishing
different daemons. When deliver is invoked,
by submit, for an immediate attempt, the tag
begins with ``DL'' rather than ``BG''.
Entries by submit begin with ``SB''.
Every major entry will indicate the name of the message
involved. Entries from submit will show ``lin'' if the
submission is from a user on the local machine. In this
case, the end of the entry will show the login name of the
sender. If the entry is labelled ``rin,'' then the mail is
being relayed. The channel name, source host, and sender
address are shown. Within parentheses, the number of
addressees and the byte-length of the message are listed.
Entries from deliver show final disposition of a
message/addressee. These are indicated by ``end.'' Then,
there is the destination channel and mailbox name. In
brackets, the queue latency for the address is shown in
hours, seconds, and minutes.
chan.log records activity by the channel programs, in
chndfldir[]. Entries have a tag indicating
the type of channel making the entry.
Different channels record different sorts of
information. For example, the local channel
shows when a rcvmail private reception
program is invoked.
ph.log is used by the telephone link-level (packet)
code.
ph.trn is the one file that is not size-limited. It
records a transcript of every character sent
and received on a telephone channel. It is
reset to zero length at the beginning of
every phone session. It is kept verbose, in
order to facilitate checking the status of
any telephone channel which is active.
Hence, just watching for the ph.trn file to
get larger can indicate that there is
progress. Each telephone channel may have
its own transcript file specified in the
channel definition in the runtime tailor
file.
See Also
mmdf(ADM)
Value Added
logs is an extension of AT&T System V provided by the Santa
Cruz Operation.
(printed 2/15/90) LOGS(F)