Fix typo regarding CVS in adminmanual

[spider.git] / sgml / adminmanual.sgml

diff --git a/sgml/adminmanual.sgml b/sgml/adminmanual.sgml
index dc4a4ab649456765ae2fdd5cf63564991d209d1e..40e6000a5090f25fad4d5b6d86ad812392c5da92 100644 (file)
--- a/sgml/adminmanual.sgml
+++ b/sgml/adminmanual.sgml
@@ -6,7 +6,7 @@
 
 <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>
@@ -19,7 +19,7 @@ A reference for SysOps of the DXSpider DXCluster program.
 <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
 
@@ -579,7 +579,7 @@ have no control over it.  The chances are that this link will create echo and
 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
@@ -588,7 +588,7 @@ connection scripts fail they have to be started again manually too, not much use
 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
@@ -616,7 +616,7 @@ you should find everything running nicely.
 <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.  
@@ -1707,7 +1707,7 @@ First login as the user <em>sysop</em>.  Next you need to connect to the CVS
 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
@@ -2470,6 +2470,22 @@ suffix.
 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 &lt;node_call&gt;</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>
@@ -2755,16 +2771,17 @@ without any processing, added of "from &lt;blah&gt; to &lt;blah&gt;" or whatever
 
 <P>
 <tt>
-<bf>ping &lt;node&gt;</bf> Send a ping command to another cluster node
+<bf>ping &lt;node&gt;</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>
@@ -3991,6 +4008,21 @@ This command queries the QRZ callbook server on the internet
 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 &lt;callsign&gt;</bf> Show the route to &lt;callsign&gt;
+</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>