<title>The DXSpider Installation and Administration Manual
<author>Ian Maude, G0VGS, (ianmaude@btinternet.com)
-<date>Version 1.27 December 2000
+<date>Version 1.28 January 2001
<abstract>
A reference for SysOps of the DXSpider DXCluster program.
</abstract>
<sect>Installation (Original version by Iain Phillips, G0RDI)
<P>
-Last modified: 28 December 2000 by Ian Maude, G0VGS
+Last modified: 03 January 2001 by Ian Maude, G0VGS
<sect1>Introduction
there will be no way you can stop it.
-<sect1>Automating things
+<sect>Automating things
<P>
Ok, you should now have DXSpider running nicely and allowing connects by cluster
if you are not at the console! So, in this section we will automate both.
Firstly starting the cluster.
-<sect2>Autostarting the cluster
+<sect1>Autostarting the cluster
<P>
This is not only a way to start the cluster automatically, it also works as a
<P>
So far so good, now to automate script connections...
-<sect2>The crontab file
+<sect1>The crontab file
<P>
Login as <em>sysop</em> and create a file in /spider/local_cmd called crontab.
repository. You do this with the command below ...
<verb>
-cvs -d:pserver:anonymous@cvs.DXSpider.sourceforge.net:/cvsroot/DXSpider login
+cvs -d:pserver:anonymous@cvs.DXSpider.sourceforge.net:/cvsroot/dxspider login
</verb>
You will get a password prompt. Simply hit return here and your machine should
BE WARNED: this will write to any file you have write access to. No check is
made on the filename (if any) that you specify.
+<sect1>forward/latlong (8)
+
+<P>
+<tt>
+<bf>forward/latlong <node_call></bf> Send latitude and longitude
+information to another cluster
+</tt>
+
+<P>
+This command sends all the latitude and longitude information that your
+cluster is holding against callsigns. One advantage of recieving this
+information is that more locator information is held by you. This
+means that more locators are given on the DX line assuming you have
+<em>set/dxgrid</em> enabled. This could be a LOT of information though, so
+it is not recommended on slow links.
+
<sect1>forward/opername (1)
<P>
<P>
<tt>
-<bf>ping <node></bf> Send a ping command to another cluster node
+<bf>ping <node></bf> Check the link quality between nodes
</tt>
<P>
-This command is used to estimate the quality of the link to another cluster.
-The time returned is the length of time taken for a PC51 to go to another
-cluster and be returned.
-
+his command allows you to send a frame to another cluster node on
+the network and get a return frame. The time it takes to do this
+is a good indication of the quality of the link. The actual time
+it takes is output to the console in seconds.
Any visible cluster node can be PINGed.
+
<sect1>rcmd (1)
<P>
and returns any information available for that callsign. This service
is provided for users of this software by http://www.qrz.com
+<sect1>show/route (0)
+
+<P>
+<tt>
+<bf>show/route <callsign></bf> Show the route to <callsign>
+</tt>
+
+<P>
+This command allows you to see to which node the callsigns specified are
+connected. It is a sort of inverse sh/config.
+
+<verb>
+ sh/route n2tly
+</verb>
+
<sect1>show/satellite (0)
<P>