Technical article 104899

Defining MMSGLOG, MCHANLOG or AUTHLOG filenames causes MMDF utilities to fail

OpenServer 5.0.0

Written · Last revised

Problem

Attempting to configure the filename for any of the generic MMDF log files causes MMDF related commands to fail, dumping core. Some examples of these log files are:

MCHANLOG "/usr/mmdf/log/chan.log", level=FST, size=40, ... MMSGLOG "/usr/mmdf/log/msg.log", level=FST, size=40, ... AUTHLOG "/usr/mmdf/log/auth.log", level=FST, size=40, ...

The type of logfile configured will determine which MMDF utilities
fail.  The programs affected include, but are not limited to:

submit(ADM) deliver(ADM) dbmbuild(ADM) various channel programs (smtp, smtpd, smtpsrvr, and so on)

To determine which command produced a core(FP) file, see another article in this database, TA103851, "How can I tell what program produced a core dump?".

Although the mail(C) command does not directly fail, it may not be
possible to send mail, as the mail(C) command invokes submit(ADM).
Other mail user agents (MUAs) may also fail for this reason.  If
this is the case, a core(FP) file may be produced by the submit(ADM)
process.

Solution

Remove the filename reference from the mmdftailor(F) file, for example:

AUTHLOG level=FST, size=40, ... MCHANLOG level=FST, size=40, ... MMSGLOG level=FST, size=40, ...

The log information will be logged in these default files:

/usr/mmdf/log/auth.log
/usr/mmdf/log/chan.log
/usr/mmdf/log/msg.log
Alternatively, a symbolic link may be used to simulate changing
the filename.  For example, to log message entries in /tmp/msg.log:
$ cd /usr/mmdf/log
$ mv msg.log msg.log.old
$ touch /tmp/msg.log
$ chown mmdf /tmp/msg.log
$ chgrp mmdf /tmp/msg.log
$ chmod 620 /tmp/msg.log
$ ln -s /tmp/msg.log msg.log

SCO is aware of this problem and is working to resolve it.

From the Xinuos technical article database, record 104899. Reproduced with permission. The original is at www.sco.com/ta/104899, which is reachable but blocked from search engines. Xinuos marks this article against a retired product line. That refers to the product’s lifecycle, not to whether the advice still works — plenty of it still applies to running systems.

Next step

Need this fixed rather than explained?

Tell us the release, what the system runs and what it is doing. We will reply by email with what we would do next.

  • You deal with the people who do the work
  • No obligation, and no upgrade required before we will help
  • We tell you plainly if something is not worth doing

Send an enquiry

We reply by email. If a server is down, say so in the first line. You can also write to help@scoexpert.com.