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.logAlternatively, 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.logSCO is aware of this problem and is working to resolve it.