Debugging Channel Master and Slave Programs (master_debug, nomaster_debug, slave_debug, noslave_debug)

Some channel programs include optional code to assist in debugging by producing additional diagnostic output. Two channel keywords are provided to enable generation of this debugging output on a per-channel basis. The keywords are master_debug, which enables debugging output in master programs, and slave_debug, which enables debugging output in slave programs. Both types of debugging output are disabled by default, corresponding to nomaster_debug and noslave_debug.

When activated, debugging output ends up in the log file associated with the channel program. The location of the log file may vary from program to program. Log files are usually kept in the IMTA log directory. Master programs usually have log file names of the form x_master.log, where x is the name of the channel; slave programs usually have log file names of the form x_slave.log. Also, some channel programs, notably TCP/IP and fax channel programs, may produce additional log files with names:

err_x_master.log
err_x_slave.log
di_x_master.log
di_x_xlave.log
ph_x_master.log
ph_x_slave.log

In the case of the local channel, master_debug enables debugging output when sending from the local channel, and slave_debug enables debugging output as messages are delivered to the local channel, with output usually appearing in the
/var/opt/SUNWmail/imta/log/l_master.log.




Copyright © 1999 Sun Microsystems, Inc. All Rights Reserved.