DXSpider Debug Commands and Levels: Difference between revisions
Jump to navigation
Jump to search
Start point |
No edit summary |
||
| Line 1: | Line 1: | ||
===General Information=== | ===General Information=== | ||
The debug commands are set and unset through the console, this gives the sysop control on the messages that are logged in the debug files. | The debug commands, or levels, are set and unset through the console, this gives the sysop control on the messages that are logged in the debug files. | ||
====Levels==== | |||
* badip - for logging bad ip address | |||
* chan | |||
* connect - for logging connect messages | |||
* cron | |||
* msg | |||
* nologchan - for logging (or not) the channel traffic | |||
* pc11 - for logging PC11 messages | |||
* progress | |||
* spotdup | |||
* state | |||
====Examples==== | |||
At the console: | |||
To enable the logging of PC11 messages | |||
set/debug pc11 | |||
To unset the default of not logging channels | |||
unset/debug nologchan | |||
Revision as of 21:02, 4 April 2025
General Information
The debug commands, or levels, are set and unset through the console, this gives the sysop control on the messages that are logged in the debug files.
Levels
- badip - for logging bad ip address
- chan
- connect - for logging connect messages
- cron
- msg
- nologchan - for logging (or not) the channel traffic
- pc11 - for logging PC11 messages
- progress
- spotdup
- state
Examples
At the console:
To enable the logging of PC11 messages
set/debug pc11
To unset the default of not logging channels
unset/debug nologchan