[Dxspider-support] Unset/debug

Martin Davies G0HDB g0hdb at amdavies.demon.co.uk
Thu Sep 3 11:53:01 BST 2015


Hello again all, I now have a query about unsetting debugging.

I see from various previous threads that there appear to be two ways of unsetting debugging 
on a node, either by modifying the "@debug" line in DXVars.pm or by including an unset 
command in a startup script.  What are the relative advantages and disadvantages of these 
two approaches?

In a posting in Sept 2010 Dirk recommended leaving a minimum of 'chan' enabled for 
debugging; does this recommendation still stand?  What are the implications of disabling all 
debugging including 'chan'?

I've also found that if I start the node with all debugging enabled, ie. using the default setting 
in DXVars.pm, and then do 'unset/debug all' from the sysop console, nothing happens - full 
debugging seems to continue.  To stop it I've found I have to do 'unset/debug chan state ...'.  
Have I missed a cunning way of stopping all debugging  from the sysop console?

Thanks again,

---
Martin, G0HDB


---
This email has been checked for viruses by Avast antivirus software.
https://www.avast.com/antivirus




More information about the Dxspider-support mailing list