Useful Daily Commands For Sysops - Revision history

G0TRT: added update_sysop.pl for changing the cluster callsign

2025-11-20T09:29:39Z

added update_sysop.pl for changing the cluster callsign

← Older revision		Revision as of 09:29, 20 November 2025
Line 6:		Line 6:
	* ./watchdbg GB7AXX-3 - watch everything that's coming out of this node.		* ./watchdbg GB7AXX-3 - watch everything that's coming out of this node.
	* ./watchdbg connect' - watching for connections, there are a lot of unsuccessful attempts aren't there.		* ./watchdbg connect' - watching for connections, there are a lot of unsuccessful attempts aren't there.
	* ./grepdbg 'progress' "(CMD: \'dx )" - see all the spots originating from your node (the space after the dx is very important).		* ./grepdbg 'progress' "(CMD: \'dx )" - see all the spots originating from your node (the space after the dx is very important). grepdbg can also be used instead of watchdbg, or vice versa. For more information on watchdbg and grepdbg see the "[[DXSpider_Tracing_Debug_Entries\|Tracing Debug Entries]]" page.
	* sudo service dxspider restart		* sudo service dxspider restart
	~~grepdbg can also be used instead of watchdbg, or vice versa~~. ~~For more information on watchdbg and grepdbg see~~ the ~~"[[DXSpider_Tracing_Debug_Entries\|Tracing Debug Entries]]" page~~.		* update_sysop.pl - if a cluster callsign needs to change then edit the variables such as sysop callsign within DXVars.pm then run /spider/perl/update_sysop.pl

	===Console commands===		===Console commands===

WI3W: add clarification

2025-04-13T21:30:01Z

add clarification

← Older revision		Revision as of 21:30, 13 April 2025
Line 8:		Line 8:
	* ./grepdbg 'progress' "(CMD: \'dx )" - see all the spots originating from your node (the space after the dx is very important).		* ./grepdbg 'progress' "(CMD: \'dx )" - see all the spots originating from your node (the space after the dx is very important).
	* sudo service dxspider restart		* sudo service dxspider restart
	grepdbg can also be used instead of watchdbg. For more information on watchdbg and grepdbg see the "[[DXSpider_Tracing_Debug_Entries\|Tracing Debug Entries]]" page.		grepdbg can also be used instead of watchdbg, or vice versa. For more information on watchdbg and grepdbg see the "[[DXSpider_Tracing_Debug_Entries\|Tracing Debug Entries]]" page.

	===Console commands===		===Console commands===

WI3W: Fix syntax of spots from node command

2025-04-13T21:16:41Z

Fix syntax of spots from node command

← Older revision		Revision as of 21:16, 13 April 2025
Line 6:		Line 6:
	* ./watchdbg GB7AXX-3 - watch everything that's coming out of this node.		* ./watchdbg GB7AXX-3 - watch everything that's coming out of this node.
	* ./watchdbg connect' - watching for connections, there are a lot of unsuccessful attempts aren't there.		* ./watchdbg connect' - watching for connections, there are a lot of unsuccessful attempts aren't there.
	* ./grepdbg 'progress' 'CMD:' 'dx ' - see all the spots originating from your node (the space after the dx is very important).		* ./grepdbg 'progress' "(CMD: \'dx )" - see all the spots originating from your node (the space after the dx is very important).
	* sudo service dxspider restart		* sudo service dxspider restart
	grepdbg can also be used instead of watchdbg. For more information on watchdbg and grepdbg see the "[[DXSpider_Tracing_Debug_Entries\|Tracing Debug Entries]]" page.		grepdbg can also be used instead of watchdbg. For more information on watchdbg and grepdbg see the "[[DXSpider_Tracing_Debug_Entries\|Tracing Debug Entries]]" page.

WI3W: add command for node originating spots

2025-04-13T20:45:38Z

add command for node originating spots

← Older revision		Revision as of 20:45, 13 April 2025
Line 6:		Line 6:
	* ./watchdbg GB7AXX-3 - watch everything that's coming out of this node.		* ./watchdbg GB7AXX-3 - watch everything that's coming out of this node.
	* ./watchdbg connect' - watching for connections, there are a lot of unsuccessful attempts aren't there.		* ./watchdbg connect' - watching for connections, there are a lot of unsuccessful attempts aren't there.
			* ./grepdbg 'progress' 'CMD:' 'dx ' - see all the spots originating from your node (the space after the dx is very important).
	* sudo service dxspider restart		* sudo service dxspider restart
	grepdbg can also be used instead of watchdbg. For more information on watchdbg and grepdbg see the "[[DXSpider_Tracing_Debug_Entries\|Tracing Debug Entries]]" page.		grepdbg can also be used instead of watchdbg. For more information on watchdbg and grepdbg see the "[[DXSpider_Tracing_Debug_Entries\|Tracing Debug Entries]]" page.

G0TRT: Added set/var @main::localhost_names

2025-04-09T20:55:27Z

Added set/var @main::localhost_names

← Older revision		Revision as of 20:55, 9 April 2025
Line 20:		Line 20:
	* stat/user <callsign> - everything you want to know about <callsign>		* stat/user <callsign> - everything you want to know about <callsign>
	* sh/hf - a table of spot quantities, per day, per band, for the last month.		* sh/hf - a table of spot quantities, per day, per band, for the last month.
			* set/var @main::localhost_names ('127.0.0.1', '::1', '192.168.1.127','192.168.1.154','192.168.1.110') - sets all of the IP addresses in your LAN
	* sh/var @main::localhost_names - all of your IP addresses.		* sh/var @main::localhost_names - all of your IP addresses.
	* mnodes - orderly listing of connected nodes (not included in DXSpider unless Kin's script is installed).		* mnodes - orderly listing of connected nodes (not included in DXSpider unless Kin's script is installed).

