<title>The DXSpider Installation and Administration Manual
<author>Ian Maude, G0VGS, (ianmaude@btinternet.com)
-<date>Version 1.27 December 2000
+<date>Version 1.29 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: 13 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.
the other cluster nodes that we are linked to. This is usually because of
rules and regulations pertaining to items for sale etc in a particular country.
-<sect1>Filtering DX callouts
+<sect1>Filtering DX callouts (Depricated)
+
+<P>
+<bf><it>From version 1.47, this method is replaced by the command set/baddx</it></bf>
<P>
In the same way as mail, there are some types of spot we do not wish to pass on
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
directory.
<verb>
-cvs -z3 -d:pserver:anonymous@cvs.DXSpider.sourceforge.net:/cvsroot/DXSpider co spider
+cvs -z3 -d:pserver:anonymous@cvs.DXSpider.sourceforge.net:/cvsroot/dxspider co spider
</verb>
This command is all on one line.
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>
</tt>
<P>
-Create an 'reject this spot' line for a filter.
+Create a 'reject this spot' line for a filter.
-An reject filter line means that if the spot matches this filter it is
+A reject filter line means that if the spot matches this filter it is
dumped (not passed on). See HELP FILTERS for more info. Please read this
to understand how filters work - it will save a lot of grief later on.
<P>
Set the node_call as an AR-Cluster type node
+<sect1>set/baddx (8)
+
+<P>
+<tt>
+<bf>set/baddx <call></bf> Stop words we do not wish to see in the callsign field
+of a dx spot being propagated
+</tt>
+
+<P>
+Setting a word as 'baddx' will prevent spots with that word in the callsign
+field of a DX spot from going any further. They will not be displayed and they
+will not be sent onto other nodes.
+
+The word must be wriiten in full, no wild cards are allowed eg:-
+
+<verb>
+ set/baddx FORSALE VIDEO FR0G
+</verb>
+
+To allow a word again, use the following command ...
+
+<verb>
+ unset/baddx VIDEO
+</verb>
+
<sect1>set/badnode (6)
<P>
Use with extreme care. This command may well be superceded by FILTERing.
+<sect1>set/badspotter (8)
+
+<P>
+<tt>
+<bf>set/badspotter <call></bf> Stop spots from this callsign being propagated
+</tt>
+
+<P>
+Setting a callsign as a 'badspotter' will prevent spots from this callsign
+going any further. They will not be displayed and they will not be
+sent onto other nodes.
+
+The call must be written in full, no wild cards are allowed eg:-
+
+<verb>
+ set/badspotter VE2STN
+</verb>
+
+will stop anything from VE2STN. If you want SSIDs as well then you must
+enter them specifically.
+
+<verb>
+ unset/badspotter VE2STN
+</verb>
+
+will allow spots from him again.
+
+Use with extreme care. This command may well be superceded by FILTERing.
+
<sect1>set/beep (0)
<P>
Allow WX information to be seen at your console. You can switch off
WX messages with the <em>unset/wx</em> command.
+<sect1>show/baddx (1)
+
+<P>
+<tt>
+<bf>show/baddx</bf>Show all the bad dx calls in the system
+</tt>
+
+<P>
+Display all the bad dx callsigns in the system, see SET/BADDX
+for more information.
+
<sect1>show/badnode (6)
<P>
Display all the bad node callsigns in the system, see SET/BADNODE
for more information.
+<sect1>show/badspotter (1)
+
+<P>
+<tt>
+<bf>show/badspotter</bf>Show all the bad spotters in the system
+</tt>
+
+<P>
+Display all the bad spotter's callsigns in the system, see SET/BADSPOTTER
+for more information.
+
<sect1>show/date (0)
<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>
projects / spider.git / blobdiff