Debugging Levels

debug string ...

Set the debugging level. This command is only effective if the code has been compiled to include debugging. The default is to have no debugging. The arguments are strings which name the types of debugging to be turned on. The following types of debugging are defined:

`abnormal'

Output debugging messages for abnormal situations, such as recoverable errors.

`chat'

Output debugging messages for chat scripts.

`handshake'

Output debugging messages for the initial handshake.

`uucp-proto'

Output debugging messages for the UUCP session protocol.

`proto'

Output debugging messages for the individual link protocols.

`port'

Output debugging messages for actions on the communication port.

`config'

Output debugging messages while reading the configuration files.

`spooldir'

Output debugging messages for actions in the spool directory.

`execute'

Output debugging messages whenever another program is executed.

`incoming'

List all incoming data in the debugging file.

`outgoing'

List all outgoing data in the debugging file.

`all'

All of the above.

The debugging level may also be specified as a number. A 1 will set `chat' debugging, a 2 will set both `chat' and `handshake' debugging, and so on down the possibilities. Currently an 11 will turn on all possible debugging, since there are 11 types of debugging messages listed above; more debugging types may be added in the future. The debug command may be used several times in the configuration file; every debugging type named will be turned on. When running any of the programs, the `-x' switch (actually, for uulog it's the `-X' switch) may be used to turn on debugging. The argument to the `-x' switch is one of the strings listed above, or a number as described above, or a comma separated list of strings (e.g., `-x chat,handshake'). The `-x' switch may also appear several times on the command line, in which case all named debugging types will be turned on. The `-x' debugging is in addition to any debugging specified by the debug command; there is no way to cancel debugging information. The debugging level may also be set specifically for calls to or from a specific system with the debug command in the system file (see section Miscellaneous sys File Commands). The debugging messages are somewhat idiosyncratic; it may be necessary to refer to the source code for additional information in some cases.

Go to the first, previous, next, last section, table of contents.