logs(F) 19 June 1992 logs(F) Name logs - MMDF log files: system status, error, and statistics logging for MMDF Description MMDF maintains runtime log files at several levels of activity. The pri- mary 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 (that is, 0622). The logging files may be the source of some confusion, since the log package entails some complexity. Its three critical factors are coordi- nated 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 to be most concerned about. Set to full tilt (level=FTR), MMDF becomes noticeably slower and I/O bound. It also shows what it is doing, and helps you to discern the source of errors. When you are used to 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 in- formation. FST logs errors, general and statistics information. Specific logs Even with the listed divisions, the logs contain a variety of informa- tion. Only the message-level log's format will be explained in signifi- cant 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. See also mmdf(ADM) Value added logs is an extension of AT&T System V provided by The Santa Cruz Opera- tion, Inc. Credit MMDF was developed at the University of Delaware and is used with permis- sion.