DXSpider Tracing Debug Entries: Difference between revisions
Jump to navigation
Jump to search
mNo edit summary |
|||
| Line 1: | Line 1: | ||
==General Information== | ==General Information== | ||
DXspider has the ability to log information at various levels, and those levels are set using the [[DXSpider Sysop Command Reference#DEBUG|debug]] tool in conjunction with the [https://wiki.dxcluster.org/wiki/DXSpider_Debug_Commands_and_Levels| debug levels]. Whilst this information is capture in data files in ../spider/local_data/debug/ it can also be seen in realtime from the command line prompt. | DXspider has the ability to log information at various levels, and those levels are set using the [[DXSpider Sysop Command Reference#DEBUG|debug]] tool in conjunction with the [https://wiki.dxcluster.org/wiki/DXSpider_Debug_Commands_and_Levels| debug levels]. Whilst this information is capture in data files in ../spider/local_data/debug/ it can also be seen in realtime from the command line prompt. Once the debug level is set the watchdbg tool can be used from ../spider/perl/ to watch the cluster's full data stream. This can be a very busy stream but it can be filtered for easier scrutiny. | ||
===Filtering traces=== | |||
Revision as of 08:24, 5 April 2025
General Information
DXspider has the ability to log information at various levels, and those levels are set using the debug tool in conjunction with the debug levels. Whilst this information is capture in data files in ../spider/local_data/debug/ it can also be seen in realtime from the command line prompt. Once the debug level is set the watchdbg tool can be used from ../spider/perl/ to watch the cluster's full data stream. This can be a very busy stream but it can be filtered for easier scrutiny.