G0TRT: Link updated

2025-04-08T05:26:17Z

Link updated

← Older revision		Revision as of 05:26, 8 April 2025
Line 7:		Line 7:
	* ./watchdbg connect' - watching for connections, there are a lot of unsuccessful attempts aren't there.		* ./watchdbg connect' - watching for connections, there are a lot of unsuccessful attempts aren't there.
	* sudo service dxspider restart		* sudo service dxspider restart
	grepdbg can also be used instead of watchdbg. For more information on watchdbg and grepdbg see the "[[~~Tracing Debug Entries~~\|Tracing Debug Entries]]" page.		grepdbg can also be used instead of watchdbg. For more information on watchdbg and grepdbg see the "[[DXSpider_Tracing_Debug_Entries\|Tracing Debug Entries]]" page.

	===Console commands===		===Console commands===

WI3W: add grepdbg note

2025-04-07T22:59:20Z

add grepdbg note

← Older revision		Revision as of 22:59, 7 April 2025
Line 7:		Line 7:
	* ./watchdbg connect' - watching for connections, there are a lot of unsuccessful attempts aren't there.		* ./watchdbg connect' - watching for connections, there are a lot of unsuccessful attempts aren't there.
	* sudo service dxspider restart		* sudo service dxspider restart
	For more information on watchdbg and grepdbg see the "[[Tracing Debug Entries\|Tracing Debug Entries]]" page.		grepdbg can also be used instead of watchdbg. For more information on watchdbg and grepdbg see the "[[Tracing Debug Entries\|Tracing Debug Entries]]" page.

	===Console commands===		===Console commands===

WI3W: Make some corrections...

2025-04-07T22:58:24Z

Make some corrections...

← Older revision		Revision as of 22:58, 7 April 2025
Line 3:		Line 3:
	===Linux prompt===		===Linux prompt===

	* ./watchdbg ~~\| grep~~ 'PC92\^VE7CCD-1' - looking for troubling data out of this node. Note: the ^ needs to be escaped with \		* ./watchdbg 'PC92\^VE7CCD-1' - looking for troubling data out of this node. Note: the ^ needs to be escaped with \
	* ./watchdbg GB7AXX-3 - watch everything that's coming out of this node.		* ./watchdbg GB7AXX-3 - watch everything that's coming out of this node.
	* ./watchdbg ~~\| grep '(connect)~~ connect' - watching for connections, there are a lot of unsuccessful attempts aren't there.		* ./watchdbg connect' - watching for connections, there are a lot of unsuccessful attempts aren't there.
	* sudo service dxspider restart		* sudo service dxspider restart
			For more information on watchdbg and grepdbg see the "[[Tracing Debug Entries\|Tracing Debug Entries]]" page.

	===Console commands===		===Console commands===

WI3W: Add some details

2025-04-07T22:31:00Z

Add some details

← Older revision		Revision as of 22:31, 7 April 2025
Line 3:		Line 3:
	===Linux prompt===		===Linux prompt===

	* ./watchdbg \| grep PC92^VE7CCD-1 - looking for troubling data out of this node.		* ./watchdbg \| grep 'PC92\^VE7CCD-1' - looking for troubling data out of this node. Note: the ^ needs to be escaped with \
	* ./watchdbg GB7AXX-3 - watch everything that's coming out of this node.		* ./watchdbg GB7AXX-3 - watch everything that's coming out of this node.
	* ./watchdbg \| grep '(connect) connect' - watching for connections, there are a lot of unsuccessful attempts aren't there.		* ./watchdbg \| grep '(connect) connect' - watching for connections, there are a lot of unsuccessful attempts aren't there.
Line 20:		Line 20:
	* sh/hf - a table of spot quantities, per day, per band, for the last month.		* sh/hf - a table of spot quantities, per day, per band, for the last month.
	* sh/var @main::localhost_names - all of your IP addresses.		* sh/var @main::localhost_names - all of your IP addresses.
	* mnodes - orderly listing of connected nodes.		* mnodes - orderly listing of connected nodes (not included in DXSpider unless Kin's script is installed).
	* musers - about all those connected users.		* musers - about all those connected users (not included in DXSpider unless Kin's script is installed).
	* who - a list of the connected nodes and users, with some useful info about them.		* who - a list of the connected nodes and users, with some useful info about them.
	* rcmd g6nhu-2 sh/ver - did G6NHU update his node?		* rcmd g6nhu-2 sh/ver - did G6NHU update his node?
	* sh/debug - did I leave debug running? Is that why my disk is full!		* sh/debug - did I leave debug running? Is that why my disk is full!

G0TRT at 21:41, 7 April 2025

2025-04-07T21:41:11Z

← Older revision		Revision as of 21:41, 7 April 2025
Line 6:		Line 6:
	* ./watchdbg GB7AXX-3 - watch everything that's coming out of this node.		* ./watchdbg GB7AXX-3 - watch everything that's coming out of this node.
	* ./watchdbg \| grep '(connect) connect' - watching for connections, there are a lot of unsuccessful attempts aren't there.		* ./watchdbg \| grep '(connect) connect' - watching for connections, there are a lot of unsuccessful attempts aren't there.
			* sudo service dxspider restart

	===Console commands===		===Console commands===