+18Jul02=======================================================================
+1. Make additions and changes to manuals. (g0vgs)
+16Jul02=======================================================================
+1. Add changes to the spider-web java web client. Thanks to Rene, OZ1LQH. It
+should now be easier to install and run for all systems. (g0vgs)
11Jul02=======================================================================
1. NP work has now started in ernest ([ed]who he?). You will need to download
Digest::SHA1 and any dependant packages to run this release. HOWEVER tempted
<HTML>
<HEAD>
<META NAME="GENERATOR" CONTENT="SGML-Tools 1.0.9">
- <TITLE>The DXSpider Administration Manual v1.49: Routing and Filtering</TITLE>
+ <TITLE>The DXSpider Administration Manual v1.50: Routing and Filtering</TITLE>
<LINK HREF="adminmanual-2.html" REL=next>
<LINK HREF="adminmanual.html#toc1" REL=contents>
<P>
<P>The <EM>set/hops</EM> command overrides any hops that you have set otherwise.
<P>
-<P>You can set what hops have been set using the <EM>show/hops</EM> command.
+<P>You can show what hops have been set using the <EM>show/hops</EM> command.
<P>
<H2><A NAME="ss1.12">1.12 Isolating networks</A>
</H2>
<HTML>
<HEAD>
<META NAME="GENERATOR" CONTENT="SGML-Tools 1.0.9">
- <TITLE>The DXSpider Administration Manual v1.49: Other filters</TITLE>
+ <TITLE>The DXSpider Administration Manual v1.50: Other filters</TITLE>
<LINK HREF="adminmanual-3.html" REL=next>
<LINK HREF="adminmanual-1.html" REL=previous>
<LINK HREF="adminmanual.html#toc2" REL=contents>
<HTML>
<HEAD>
<META NAME="GENERATOR" CONTENT="SGML-Tools 1.0.9">
- <TITLE>The DXSpider Administration Manual v1.49: Mail</TITLE>
+ <TITLE>The DXSpider Administration Manual v1.50: Mail</TITLE>
<LINK HREF="adminmanual-4.html" REL=next>
<LINK HREF="adminmanual-2.html" REL=previous>
<LINK HREF="adminmanual.html#toc3" REL=contents>
<P>
<P>To force the cluster to reread the file use load/forward
<P>
+<P>NB: If a user tries to send mail to a bulletin address that does not exist
+in this file, they will get an error.
<P>
<H2><A NAME="ss3.4">3.4 The msg command</A>
</H2>
<HTML>
<HEAD>
<META NAME="GENERATOR" CONTENT="SGML-Tools 1.0.9">
- <TITLE>The DXSpider Administration Manual v1.49: Scripts</TITLE>
+ <TITLE>The DXSpider Administration Manual v1.50: Scripts</TITLE>
<LINK HREF="adminmanual-5.html" REL=next>
<LINK HREF="adminmanual-3.html" REL=previous>
<LINK HREF="adminmanual.html#toc4" REL=contents>
# startup script example
#
# set maximum no of spots allowed to 100
-# set/var $Spot::maxspots = 1
+# set/var $Spot::maxspots = 100
#
# Set registration on
# set/var $main::reqreg = 1
a user can request with the <EM>sh/dx</EM> command. Normally the default is
to give 10 spots unless the user specifies more. Without this line enabled,
the maximum a user can request is 100 spots. Depending on your link quality
-you may wish to enable more or less by specifying the number. If you simply
-uncomment the line, the maximum would be 1 spot!
+you may wish to enable more or less by specifying the number.
<P>
<P>The other 2 options are dealt with more fully in the security section.
<P>
<HTML>
<HEAD>
<META NAME="GENERATOR" CONTENT="SGML-Tools 1.0.9">
- <TITLE>The DXSpider Administration Manual v1.49: Databases</TITLE>
+ <TITLE>The DXSpider Administration Manual v1.50: Databases</TITLE>
<LINK HREF="adminmanual-6.html" REL=next>
<LINK HREF="adminmanual-4.html" REL=previous>
<LINK HREF="adminmanual.html#toc5" REL=contents>
<HTML>
<HEAD>
<META NAME="GENERATOR" CONTENT="SGML-Tools 1.0.9">
- <TITLE>The DXSpider Administration Manual v1.49: Information, files and useful programs</TITLE>
+ <TITLE>The DXSpider Administration Manual v1.50: Information, files and useful programs</TITLE>
<LINK HREF="adminmanual-7.html" REL=next>
<LINK HREF="adminmanual-5.html" REL=previous>
<LINK HREF="adminmanual.html#toc6" REL=contents>
the setup. Many thanks to Fred Lloyd, the proprieter of
<A HREF="http://www.qrz.com">qrz.com</A> for allowing this access.
<P>
+<H2><A NAME="ss6.9">6.9 Connecting logging programs</A>
+</H2>
+
+<P>There appear to be very few logging programs out there that support telnet
+especially the popular ones like LogEQF, Turbolog etc. This can make it
+difficult to connect to your own cluster!
+The way to do it is to make the logging program think it has a TNC attached
+to a com port on the logging PC and 'push' a linux login out to it.
+This is achieved very simply by the use of <EM>agetty</EM>.
+<P>
+<P>All that is required is to add a line in /etc/inittab to have the client
+ready for a connection on the com port of your choice. Remember that in
+Linux, the com ports start at ttyS0 for com1, ttyS1 for com2 etc.
+<P>
+<BLOCKQUOTE><CODE>
+<PRE>
+c4:2345:respawn:/sbin/agetty -L 9600 ttyS1
+</PRE>
+</CODE></BLOCKQUOTE>
+<P>
+<P>Add this after the standard runlevel lines in /etc/inittab. The above
+line works on ttyS1 (com2). Now as root, issue the command <EM>telinit q</EM>
+and it should be ready for connection. All that is required is a 3 wire
+serial lead (tx, rx and signal ground). Tell you logging program to use
+8n1 at 9600 baud and you should see a Linux login prompt. Login as normal
+and then telnet from there to the cluster.
+<P>
<HR>
<A HREF="adminmanual-7.html">Next</A>
<A HREF="adminmanual-5.html">Previous</A>
<HTML>
<HEAD>
<META NAME="GENERATOR" CONTENT="SGML-Tools 1.0.9">
- <TITLE>The DXSpider Administration Manual v1.49: Security</TITLE>
+ <TITLE>The DXSpider Administration Manual v1.50: Java Web applet</TITLE>
<LINK HREF="adminmanual-8.html" REL=next>
<LINK HREF="adminmanual-6.html" REL=previous>
<LINK HREF="adminmanual.html#toc7" REL=contents>
<A HREF="adminmanual-6.html">Previous</A>
<A HREF="adminmanual.html#toc7">Contents</A>
<HR>
-<H2><A NAME="s7">7. Security</A></H2>
+<H2><A NAME="s7">7. Java Web applet</A></H2>
-<P>From version 1.49 DXSpider has some additional security features. These
-are not by any means meant to be exhaustive, however they do afford some
-security against piracy. These two new features can be used independently
-of each other or in concert to tighten the security.
+<P>In the spider tree will be a directory <EM>spider-web</EM>. This is a
+neat little java web applet that can be run from a website. The applet
+must run on the same machine as the cluster. The included README file is
+shown below.
<P>
-<H2><A NAME="ss7.1">7.1 Registration</A>
-</H2>
-
-<P>The basic principle of registration is simple. If a user is not registered
-by the sysop, then they have read-only access to the cluster. The only
-thing they can actually send is a talk or a message to the sysop. In
-order for them to be able to spot, send announces or talks etc the sysop
-must register them with the <EM>set/register</EM> command, like this ...
+<P>I should comment here that the applet is precompiled, that is, ready to go.
+It was compiled using JDK1.3.1. If your version is earlier than this then it
+may not work. Should that be the case you need to recompile or update your
+JDK. To recompile do the following ...
<P>
<BLOCKQUOTE><CODE>
<PRE>
-set/register g0vgs
+cd /spider/spider-web
+rm *.class
+/usr/bin/javac spiderclient.java
</PRE>
</CODE></BLOCKQUOTE>
-<P>The user g0vgs can now fully use the cluster. In order to enable
-registration, you can issue the command ...
<P>
-<BLOCKQUOTE><CODE>
-<PRE>
-set/var $main::reqreg = 1
-</PRE>
-</CODE></BLOCKQUOTE>
-<P>Any users that are not registered will now see the motd_nor file rather
-than the motd file as discussed in the Information, files and useful
-programs section.
-<P>
-<P>Entering this line at the prompt will only last for the time the cluster
-is running of course and would not be present on a restart. To make the
-change permanent, add the above line to /spider/scripts/startup. To
-read more on the startup file, see the section on Information, files
-and useful programs.
-<P>
-<P>To unregister a user use <EM>unset/register</EM> and to show the list
-of registered users, use the command <EM>show/register</EM>.
-<P>
-<H2><A NAME="ss7.2">7.2 Passwords</A>
-</H2>
-
-<P>At the moment, passwords only affect users who login to a DXSpider
-cluster node via telnet. If a user requires a password, they can
-either set it themselves or have the sysop enter it for them by using
-the <EM>set/password</EM> command. Any users who already have passwords,
-such as remote sysops, will be asked for their passwords automatically
-by the cluster. Using passwords in this way means that the user has a
-choice on whether to have a password or not. To force the use of
-passwords at login, issue the command ...
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
-set/var $main::passwdreq = 1
-</PRE>
-</CODE></BLOCKQUOTE>
-<P>at the cluster prompt. This can also be added to the /spider/scripts/startup
-file as above to make the change permanent.
+<P>I have used /usr/bin/javac as an example, your path to javac may be different.
<P>
-<P>Of course, if you do this you will have to assign a password for each of
-your users. If you were asking them to register, it is anticipated that
-you would ask them to send you a message both to ask to be registered and
-to give you the password they wish to use.
-<P>
-<P>Should a user forget their password, it can be reset by the sysop by
-first removing the existing password and then setting a new one like so ...
-<P>
-<BLOCKQUOTE><CODE>
<PRE>
-unset/password g0vgs
-set/password g0vgs new_password
+Spider-WEB v0.6b
+
+Completely based on a clx web client written in Java by dl6dbh
+(ftp://clx.muc.de/pub/clx/clx-java_10130001.tgz)
+
+The webserver has to run on the same machine as your DxSpider software!
+
+It is assumed that you have Java installed. You need JDK1.3.1 at least.
+
+Installation instructions (Performed as root):
+
+Put all the files in the spider-web directory into a newly created directory
+under the DocumentRoot of your websever for instance 'client'. In my case
+this is: /home/httpd/html/client/ although ymmv. For Suse the correct
+path should be /usr/local/httpd/htdocs/client/ for example.
+
+Move spider.cgi to the cgi-bin directory of your webserver, in my case that is
+/home/httpd/cgi-bin/ although ymmv. For Suse the correct path should be
+/usr/local/httpd/cgi-bin/ for example.
+
+Change the permissions of the files to ensure they are correct, obviously you
+will need to use the correct path the the files according to your system:
+
+chmod 755 /home/httpd/html/cgi-bin/spider.cgi
+chmod -R 755 /home/httpd/html/client/
+
+By default the spider.cgi script should pick up your hostname (As long as this
+is set correctly). If it does not or your hostname differs from the name that
+you attach to the public address that you are using, then edit spider.cgi :
+
+# Uncomment and set the hostname manually here if the above fails.
+# $HOSTNAME = "gb7mbc.spoo.org" ;
+$PORT = "8000" ;
+
+'HOSTNAME' is the hostname of your cluster.
+
+'PORT' is the portnumber that you use to connect to your DxSpider via
+telnet (see Listeners.pm)
+
+NOTE: If you can start the console but cannot connect to the cluster from it,
+then it is possible that the machine you are on cannot resolve the hostname of
+your cluster machine. If this is the case, you need to set your hostname
+manually as above.
+
+You also need to set the $NODECALL variable. This prints the name of your
+choosing (probably your cluster callsign) on the html page.
+
+You now can connect to Spider-Web via http://yourserver/cgi-bin/spider.cgi
</PRE>
-</CODE></BLOCKQUOTE>
<P>
<HR>
<A HREF="adminmanual-8.html">Next</A>
<HTML>
<HEAD>
<META NAME="GENERATOR" CONTENT="SGML-Tools 1.0.9">
- <TITLE>The DXSpider Administration Manual v1.49: CVS</TITLE>
+ <TITLE>The DXSpider Administration Manual v1.50: Security</TITLE>
<LINK HREF="adminmanual-9.html" REL=next>
<LINK HREF="adminmanual-7.html" REL=previous>
<LINK HREF="adminmanual.html#toc8" REL=contents>
<A HREF="adminmanual-7.html">Previous</A>
<A HREF="adminmanual.html#toc8">Contents</A>
<HR>
-<H2><A NAME="s8">8. CVS</A></H2>
+<H2><A NAME="s8">8. Security</A></H2>
-<P>CVS stands for "Concurrent Versions System" and the CVS for DXSpider is held
-at
-<A HREF="http://www.sourceforge.net">Sourceforge</A>. This means
-that it is possible to update your DXSpider installation to the latest
-sources by using a few simple commands.
+<P>From version 1.49 DXSpider has some additional security features. These
+are not by any means meant to be exhaustive, however they do afford some
+security against piracy. These two new features can be used independently
+of each other or in concert to tighten the security.
<P>
-<P>Please be aware that if you update your system using CVS, it is possible that
-you could be running code that is very beta and not fully tested. There is
-a possibility that it could be unstable.
-<P>
-<P>I am of course assuming that you have a machine with both DXSpider and
-Internet access running.
-<P>
-<P>BEFORE YOU EVEN CONSIDER STARTING WITH THIS MAKE A BACKUP OF YOUR
-ENTIRE SPIDER TREE!!
-<P>
-<P>Assuming you are connected to the Internet, you need to login to the
-CVS repository and then update your Spider source. There are several
-steps which are listed below ...
-<P>
-<P>First login as the user <EM>sysop</EM>. Next you need to connect to the CVS
-repository. You do this with the command below ...
+<H2><A NAME="ss8.1">8.1 Registration</A>
+</H2>
+
+<P>The basic principle of registration is simple. If a user is not registered
+by the sysop, then they have read-only access to the cluster. The only
+thing they can actually send is a talk or a message to the sysop. In
+order for them to be able to spot, send announces or talks etc the sysop
+must register them with the <EM>set/register</EM> command, like this ...
<P>
+<BLOCKQUOTE><CODE>
<PRE>
-cvs -d:pserver:anonymous@cvs.DXSpider.sourceforge.net:/cvsroot/dxspider login
+set/register g0vgs
</PRE>
-<P>You will get a password prompt. Simply hit return here and your machine should
-return to a normal linux prompt.
-<P>
-<P>What happens next depends on whether you have an existing installation that
-you want to update with the latest and greatest or whether you just want
-to see what is there and/or run it on a new machine for testing.
-<P>If you are installing Spider from CVS then change directory to /home/sysop
-<P>If you are wanting to update Spider then cd to /tmp
-<P>
-<P>The next step will create a brand new 'spider' directory in your current
-directory.
+</CODE></BLOCKQUOTE>
+<P>The user g0vgs can now fully use the cluster. In order to enable
+registration, you can issue the command ...
<P>
+<BLOCKQUOTE><CODE>
<PRE>
-cvs -z3 -d:pserver:anonymous@cvs.DXSpider.sourceforge.net:/cvsroot/dxspider co spider
+set/var $main::reqreg = 1
</PRE>
-<P>This command is all on one line.
+</CODE></BLOCKQUOTE>
+<P>Any users that are not registered will now see the motd_nor file rather
+than the motd file as discussed in the Information, files and useful
+programs section.
<P>
-<P>Hopefully your screen should show you downloading files. The -z3 simply compresses
-the download to improve speed.
-When this has finished, you will have exactly the same as if you had untarred a full
-tarball PLUS some extra directories and files that CVS needs to do the magic that
-it does.
+<P>Entering this line at the prompt will only last for the time the cluster
+is running of course and would not be present on a restart. To make the
+change permanent, add the above line to /spider/scripts/startup. To
+read more on the startup file, see the section on Information, files
+and useful programs.
<P>
-<P>Now if you are doing a new installation, that's it. Carry on as if you have
-just downloaded and untarred the lastest tarball.
+<P>To unregister a user use <EM>unset/register</EM> and to show the list
+of registered users, use the command <EM>show/register</EM>.
<P>
-<P>If you want to upgrade your current installation then do this ...
+<H2><A NAME="ss8.2">8.2 Passwords</A>
+</H2>
+
+<P>At the moment, passwords only affect users who login to a DXSpider
+cluster node via telnet. If a user requires a password, they can
+either set it themselves or have the sysop enter it for them by using
+the <EM>set/password</EM> command. Any users who already have passwords,
+such as remote sysops, will be asked for their passwords automatically
+by the cluster. Using passwords in this way means that the user has a
+choice on whether to have a password or not. To force the use of
+passwords at login, issue the command ...
<P>
<BLOCKQUOTE><CODE>
<PRE>
-tar cvfz /tmp/s.tgz spider
-cd /
-tar xvfzp /tmp/s.tgz
+set/var $main::passwdreq = 1
</PRE>
</CODE></BLOCKQUOTE>
-<P>This is assuming you downloaded to the /tmp directory of course.
-<P>
-<P>NOTE: the 'p' on the end of the 'xvfz' is IMPORTANT! It keeps the permissions
-correct. YOU WERE LOGGED IN AS THE USER SYSOP WEREN'T YOU?????
-<P>Remember to recompile the C client (cd /spider/src; make)
+<P>at the cluster prompt. This can also be added to the /spider/scripts/startup
+file as above to make the change permanent.
<P>
-<P>At this point the files have been upgraded. You can (usually) restart the cluster
-in your own time. However, if you attempt to use any new commands or features
-expect it to be fatal! At least your cluster will have been restarted then so it
-will be too late to worry about it!
+<P>Of course, if you do this you will have to assign a password for each of
+your users. If you were asking them to register, it is anticipated that
+you would ask them to send you a message both to ask to be registered and
+to give you the password they wish to use.
<P>
-<P>Now the magic part! From now on when you want to update, simply connect to the
-Internet and then, as the user <EM>sysop</EM> ...
+<P>Should a user forget their password, it can be reset by the sysop by
+first removing the existing password and then setting a new one like so ...
<P>
<BLOCKQUOTE><CODE>
<PRE>
-cd /spider
-cvs -z3 update -d
+unset/password g0vgs
+set/password g0vgs new_password
</PRE>
</CODE></BLOCKQUOTE>
-<P>and your files will be updated. As above, remember to recompile the "C" client
-if it has been updated (CVS will tell you) and restart if any of the perl scripts
-have been altered or added, again, CVS will tell you.
-<P>
-<P>You will find any changes documented in the /spider/Changes file.
<P>
<HR>
<A HREF="adminmanual-9.html">Next</A>
<HTML>
<HEAD>
<META NAME="GENERATOR" CONTENT="SGML-Tools 1.0.9">
- <TITLE>The DXSpider Administration Manual v1.49: The DXSpider command set</TITLE>
+ <TITLE>The DXSpider Administration Manual v1.50: CVS</TITLE>
+ <LINK HREF="adminmanual-10.html" REL=next>
<LINK HREF="adminmanual-8.html" REL=previous>
<LINK HREF="adminmanual.html#toc9" REL=contents>
<link rel=stylesheet href="style.css" type="text/css" title="default stylesheet">
</HEAD>
<BODY>
-Next
+<A HREF="adminmanual-10.html">Next</A>
<A HREF="adminmanual-8.html">Previous</A>
<A HREF="adminmanual.html#toc9">Contents</A>
<HR>
-<H2><A NAME="s9">9. The DXSpider command set</A></H2>
+<H2><A NAME="s9">9. CVS</A></H2>
-<P>Below is a complete list of commands available from the cluster prompt.
-Most maintenance tasks are automatic but there are some commands that are useful
-for a sysop. These are listed below in alphabetical order. The number in
-brackets following the command name is the permissions level needed to use
-the command.
+<P>CVS stands for "Concurrent Versions System" and the CVS for DXSpider is held
+at
+<A HREF="http://www.sourceforge.net">Sourceforge</A>. This means
+that it is possible to update your DXSpider installation to the latest
+sources by using a few simple commands.
<P>
-<H2><A NAME="ss9.1">9.1 accept/announce (0)</A>
-</H2>
-
-<P><CODE><B>accept/announce [0-9] <pattern></B> Set an accept filter
-line for announce</CODE>
-<P>
-<P>Create an 'accept this announce' line for a filter.
-<P>An accept filter line means that if the announce matches this filter it is
-passed onto the user. See HELP FILTERS for more info. Please read this
-to understand how filters work - it will save a lot of grief later on.
-<P>You can use any of the following things in this line:-
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
- info <string> eg: iota or qsl
- by <prefixes> eg: G,M,2
- origin <prefixes>
- origin_dxcc <numbers> eg: 61,62 (from eg: sh/pre G)
- origin_itu <numbers>
- origin_zone <numbers>
- by_dxcc <numbers>
- by_itu <numbers>
- by_zone <numbers>
- channel <prefixes>
- wx 1 filter WX announces
- dest <prefixes> eg: 6MUK,WDX (distros)
-</PRE>
-</CODE></BLOCKQUOTE>
-<P>some examples:-
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
- acc/ann dest 6MUK
- acc/ann 2 by_zone 14,15,16
- (this could be all on one line: acc/ann dest 6MUK or by_zone 14,15,16)
-</PRE>
-</CODE></BLOCKQUOTE>
-<P>or
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
- acc/ann by G,M,2
-</PRE>
-</CODE></BLOCKQUOTE>
-<P>This filter would only allow announces that were posted buy UK stations.
-You can use the tag 'all' to accept everything eg:
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
- acc/ann all
-</PRE>
-</CODE></BLOCKQUOTE>
-<P>but this probably for advanced users...
-<P>
-<H2><A NAME="ss9.2">9.2 accept/announce (extended for sysops) (8)</A>
-</H2>
-
-<P><CODE><B>accept/announce <call> [input] [0-9]<pattern></B> Announce filter sysop version</CODE>
-<P>
-<P>This version allows a sysop to set a filter for a callsign as well as the
-default for nodes and users eg:-
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
- accept/ann by G,M,2
- accept/ann input node_default by G,M,2
- accept/ann user_default by G,M,2
-</PRE>
-</CODE></BLOCKQUOTE>
-<P>
-<H2><A NAME="ss9.3">9.3 accept/route (8)</A>
-</H2>
-
-<P><CODE><B>accept/route <call> [0-9] <pattern></B> Set an 'accept' filter line for routing</CODE>
-<P>
-<P>Create an 'accept this routing PC Protocol' line for a filter.
-<P>
-<P>An accept filter line means that if a PC16/17/19/21/24/41/50 matches this filter
-it is passed thru that interface. See HELP FILTERING for more info. Please read this
-to understand how filters work - it will save a lot of grief later on.
-<P>
-<P>You can use any of the following things in this line:-
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
- call <prefixes> the callsign of the thingy
- call_dxcc <numbers> eg: 61,62 (from eg: sh/pre G)
- call_itu <numbers>
- call_zone <numbers>
- origin <prefixes> really the interface it came in on
- origin_dxcc <numbers> eg: 61,62 (from eg: sh/pre G)
- origin_itu <numbers>
- origin_zone <numbers>
-</PRE>
-</CODE></BLOCKQUOTE>
-<P>
-<P>some examples:-
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
- acc/route gb7djk call_dxcc 61,38 (send only UK+EIRE nodes)
- acc/route gb7djk call gb7djk (equiv to SET/ISOLATE)
-</PRE>
-</CODE></BLOCKQUOTE>
-<P>
-<P>You can use the tag 'all' to accept everything eg:
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
- acc/route all
-</PRE>
-</CODE></BLOCKQUOTE>
-<P>
-<H2><A NAME="ss9.4">9.4 accept/spots (0)</A>
-</H2>
-
-<P><CODE><B>accept/spots [0-9] <pattern></B> Set an accept filter line for spots</CODE>
-<P>
-<P>Create an 'accept this spot' line for a filter.
-<P>
-<P>An accept filter line means that if the spot matches this filter it is
-passed onto the user. See HELP FILTERS for more info. Please read this
-to understand how filters work - it will save a lot of grief later on.
-<P>You can use any of the following things in this line:-
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
- freq <range> eg: 0/30000 or hf or hf/cw or 6m,4m,2m
- on <range> same as 'freq'
- call <prefixes> eg: G,PA,HB9
- info <string> eg: iota or qsl
- by <prefixes>
- call_dxcc <numbers> eg: 61,62 (from eg: sh/pre G)
- call_itu <numbers>
- call_zone <numbers>
- by_dxcc <numbers>
- by_itu <numbers>
- by_zone <numbers>
- origin <prefixes>
- channel <prefixes>
-</PRE>
-</CODE></BLOCKQUOTE>
-<P>
-<P>For frequencies, you can use any of the band names defined in
-SHOW/BANDS and you can use a subband name like: cw, rtty, data, ssb -
-thus: hf/ssb. You can also just have a simple range like: 0/30000 -
-this is more efficient than saying simply: freq HF (but don't get
-too hung up about that)
-<P>some examples:-
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
- acc/spot 1 on hf/cw
- acc/spot 2 on vhf and (by_zone 14,15,16 or call_zone 14,15,16)
-</PRE>
-</CODE></BLOCKQUOTE>
-<P>You can use the tag 'all' to accept everything, eg:
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
- acc/spot 3 all
-</PRE>
-</CODE></BLOCKQUOTE>
-<P>but this probably for advanced users...
-<P>
-<H2><A NAME="ss9.5">9.5 accept/spots (extended for sysops) (8)</A>
-</H2>
-
-<P><CODE><B>accept/spots <call> [input] [0-9] <pattern></B> Spot filter sysop version</CODE>
-<P>
-<P>This version allows a sysop to set a filter for a callsign as well as the
-default for nodes and users eg:-
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
- accept/spot db0sue-7 1 by_zone 14,15,16
- accept/spot node_default all
- set/hops node_default 10
-
- accept/spot user_default by G,M,2
-</PRE>
-</CODE></BLOCKQUOTE>
-<P>
-<H2><A NAME="ss9.6">9.6 accept/wcy (0)</A>
-</H2>
-
-<P><CODE><B>accept/wcy [0-9] <pattern></B> set an accept WCY filter</CODE>
-<P>
-<P>It is unlikely that you will want to do this, but if you do then you can
-filter on the following fields:-
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
- by <prefixes> eg: G,M,2
- origin <prefixes>
- origin_dxcc <numbers> eg: 61,62 (from eg: sh/pre G)
- origin_itu <numbers>
- origin_zone <numbers>
- by_dxcc <numbers>
- by_itu <numbers>
- by_zone <numbers>
- channel <prefixes>
-</PRE>
-</CODE></BLOCKQUOTE>
-<P>
-<P>There are no examples because WCY Broadcasts only come from one place and
-you either want them or not (see UNSET/WCY if you don't want them).
-<P>This command is really provided for future use.
-<P>See HELP FILTER for information.
-<P>
-<H2><A NAME="ss9.7">9.7 accept/wcy (extended for sysops) (8)</A>
-</H2>
-
-<P><CODE><B>accept/wcy <call> [input] [0-9] <pattern></B>
-WCY filter sysop version</CODE>
-<P>
-<P>This version allows a sysop to set a filter for a callsign as well as the
-default for nodes and users eg:-
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
- accept/wcy node_default all
- set/hops node_default 10
-</PRE>
-</CODE></BLOCKQUOTE>
-<P>
-<H2><A NAME="ss9.8">9.8 accept/wwv (0)</A>
-</H2>
-
-<P><CODE><B>accept/wwv [0-9] <pattern></B> Set an accept WWV filter</CODE>
-<P>
-<P>It is unlikely that you will want to do this, but if you do then you can
-filter on the following fields:-
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
- by <prefixes> eg: G,M,2
- origin <prefixes>
- origin_dxcc <numbers> eg: 61,62 (from eg: sh/pre G)
- origin_itu <numbers>
- origin_zone <numbers>
- by_dxcc <numbers>
- by_itu <numbers>
- by_zone <numbers>
- channel <prefixes>
-</PRE>
-</CODE></BLOCKQUOTE>
-<P>for example
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
- accept/wwv by_zone 4
-</PRE>
-</CODE></BLOCKQUOTE>
-<P>is probably the only useful thing to do (which will only show WWV broadcasts
-by stations in the US).
-<P>See HELP FILTER for information.
-<P>
-<H2><A NAME="ss9.9">9.9 accept/wwv (extended for sysops) (8)</A>
-</H2>
-
-<P><CODE><B>accept/wwv <call> [input] [0-9] <pattern></B>
-WWV filter sysop version</CODE>
-<P>
-<P>This version allows a sysop to set a filter for a callsign as well as the
-default for nodes and users eg:-
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
- accept/wwv db0sue-7 1 by_zone 4
- accept/wwv node_default all
- set/hops node_default 10
-
- accept/wwv user_default by W,K
-</PRE>
-</CODE></BLOCKQUOTE>
-<P>
-<H2><A NAME="ss9.10">9.10 announce (0)</A>
-</H2>
-
-<P><CODE><B>announce <text></B> Send an announcement to local users</CODE>
-<P>
-<P>Send an announcement to LOCAL users only, where <text> is the text
-of the announcement you wish to broadcast. If you do not wish to receive
-announces, use the <EM>set/noannounce</EM> command. Any announces made by
-a sysop will override set/noannounce.
-<P>
-<H2><A NAME="ss9.11">9.11 announce full (0)</A>
-</H2>
-
-<P><CODE><B>announce full <text></B> Send an announcement cluster wide</CODE>
-<P>
-<P>This command will send your announcement across the whole cluster
-network.
-<P>
-<P>
-<H2><A NAME="ss9.12">9.12 announce sysop (5)</A>
-</H2>
-
-<P><CODE><B>announce sysop <text></B></CODE>
-<P>
-<P>Send an announcement to Sysops only
-<P>
-<H2><A NAME="ss9.13">9.13 apropos (0)</A>
-</H2>
-
-<P><CODE><B>apropos <string></B> Search the help database</CODE>
-<P>
-<P>Search the help database for <string> (it isn't case sensitive),
-and print the names of all the commands that may be relevant.
-<P>
-<H2><A NAME="ss9.14">9.14 bye (0)</A>
-</H2>
-
-<P><CODE><B>bye</B> Exit from the cluster</CODE>
-<P>
-<P>This will disconnect you from the cluster
-<P>
-<H2><A NAME="ss9.15">9.15 catchup (5)</A>
-</H2>
-
-<P><CODE><B>catchup <node_call> All|[<msgno> ...]</B> Mark a message as sent</CODE>
-<P>
-<P>When you send messages the fact that you have forwarded it to another node
-is remembered so that it isn't sent again. When you have a new partner
-node and you add their callsign to your /spider/msg/forward.pl file, all
-outstanding non-private messages will be forwarded to them. This may well
-be ALL the non-private messages. You can prevent this by using these
-commmands:-
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
- catchup GB7DJK all
- catchup GB7DJK 300 301 302 303 500-510
-</PRE>
-</CODE></BLOCKQUOTE>
-<P>and to undo what you have just done:-
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
- uncatchup GB7DJK all
- uncatchup GB7DJK 300 301 302 303 500-510
-</PRE>
-</CODE></BLOCKQUOTE>
-<P>which will arrange for them to be forward candidates again.
-<P>Order is not important.
-<P>
-<H2><A NAME="ss9.16">9.16 clear/announce (8)</A>
-</H2>
-
-<P><CODE><B>clear/announce [input] <callsign> [0-9|all]</B> Clear an announce filter line</CODE>
-<P>
-<P>A sysop can clear an input or normal output filter for a user or the
-node_default or user_default.
-<P>
-<H2><A NAME="ss9.17">9.17 clear/route (8)</A>
-</H2>
-
-<P><CODE><B>clear/route [input] ^lt;callsign> [0-9|all]</B> Clear a route filter line</CODE>
-<P>
-<P>This command allows you to clear (remove) a line in a route filter or to
-remove the whole filter.
-<P>see CLEAR/SPOTS for a more detailed explanation.
-<P>A sysop can clear an input or normal output filter for a user or the
-node_default or user_default.
-<P>
-<H2><A NAME="ss9.18">9.18 clear/spots (0)</A>
-</H2>
-
-<P><CODE><B>clear/spots [1|all]</B> Clear a spot filter line</CODE>
-<P>
-<P>This command allows you to clear (remove) a line in a spot filter or to
-remove the whole filter.
-<P>If you have a filter:-
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
- acc/spot 1 on hf/cw
- acc/spot 2 on vhf and (by_zone 14,15,16 or call_zone 14,15,16)
-</PRE>
-</CODE></BLOCKQUOTE>
-<P>and you say:-
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
- clear/spot 1
-</PRE>
-</CODE></BLOCKQUOTE>
-<P>you will be left with:-
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
- acc/spot 2 on vhf and (by_zone 14,15,16 or call_zone 14,15,16)
-</PRE>
-</CODE></BLOCKQUOTE>
-<P>If you do:
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
- clear/spot all
-</PRE>
-</CODE></BLOCKQUOTE>
-<P>the filter will be completely removed.
-<P>
-<H2><A NAME="ss9.19">9.19 clear/spots (extended for sysops) (8)</A>
-</H2>
-
-<P><CODE><B>clear/spots [input] <callsign> [0-9|all]</B> Clear a spot filter line</CODE>
-<P>
-<P>A sysop can clear an input or normal output filter for a user or the
-node_default or user_default.
-<P>
-<H2><A NAME="ss9.20">9.20 clear/wcy (0)</A>
-</H2>
-
-<P><CODE><B>clear/wcy [1|all]</B> Clear a WCY filter line</CODE>
-<P>
-<P>This command allows you to clear (remove) a line in a WCY filter or to
-remove the whole filter.
-<P>see CLEAR/SPOTS for a more detailed explanation.
-<P>
-<H2><A NAME="ss9.21">9.21 clear/wcy (extended for sysops) (8)</A>
-</H2>
-
-<P><CODE><B>clear/wcy [input] <callsign> [0-9|all]</B> Clear a WCY filter line</CODE>
-<P>
-<P>A sysop can clear an input or normal output filter for a user or the
-node_default or user_default.
-<P>
-<H2><A NAME="ss9.22">9.22 clear/wwv (0)</A>
-</H2>
-
-<P><CODE><B>clear/wwv [1|all]</B> Clear a WWV filter line</CODE>
-<P>
-<P>This command allows you to clear (remove) a line in a WWV filter or to
-remove the whole filter.
-<P>see CLEAR/SPOTS for a more detailed explanation.
-<P>
-<H2><A NAME="ss9.23">9.23 clear/wwv (extended for sysops) (8)</A>
-</H2>
-
-<P><CODE><B>clear/wwv [input] <callsign> [0-9|all]</B> Clear a WWV filter line</CODE>
-<P>
-<P>A sysop can clear an input or normal output filter for a user or the
-node_default or user_default.
-<P>
-<H2><A NAME="ss9.24">9.24 connect (5) </A>
-</H2>
-
-<P><CODE><B>connect <callsign></B> Start a connection to another DX Cluster</CODE>
-<P>
-<P>Start a connection process that will culminate in a new connection to the
-DX cluster <callsign>. This process creates a new 'client' process which will
-use the script in /spider/connect/<callsign> to effect the 'chat' exchange
-necessary to traverse the network(s) to logon to the cluster <callsign>.
-<P>
-<H2><A NAME="ss9.25">9.25 dbavail (0)</A>
-</H2>
-
-<P><CODE><B>dbavail</B> Show a list of all the databases in the system</CODE>
-<P>
-<P>The title says it all really, this command lists all the databases defined
-in the system. It is also aliased to SHOW/COMMAND.
-<P>
-<H2><A NAME="ss9.26">9.26 dbcreate (9)</A>
-</H2>
-
-<P><CODE><B>dbcreate <name></B> Create a database entry<BR>
-<B>dbcreate <name> chain <name> [<name>..]</B> Create a chained database entry<BR>
-<B>dbcreate <name> remote <node></B> Create a remote database
-entry<BR></CODE>
-<P>
-<P>DBCREATE allows you to define a database in the system. It doesn't actually
-create anything, just defines it.
-<P>The databases that are created are simple DB_File hash databases, they are
-therefore already 'indexed'.
-<P>You can define a local database with the first form of the command eg:
-<P>DBCREATE oblast
-<P>You can also chain databases with the addition of the 'chain' keyword.
-This will search each database one after the other. A typical example
-is:
-<P>DBCREATE sdx_qsl chain sql_ad
-<P>No checking is done to see if the any of the chained databases exist, in
-fact it is usually better to do the above statement first then do each of
-the chained databases.
-<P>Databases can exist offsite. To define a database that lives on another
-node do:
-<P>DBCREATE buckmaster remote gb7dxc
-<P>Remote databases cannot be chained; however, the last database in a
-a chain can be a remote database eg:
-<P>DBCREATE qsl chain gb7dxc
-<P>To see what databases have been defined do:
-<P>DBAVAIL (or it will have been aliased to SHOW/COMMAND)
-<P>It would be normal for you to add an entry into your local Aliases file
-to allow people to use the 'SHOW/<dbname>' style syntax. So you would
-need to add a line like:-
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
- 's' => [
- ..
- ..
- '^sh\w*/buc', 'dbshow buckmaster', 'dbshow',
- ..
- ..
- ],
-</PRE>
-</CODE></BLOCKQUOTE>
-<P>to allow
-<P>SH/BUCK g1tlh
-<P>to work as they may be used to.
-<P>See DBIMPORT for the importing of existing AK1A format data to databases.
-See DBSHOW for generic database enquiry
-<P>
-<H2><A NAME="ss9.27">9.27 dbimport (9)</A>
-</H2>
-
-<P><CODE><B>dbimport <dbname></B> Import AK1A data into a database</CODE>
-<P>
-<P>If you want to import or update data in bulk to a database you can use
-this command. It will either create or update entries into an existing
-database. For example:-
-<P>DBIMPORT oblast /tmp/OBLAST.FUL
-<P>will import the standard OBLAST database that comes with AK1A into the
-oblast database held locally.
-<P>
-<H2><A NAME="ss9.28">9.28 dbremove (9)</A>
-</H2>
-
-<P><CODE><B>dbremove <dbname></B> Delete a database</CODE>
-<P>
-<P>DBREMOVE will completely remove a database entry and also delete any data
-file that is associated with it.
-<P>There is no warning, no comeback, no safety net.
-<P>For example:
-<P>DBREMOVE oblast
-<P>will remove the oblast database from the system and it will also remove
-the associated datafile.
-<P>I repeat:
-<P>There is no warning, no comeback, no safety net.
-<P>You have been warned.
-<P>
-<H2><A NAME="ss9.29">9.29 dbshow (0)</A>
-</H2>
-
-<P><CODE><B>dbshow <dbname> <key></B> Display an entry, if it exists, in a database</CODE>
-<P>
-<P>This is the generic user interface to the database to the database system.
-It is expected that the sysop will add an entry to the local Aliases file
-so that users can use the more familiar AK1A style of enquiry such as:
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
- SH/BUCK G1TLH
-</PRE>
-</CODE></BLOCKQUOTE>
-<P>but if he hasn't and the database really does exist (use DBAVAIL or
-SHOW/COMMAND to find out) you can do the same thing with:
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
- DBSHOW buck G1TLH
-</PRE>
-</CODE></BLOCKQUOTE>
-<P>
-<P>
-<H2><A NAME="ss9.30">9.30 debug (9)</A>
-</H2>
-
-<P><CODE><B>debug</B> Set the cluster program into debug mode</CODE>
-<P>
-<P>Executing this command will only have an effect if you are running the cluster
-in debug mode i.e.
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
- perl -d cluster.pl
-</PRE>
-</CODE></BLOCKQUOTE>
-<P>It will interrupt the cluster just after the debug command has finished.
-<P>
-<H2><A NAME="ss9.31">9.31 delete/user (9)</A>
-</H2>
-
-<P><CODE><B>delete/user <callsign></B> Delete a user from the User Database</CODE>
-<P>
-<P>This command will completely remove a one or more users from the database.
-<P>There is NO SECOND CHANCE.
-<P>It goes without saying that you should use this command CAREFULLY!
-<P>
-<P>
-<H2><A NAME="ss9.32">9.32 directory (0)</A>
-</H2>
-
-<P><CODE><B>directory</B> List messages<BR> <B>directory all</B> List all messages<BR>
-<B>directory own</B> List your own messages<BR>
-<B>directory new</B> List all new messages<BR>
-<B>directory to <call></B> List all messages to <call><BR>
-<B>directory from <call></B> List all messages from <call><BR>
-<B>directory subject <string></B> List all messages with <string> in subject<BR>
-<B>directory <nn></B> List last <nn> messages<BR>
-<B>directory <from>-<to></B> List messages <from> message <to> message <BR></CODE>
-<P>
-<P>List the messages in the messages directory.
-<P>If there is a 'p' one space after the message number then it is a
-personal message. If there is a '-' between the message number and the
-'p' then this indicates that the message has been read.
-<P>You can use shell escape characters such as '*' and '?' in the <call>
-fields.
-<P>You can combine some of the various directory commands together eg:-
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
- DIR TO G1TLH 5
-or
- DIR SUBJECT IOTA 200-250
-</PRE>
-</CODE></BLOCKQUOTE>
-<P>You can abbreviate all the commands to one letter and use ak1a syntax:-
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
- DIR/T G1* 10
- DIR/S QSL 10-100 5
-</PRE>
-</CODE></BLOCKQUOTE>
-<P>
-<P>
-<H2><A NAME="ss9.33">9.33 directory (extended for sysops) (5)</A>
-</H2>
-
-<P>Works just like the user command except that sysops can see ALL messages.
-<P>
-<H2><A NAME="ss9.34">9.34 disconnect (8)</A>
-</H2>
-
-<P><CODE><B>disconnect <call> [<call> ...]</B> Disconnect a user or node</CODE>
-<P>
-<P>Disconnect any <call> connected locally
-<P>
-<H2><A NAME="ss9.35">9.35 dx (0)</A>
-</H2>
-
-<P><CODE><B>dx [by <call>] <freq> <call> <remarks></B> Send a DX spot</CODE>
-<P>
-<P>This is how you send a DX Spot to other users. You can, in fact, now
-enter the <freq> and the <call> either way round.
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
- DX FR0G 144.600
- DX 144.600 FR0G
- DX 144600 FR0G
-</PRE>
-</CODE></BLOCKQUOTE>
-<P>will all give the same result. You can add some remarks to the end
-of the command and they will be added to the spot.
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
- DX FR0G 144600 this is a test
-</PRE>
-</CODE></BLOCKQUOTE>
-<P>You can credit someone else by saying:-
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
- DX by G1TLH FR0G 144.600 he isn't on the cluster
-</PRE>
-</CODE></BLOCKQUOTE>
-<P>The <freq> is compared against the available bands set up in the
-cluster. See SHOW/BANDS for more information.
-<P>
-<H2><A NAME="ss9.36">9.36 export (9)</A>
-</H2>
-
-<P><CODE><B>export <msgno> <filename></B> Export a message to a file</CODE>
-<P>
-<P>Export a message to a file. This command can only be executed on a local
-console with a fully privileged user. The file produced will be in a form
-ready to be imported back into the cluster by placing it in the import
-directory (/spider/msg/import).
-<P>This command cannot overwrite an existing file. This is to provide some
-measure of security. Any files written will owned by the same user as the
-main cluster, otherwise you can put the new files anywhere the cluster can
-access. For example:-
-<P>EXPORT 2345 /tmp/a
-<P>
-<H2><A NAME="ss9.37">9.37 export_users (9)</A>
-</H2>
-
-<P><CODE><B>export_users [<filename>]</B> Export the users database to ascii</CODE>
-<P>
-<P>Export the users database to a file in ascii format. If no filename
-is given then it will export the file to /spider/data/user_asc.
-<P>If the file already exists it will be renamed to <filename>.o. In fact
-up to 5 generations of the file can be kept each one with an extra 'o' on the
-suffix.
-<P>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.
-<P>
-<H2><A NAME="ss9.38">9.38 filtering (0)</A>
-</H2>
-
-<P><CODE><B>filtering</B> Filtering things in DXSpider</CODE>
-<P>
-<P>There are a number of things you can filter in the DXSpider system. They
-all use the same general mechanism.
-<P>In general terms you can create a 'reject' or an 'accept' filter which
-can have up to 10 lines in it. You do this using, for example:-
-<P>accept/spots .....
-reject/spots .....
-<P>where ..... are the specific commands for that type of filter. There
-are filters for spots, wwv, announce, wcy and (for sysops)
-connects. See each different accept or reject command reference for
-more details.
-<P>There is also a command to clear out one or more lines in a filter and
-one to show you what you have set. They are:-
-<P>clear/spots 1
-clear/spots all
-<P>and
-<P>show/filter
-<P>There is clear/xxxx command for each type of filter.
-<P>For now we are going to use spots for the examples, but you can apply
-the principles to all types of filter.
-<P>There are two main types of filter 'accept' or 'reject'; which you use
-depends entirely on how you look at the world and what is least
-writing to achieve what you want. Each filter has 10 lines (of any
-length) which are tried in order. If a line matches then the action
-you have specified is taken (ie reject means ignore it and accept
-means gimme it).
-<P>The important thing to remember is that if you specify a 'reject'
-filter (all the lines in it say 'reject/spots' (for instance) then if
-a spot comes in that doesn't match any of the lines then you will get
-it BUT if you specify an 'accept' filter then any spots that don't
-match are dumped. For example if I have a one line accept filter:-
-<P>accept/spots on vhf and (by_zone 14,15,16 or call_zone 14,15,16)
-<P>then automatically you will ONLY get VHF spots from or to CQ zones 14
-15 and 16. If you set a reject filter like:
-<P>reject/spots on hf/cw
-<P>Then you will get everything EXCEPT HF CW spots, If you am interested in IOTA
-and will work it even on CW then you could say:-
-<P>reject/spots on hf/cw and not info iota
-<P>But in that case you might only be interested in iota and say:-
-<P>accept/spots not on hf/cw or info iota
-<P>which is exactly the same. You should choose one or the other until
-you are confortable with the way it works. Yes, you can mix them
-(actually you can have an accept AND a reject on the same line) but
-don't try this at home until you can analyse the results that you get
-without ringing up the sysop for help.
-<P>You can arrange your filter lines into logical units, either for your
-own understanding or simply convenience. I have one set frequently:-
-<P>reject/spots 1 on hf/cw
-reject/spots 2 on 50000/1400000 not (by_zone 14,15,16 or call_zone 14,15,16)
-<P>What this does is to ignore all HF CW spots (being a class B I can't
-read any CW and couldn't possibly be interested in HF :-) and also
-rejects any spots on VHF which don't either originate or spot someone
-in Europe.
-<P>This is an exmaple where you would use the line number (1 and 2 in
-this case), if you leave the digit out, the system assumes '1'. Digits
-'0'-'9' are available.
-<P>You can leave the word 'and' out if you want, it is implied. You can
-use any number of brackets to make the 'expression' as you want
-it. There are things called precedence rules working here which mean
-that you will NEED brackets in a situation like line 2 because,
-without it, will assume:-
-<P>(on 50000/1400000 and by_zone 14,15,16) or call_zone 14,15,16
-<P>annoying, but that is the way it is. If you use OR - use
-brackets. Whilst we are here CASE is not important. 'And BY_Zone' is
-just 'and by_zone'.
-<P>If you want to alter your filter you can just redefine one or more
-lines of it or clear out one line. For example:-
-<P>reject/spots 1 on hf/ssb
-<P>or
-<P>clear/spots 1
-<P>To remove the filter in its entirty:-
-<P>clear/spots all
-<P>There are similar CLEAR commands for the other filters:-
-<P>clear/announce
-clear/wcy
-clear/wwv
-<P>ADVANCED USERS:-
-<P>Once you are happy with the results you get, you may like to experiment.
-<P>my example that filters hf/cw spots and accepts vhf/uhf spots from EU
-can be written with a mixed filter, eg:
-<P>rej/spot on hf/cw
-acc/spot on 0/30000
-acc/spot 2 on 50000/1400000 and (by_zone 14,15,16 or call_zone 14,15,16)
-<P>each filter slot actually has a 'reject' slot and an 'accept'
-slot. The reject slot is executed BEFORE the accept slot.
-<P>It was mentioned earlier that after a reject test that doesn't match,
-the default for following tests is 'accept', the reverse is true for
-'accept'. In the example what happens is that the reject is executed
-first, any non hf/cw spot is passed to the accept line, which lets
-thru everything else on HF.
-<P>The next filter line lets through just VHF/UHF spots from EU.
-<P>
-<H2><A NAME="ss9.39">9.39 forward/latlong (8)</A>
-</H2>
-
-<P><CODE><B>forward/latlong <node_call></B> Send latitude and longitude information to another cluster</CODE>
-<P>
-<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.
-<P>
-<H2><A NAME="ss9.40">9.40 forward/opername (1)</A>
-</H2>
-
-<P><CODE><B>forward/opername <call></B> Send out information on this <call> to all clusters</CODE>
-<P>
-<P>This command sends out any information held in the user file which can
-be broadcast in PC41 protocol packets. This information is Name, QTH, Location
-and Homenode. PC41s are only sent for the information that is available.
-<P>
-<H2><A NAME="ss9.41">9.41 help (0)</A>
-</H2>
-
-<P><CODE><B>help <cmd></B> Get help on a command</CODE>
-<P>
-<P>All commands can be abbreviated, so SHOW/DX can be abbreviated
-to SH/DX, ANNOUNCE can be shortened to AN and so on.
-<P>Look at the APROPOS <string> command which will search the help database
-for the <string> you specify and give you a list of likely commands
-to look at with HELP.
-<P>
-<H2><A NAME="ss9.42">9.42 init (5)</A>
-</H2>
-
-<P><CODE><B>init <node call></B> Re-initialise a link to an AK1A compatible node</CODE>
-<P>
-<P>This command attempts to re-initialise a link to a (usually) AK1A node
-that has got confused, usually by a protocol loop of some kind. It may
-work - but you usually will be better off simply disconnecting it (or
-better, if it is a real AK1A node, doing an RCMD <node> DISC/F <your
-node>).
-<P>Best of luck - you will need it.
-<P>
-<H2><A NAME="ss9.43">9.43 kill (0)</A>
-</H2>
-
-<P><CODE><B>kill <msgno> [<msgno> ..]</B> Delete a message from the local system</CODE>
-<P>
-<P>Delete a message from the local system. You will only be able to
-delete messages that you have originated or been sent (unless you are
-the sysop).
-<P>
-<H2><A NAME="ss9.44">9.44 kill (5)</A>
-</H2>
-
-<P><CODE><B>kill <msgno> [<msgno> ...]</B> Remove or erase a message from the system<BR>
-<B>kill from <call></B> Remove all messages from a callsign<BR>
-<B>kill to <call></B> Remove all messages to a callsign<BR></CODE>
-<P>
-<P>You can get rid of any message to or originating from your callsign using
-this command. You can remove more than one message at a time.
-<P>As a sysop you can kill any message on the system.
-<P>
-<H2><A NAME="ss9.45">9.45 kill full (5)</A>
-</H2>
-
-<P><CODE><B>kill full <msgno> [<msgno>]</B> Delete a message from the whole cluster</CODE>
-<P>
-<P>Delete a message (usually a 'bulletin') from the whole cluster system.
-<P>This uses the subject field, so any messages that have exactly the same subject
-will be deleted. Beware!
-<P>
-<H2><A NAME="ss9.46">9.46 kill/expunge (6)</A>
-</H2>
-
-<P><CODE><B>kill/expunge <msgno> [<msgno>..]</B>Expunge a message</CODE>
-<P>
-<P>Deleting a message using the normal KILL commands only marks that message
-for deletion. The actual deletion only happens later (usually two days later).
-<P>The KILL EXPUNGE command causes the message to be truly deleted more or less
-immediately.
-<P>It otherwise is used in the same way as the KILL command.
-<P>
-<P>
-<H2><A NAME="ss9.47">9.47 links (0)</A>
-</H2>
-
-<P><CODE><B>links</B> Show which nodes are physically connected</CODE>
-<P>
-<P>This is a quick listing that shows which links are connected and
-some information about them. See WHO for a list of all connections.
-<P>
-<P>
-<H2><A NAME="ss9.48">9.48 load/aliases (9)</A>
-</H2>
-
-<P><CODE><B>load/aliases</B> Reload the command alias table</CODE>
-<P>
-<P>Reload the /spider/cmd/Aliases file after you have editted it. You will need to
-do this if you change this file whilst the cluster is running in order for the
-changes to take effect.
-<P>
-<H2><A NAME="ss9.49">9.49 load/badmsg (9)</A>
-</H2>
-
-<P><CODE><B>load/badmsg</B> Reload the bad message table</CODE>
-<P>
-<P>Reload the /spider/msg/badmsg.pl file if you have changed it manually whilst
-the cluster is running. This table contains a number of perl regular
-expressions which are searched for in the fields targetted of each message.
-If any of them match then that message is immediately deleted on receipt.
-<P>
-<H2><A NAME="ss9.50">9.50 load/badwords (9)</A>
-</H2>
-
-<P><CODE><B>load/badwords</B> Reload the bad words table</CODE>
-<P>
-<P>Reload the /spider/data/badwords file if you have changed it manually whilst
-the cluster is running. This file contains a list of words which, if found
-on certain text portions of PC protocol, will cause those protocol frames
-to be rejected. It will all put out a message if any of these words are
-used on the announce, dx and talk commands. The words can be one or
-more on a line, lines starting with '#' are ignored.
-<P>
-<H2><A NAME="ss9.51">9.51 load/bands (9)</A>
-</H2>
-
-<P><CODE><B>load/bands</B> Reload the band limits table</CODE>
-<P>
-<P>Reload the /spider/data/bands.pl file if you have changed it manually whilst
-the cluster is running.
-<P>
-<H2><A NAME="ss9.52">9.52 load/cmd_cache (9)</A>
-</H2>
-
-<P><CODE><B>load/cmd_cache</B> Reload the automatic command cache</CODE>
-<P>
-<P>Normally, if you change a command file in the cmd or local_cmd tree it will
-automatially be picked up by the cluster program. Sometimes it can get confused
-if you are doing a lot of moving commands about or delete a command in the
-local_cmd tree and want to use the normal one again. Execute this command to
-reset everything back to the state it was just after a cluster restart.
-<P>
-<H2><A NAME="ss9.53">9.53 load/forward (9)</A>
-</H2>
-
-<P><CODE><B>load/forward</B> Reload the msg forwarding routing table</CODE>
-<P>Reload the /spider/msg/forward.pl file if you have changed it
-manually whilst the cluster is running.
-<P>
-<H2><A NAME="ss9.54">9.54 load/messages (9)</A>
-</H2>
-
-<P><CODE><B>load/messages</B> Reload the system messages file</CODE>
-<P>
-<P>If you change the /spider/perl/Messages file (usually whilst fiddling/writing ne
-commands) you can have them take effect during a cluster session by executing this
-command. You need to do this if get something like :-
-<P>unknown message 'xxxx' in lang 'en'
-<P>
-<H2><A NAME="ss9.55">9.55 load/prefixes (9)</A>
-</H2>
-
-<P><CODE><B>load/prefixes</B> Reload the prefix table</CODE>
-<P>
-<P>Reload the /spider/data/prefix_data.pl file if you have changed it manually
-whilst the cluster is running.
-<P>
-<H2><A NAME="ss9.56">9.56 merge (5)</A>
-</H2>
-
-<P><CODE><B>merge <node> [<no spots>/<no wwv>]</B> Ask for the latest spots and WWV</CODE>
-<P>
-<P>MERGE allows you to bring your spot and wwv database up to date. By default
-it will request the last 10 spots and 5 WWVs from the node you select. The
-node must be connected locally.
-<P>You can request any number of spots or wwv and although they will be appended
-to your databases they will not duplicate any that have recently been added
-(the last 2 days for spots and last month for WWV data).
-<P>
-<H2><A NAME="ss9.57">9.57 msg (9)</A>
-</H2>
-
-<P><CODE><B>msg <cmd> <msgno> [data ...]</B> Alter various message parameters</CODE>
-<P>
-<P>Alter message parameters like To, From, Subject, whether private or bulletin
-or return receipt (RR) is required or whether to keep this message from timing
-out.
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
- MSG TO <msgno> <call> - change TO callsign to <call>
- MSG FRom <msgno> <call> - change FROM callsign to <call>
- MSG PRrivate <msgno> - set private flag
- MSG NOPRrivate <msgno> - unset private flag
- MSG RR <msgno> - set RR flag
- MSG NORR <msgno> - unset RR flag
- MSG KEep <msgno> - set the keep flag (message won't be deleted ever)
- MSG NOKEep <msgno> - unset the keep flag
- MSG SUbject <msgno> <new> - change the subject to <new>
- MSG WAittime <msgno> - remove any waitting time for this message
- MSG NOREad <msgno> - mark message as unread
- MSG REad <msgno> - mark message as read
- MSG QUeue - queue any outstanding bulletins
- MSG QUeue 1 - queue any outstanding private messages
-</PRE>
-</CODE></BLOCKQUOTE>
-<P>You can look at the status of a message by using:-
-<P>STAT/MSG <msgno>
-<P>This will display more information on the message than DIR does.
-<P>
-<H2><A NAME="ss9.58">9.58 pc (8)</A>
-</H2>
-
-<P><CODE><B>pc <call> <text></B> Send text (eg PC Protocol) to <call></CODE>
-<P>
-<P>Send some arbitrary text to a locally connected callsign. No processing is done on
-the text. This command allows you to send PC Protocol to unstick things if problems
-arise (messages get stuck etc). eg:-
-<P>pc gb7djk PC33^GB7TLH^GB7DJK^400^
-<P>You can also use in the same way as a talk command to a connected user but
-without any processing, added of "from <blah> to <blah>" or whatever.
-<P>pc G1TLH Try doing that properly!!!
-<P>
-<H2><A NAME="ss9.59">9.59 ping (1)</A>
-</H2>
-
-<P><CODE><B>ping <node></B> Check the link quality between nodes</CODE>
-<P>
-<P>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.
-<P>
-<P>
-<H2><A NAME="ss9.60">9.60 rcmd (1)</A>
-</H2>
-
-<P><CODE><B>rcmd <node call> <cmd></B> Send a command to another DX cluster</CODE>
-<P>
-<P>This command allows you to send nearly any command to another DX Cluster
-node that is connected to the system.
-<P>Whether you get any output is dependant on a) whether the other system knows
-that the node callsign of this cluster is in fact a node b) whether the
-other system is allowing RCMDs from this node and c) whether you have
-permission to send this command at all.
-<P>
-<H2><A NAME="ss9.61">9.61 read (0)</A>
-</H2>
-
-<P><CODE><B>read</B> Read the next unread personal message addressed to you<BR>
-<B>read <msgno></B> Read the specified message<BR></CODE>
-<P>
-<P>You can read any messages that are sent as 'non-personal' and also any
-message either sent by or sent to your callsign.
-<P>
-<P>
-<H2><A NAME="ss9.62">9.62 read (extended for sysops) (5) </A>
-</H2>
-
-<P><CODE><B>read <msgno></B> Read a message on the system</CODE>
-<P>
-<P>As a sysop you may read any message on the system
-<P>
-<H2><A NAME="ss9.63">9.63 reject/announce</A>
-</H2>
-
-<P><CODE><B>reject/announce [0-9] <pattern></B> Set a reject filter
-for announce</CODE>
-<P>
-<P>Create an 'reject this announce' line for a filter.
-<P>An reject filter line means that if the announce matches this filter it is
-passed onto the user. See HELP FILTERS for more info. Please read this
-to understand how filters work - it will save a lot of grief later on.
-<P>You can use any of the following things in this line:-
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
- info <string> eg: iota or qsl
- by <prefixes> eg: G,M,2
- origin <prefixes>
- origin_dxcc <numbers> eg: 61,62 (from eg: sh/pre G)
- origin_itu <numbers>
- origin_zone <numbers>
- by_dxcc <numbers>
- by_itu <numbers>
- by_zone <numbers>
- channel <prefixes>
- wx 1 filter WX announces
- dest <prefixes> eg: 6MUK,WDX (distros)
-</PRE>
-</CODE></BLOCKQUOTE>
-<P>some examples:-
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
- rej/ann by_zone 14,15,16 and not by G,M,2
-</PRE>
-</CODE></BLOCKQUOTE>
-<P>You can use the tag 'all' to reject everything eg:
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
- rej/ann all
-</PRE>
-</CODE></BLOCKQUOTE>
-<P>but this probably for advanced users...
-<P>
-<H2><A NAME="ss9.64">9.64 reject/announce (extended for sysops) (8)</A>
-</H2>
-
-<P><CODE><B>reject/announce <call> [input] [0-9] <pattern></B> Announce filter sysop version</CODE>
-<P>
-<P>This version allows a sysop to set a filter for a callsign as well as the
-default for nodes and users eg:-
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
- reject/ann by G,M,2
- reject/ann input node_default by G,M,2
- reject/ann user_default by G,M,2
-</PRE>
-</CODE></BLOCKQUOTE>
-<P>
-<H2><A NAME="ss9.65">9.65 reject/route (8)</A>
-</H2>
-
-<P><CODE><B>reject/route <call> [0-9] <pattern></B> Set an 'reject' filter line for routing</CODE>
-<P>
-<P>Create an 'reject this routing PC Protocol' line for a filter.
-<P>
-<P>An reject filter line means that if a PC16/17/19/21/24/41/50 matches this filter
-it is NOT passed thru that interface. See HELP FILTERING for more info. Please
-read this to understand how filters work - it will save a lot of grief later on.
-You can use any of the following things in this line:-
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
- call <prefixes> the callsign of the thingy
- call_dxcc <numbers> eg: 61,62 (from eg: sh/pre G)
- call_itu <numbers>
- call_zone <numbers>
- origin <prefixes> really the interface it came in on
- origin_dxcc <numbers> eg: 61,62 (from eg: sh/pre G)
- origin_itu <numbers>
- origin_zone <numbers>
-</PRE>
-</CODE></BLOCKQUOTE>
-<P>
-<P>some examples:-
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
- rej/route gb7djk call_dxcc 61,38 (everything except UK+EIRE nodes)
-</PRE>
-</CODE></BLOCKQUOTE>
-<P>
-<P>You can use the tag 'all' to reject everything eg:
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
- rej/route all (equiv to [very] restricted mode)
-</PRE>
-</CODE></BLOCKQUOTE>
-<P>
-<H2><A NAME="ss9.66">9.66 reject/spots (0)</A>
-</H2>
-
-<P><CODE><B>reject/spots [0-9] <pattern></B> Set a reject filter line for spots</CODE>
-<P>
-<P>Create a 'reject this spot' line for a filter.
-<P>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>You can use any of the following things in this line:-
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
- freq <range> eg: 0/30000 or hf or hf/cw or 6m,4m,2m
- on <range> same as 'freq'
- call <prefixes> eg: G,PA,HB9
- info <string> eg: iota or qsl
- by <prefixes>
- call_dxcc <numbers> eg: 61,62 (from eg: sh/pre G)
- call_itu <numbers>
- call_zone <numbers>
- by_dxcc <numbers>
- by_itu <numbers>
- by_zone <numbers>
- origin <prefixes>
- channel <prefixes>
-</PRE>
-</CODE></BLOCKQUOTE>
-<P>For frequencies, you can use any of the band names defined in
-SHOW/BANDS and you can use a subband name like: cw, rtty, data, ssb -
-thus: hf/ssb. You can also just have a simple range like: 0/30000 -
-this is more efficient than saying simply: on HF (but don't get
-too hung up about that)
-<P>some examples:-
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
- rej/spot 1 on hf
- rej/spot 2 on vhf and not (by_zone 14,15,16 or call_zone 14,15,16)
-</PRE>
-</CODE></BLOCKQUOTE>
-<P>You can use the tag 'all' to reject everything eg:
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
- rej/spot 3 all
-</PRE>
-</CODE></BLOCKQUOTE>
-<P>but this probably for advanced users...
-<P>
-<H2><A NAME="ss9.67">9.67 reject/spots (extended for sysops) (8)</A>
-</H2>
-
-<P><CODE><B>reject/spots <call> [input] [0-9] <pattern></B>
-Reject spot filter sysop version </CODE>
-<P>
-<P>This version allows a sysop to set a filter for a callsign as well as the
-default for nodes and users eg:-
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
- reject/spot db0sue-7 1 by_zone 14,15,16
- reject/spot node_default all
- set/hops node_default 10
-
- reject/spot user_default by G,M,2
-</PRE>
-</CODE></BLOCKQUOTE>
-<P>
-<H2><A NAME="ss9.68">9.68 reject/wcy (0)</A>
-</H2>
-
-<P><CODE><B>reject/wcy [0-9] <pattern></B> Set a reject WCY filter</CODE>
-<P>
-<P>It is unlikely that you will want to do this, but if you do then you can
-filter on the following fields:-
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
- by <prefixes> eg: G,M,2
- origin <prefixes>
- origin_dxcc <numbers> eg: 61,62 (from eg: sh/pre G)
- origin_itu <numbers>
- origin_zone <numbers>
- by_dxcc <numbers>
- by_itu <numbers>
- by_zone <numbers>
- channel <prefixes>
-</PRE>
-</CODE></BLOCKQUOTE>
-<P>There are no examples because WCY Broadcasts only come from one place and
-you either want them or not (see UNSET/WCY if you don't want them).
-<P>This command is really provided for future use.
-<P>See HELP FILTER for information.
-<P>
-<H2><A NAME="ss9.69">9.69 reject/wcy (extended for sysops) (8)</A>
-</H2>
-
-<P><CODE><B>reject/wcy <call> [input] [0-9] <pattern></B>
-WCY reject filter sysop version</CODE>
-<P>
-<P>This version allows a sysop to set a filter for a callsign as well as the
-default for nodes and users eg:-
-<P>reject/wcy gb7djk all
-<P>
-<H2><A NAME="ss9.70">9.70 reject/wwv (0)</A>
-</H2>
-
-<P><CODE><B>reject/wwv [0-9] <pattern></B> Set a reject WWV filter</CODE>
-<P>
-<P>It is unlikely that you will want to do this, but if you do then you can
-filter on the following fields:-
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
- by <prefixes> eg: G,M,2
- origin <prefixes>
- origin_dxcc <numbers> eg: 61,62 (from eg: sh/pre G)
- origin_itu <numbers>
- origin_zone <numbers>
- by_dxcc <numbers>
- by_itu <numbers>
- by_zone <numbers>
- channel <prefixes>
-</PRE>
-</CODE></BLOCKQUOTE>
-<P>for example
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
- reject/wwv by_zone 14,15,16
-</PRE>
-</CODE></BLOCKQUOTE>
-<P>is probably the only useful thing to do (which will only show WWV broadcasts
-by stations in the US).
-<P>See HELP FILTER for information.
-<P>
-<H2><A NAME="ss9.71">9.71 reject/wwv (extended for sysops) (8)</A>
-</H2>
-
-<P><CODE><B>reject/wwv <call> [input] [0-9] <pattern></B>
-WWV reject filter sysop version</CODE>
-<P>
-<P>This version allows a sysop to set a filter for a callsign as well as the
-default for nodes and users eg:-
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
- reject/wwv db0sue-7 1 by_zone 4
- reject/wwv node_default all
-
- reject/wwv user_default by W
-</PRE>
-</CODE></BLOCKQUOTE>
-<P>
-<H2><A NAME="ss9.72">9.72 reply (0)</A>
-</H2>
-
-<P><CODE><B>reply</B> Reply (privately) to the last message that you have read<BR>
-<B>reply <msgno></B> Reply (privately) to the specified message<BR>
-<B>reply B <msgno></B> Reply as a Bulletin to the specified message<BR>
-<B>reply NOPrivate <msgno></B> Reply as a Bulletin to the specified
-message<BR>
-<B>reply RR <msgno></B> Reply to the specified message with read receipt<BR></CODE>
-<P>
-<P>You can reply to a message and the subject will automatically have
-"Re:" inserted in front of it, if it isn't already present.
-<P>You can also use all the extra qualifiers such as RR, PRIVATE,
-NOPRIVATE, B that you can use with the SEND command (see SEND
-for further details)
-<P>
-<H2><A NAME="ss9.73">9.73 send (0)</A>
-</H2>
-
-<P><CODE><B>send <call> [<call> ...]</B> Send a message to one or more callsigns<BR>
-<B>send RR <call></B> Send a message and ask for a read receipt<BR>
-<B>send COPY <msgno> <call></B> Send a copy of a message to someone<BR>
-<B>send PRIVATE <call></B> Send a personal message<BR>
-<B>send NOPRIVATE <call></B> Send a message to all stations<BR></CODE>
-<P>
-<P>All the SEND commands will create a message which will be sent either to
-an individual callsign or to one of the 'bulletin' addresses.
-<P>SEND <call> on its own acts as though you had typed SEND PRIVATE, that is
-it will mark the message as personal and send it to the cluster node that
-that callsign is connected to.
-<P>You can have more than one callsign in all of the SEND commands.
-<P>You can have multiple qualifiers so that you can have for example:-
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
- SEND RR COPY 123 PRIVATE G1TLH G0RDI
-</PRE>
-</CODE></BLOCKQUOTE>
-<P>which should send a copy of message 123 to G1TLH and G0RDI and you will
-receive a read receipt when they have read the message.
-<P>SB is an alias for SEND NOPRIVATE (or send a bulletin in BBS speak)
-SP is an alias for SEND PRIVATE
-<P>
-<H2><A NAME="ss9.74">9.74 set/address (0)</A>
-</H2>
-
-<P><CODE><B>set/address <your_address></B> Record your postal address</CODE>
-<P>
-<P>Literally, record your address details on the cluster.
-<P>
-<H2><A NAME="ss9.75">9.75 set/announce (0)</A>
-</H2>
-
-<P><CODE><B>set/announce</B> Allow announce messages</CODE>
-<P>
-<P>Allow announce messages to arrive at your terminal.
-<P>
-<H2><A NAME="ss9.76">9.76 set/arcluster (5)</A>
-</H2>
-
-<P><CODE><B>set/arcluster <node_call> [<node_call> ...]</B> Make
-the node_call an AR-Cluster type node</CODE>
-<P>
-<P>Set the node_call as an AR-Cluster type node
-<P>
-<H2><A NAME="ss9.77">9.77 set/baddx (8)</A>
-</H2>
-
-<P><CODE><B>set/baddx <call></B> Stop words we do not wish to see in the callsign field
-of a dx spot being propagated</CODE>
-<P>
-<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.
-<P>The word must be wriiten in full, no wild cards are allowed eg:-
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
- set/baddx FORSALE VIDEO FR0G
-</PRE>
-</CODE></BLOCKQUOTE>
-<P>To allow a word again, use the following command ...
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
- unset/baddx VIDEO
-</PRE>
-</CODE></BLOCKQUOTE>
-<P>
-<H2><A NAME="ss9.78">9.78 set/badnode (6)</A>
-</H2>
-
-<P><CODE><B>set/badnode <node_call></B> Stop spots from this node_call
-being propagated</CODE>
-<P>
-<P>Setting a callsign as a 'badnode' will prevent spots from that node
-going any further. They will not be displayed and they will not be
-sent onto other nodes.
-<P>The call can be a full or partial call (or a prefix), eg:-
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
- set/badnode K1TTT
-</PRE>
-</CODE></BLOCKQUOTE>
-<P>will stop anything from K1TTT (including any SSID's)
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
- unset/badnode K1TTT
-</PRE>
-</CODE></BLOCKQUOTE>
-<P>will allow spots from him again.
-<P>Use with extreme care. This command may well be superceded by FILTERing.
-<P>
-<H2><A NAME="ss9.79">9.79 set/badspotter (8)</A>
-</H2>
-
-<P><CODE><B>set/badspotter <call></B> Stop spots from this callsign being propagated</CODE>
-<P>
-<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.
-<P>The call must be written in full, no wild cards are allowed eg:-
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
- set/badspotter VE2STN
-</PRE>
-</CODE></BLOCKQUOTE>
-<P>will stop anything from VE2STN. If you want SSIDs as well then you must
-enter them specifically.
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
- unset/badspotter VE2STN
-</PRE>
-</CODE></BLOCKQUOTE>
-<P>will allow spots from him again.
-<P>Use with extreme care. This command may well be superceded by FILTERing.
-<P>
-<H2><A NAME="ss9.80">9.80 set/badword (8)</A>
-</H2>
-
-<P><CODE><B>set/badword <word></B> Stop things with this word being propogated</CODE>
-<P>
-<P>Setting a word as a 'badword' will prevent things like spots,
-announces or talks with this word in the the text part from going any
-further. They will not be displayed and they will not be sent onto
-other nodes.
-<P>The word must be written in full, no wild cards are allowed eg:-
-<P>set/badword annihilate annihilated annihilation
-<P>will stop anything with these words in the text.
-<P>unset/badword annihilated
-<P>will allow text with this word again.
-<P>
-<P>
-<H2><A NAME="ss9.81">9.81 set/beep (0)</A>
-</H2>
-
-<P><CODE><B>set/beep</B> Add beeps to terminal messages</CODE>
-<P>
-<P>Add a beep to DX and other terminal messages.
-<P>
-<H2><A NAME="ss9.82">9.82 set/bbs (5)</A>
-</H2>
-
-<P><CODE><B>set/bbs <call> [<call>..]</B>Make <call> a BBS</CODE>
-<P>
-<H2><A NAME="ss9.83">9.83 set/clx (5)</A>
-</H2>
-
-<P><CODE><B>set/clx <node_call> [<node_call> ...]</B> Make
-the node_call a CLX type node</CODE>
-<P>
-<P>Set the node_call as a CLX type node
-<P>
-<H2><A NAME="ss9.84">9.84 set/debug (9)</A>
-</H2>
-
-<P><CODE><B>set/debug <name></B> Add a debug level to the debug set</CODE>
-<P>
-<P>You can choose to log several different levels. The levels are
-<P>chan
-state
-msg
-cron
-connect
-<P>You can show what levels you are logging with the <EM>show/debug</EM>
-command.
-<P>You can remove a debug level with unset/debug <name>
-<P>
-<H2><A NAME="ss9.85">9.85 set/dx (0)</A>
-</H2>
-
-<P><CODE><B>set/dx</B>Allow DX messages to arrive at your terminal</CODE>
-<P>
-<P>You can stop DX messages with the <EM>unset/dx</EM> command
-<P>
-<H2><A NAME="ss9.86">9.86 set/dxgrid (0)</A>
-</H2>
-
-<P><CODE><B>set/dxgrid</B>Allow grid squares on the end of DX messages</CODE>
-<P>
-<P>Some logging programs do not like the additional information at
-the end of a DX spot. If this is the case, use the <EM>unset/dxgrid</EM>
-command to remove the grid squares.
-<P>
-<H2><A NAME="ss9.87">9.87 set/dxnet (5)</A>
-</H2>
-
-<P><CODE><B>set/dxnet <node_call> [<node_call> ...]</B> Make
-the node_call a DXNet type node</CODE>
-<P>
-<P>Set the node_call as a DXNet type node
-<P>
-<H2><A NAME="ss9.88">9.88 set/echo (0)</A>
-</H2>
-
-<P><CODE><B>set/echo</B> Make the cluster echo your input</CODE>
-<P>
-<P>If you are connected via a telnet session, different implimentations
-of telnet handle echo differently depending on whether you are
-connected via port 23 or some other port. You can use this command
-to change the setting appropriately.
-<P>You can remove the echo with the <EM>unset/echo</EM> command
-<P>The setting is stored in your user profile.
-<P>YOU DO NOT NEED TO USE THIS COMMAND IF YOU ARE CONNECTED VIA AX25.
-<P>
-<H2><A NAME="ss9.89">9.89 set/email (0)</A>
-</H2>
-
-<P><CODE><B>set/email <email_address></B> Set email address(es) and forward your personals</CODE>
-<P>
-<P>If any personal messages come in for your callsign then you can use
-these commands to control whether they are forwarded onto your email
-address. To enable the forwarding do something like:-
-<P>SET/EMAIL mike.tubby@somewhere.com
-<P>You can have more than one email address (each one separated by a space).
-Emails are forwarded to all the email addresses you specify.
-<P>You can disable forwarding by:-
-<P>UNSET/EMAIL
-<P>
-<H2><A NAME="ss9.90">9.90 set/here (0)</A>
-</H2>
-
-<P><CODE><B>set/here</B> Set the here flag</CODE>
-<P>
-<P>Let others on the cluster know you are here by only displaying your
-callsign. If you are away from your terminal you can use the <EM>unset/here</EM>
-command to let people know you are away. This simply puts brackets
-around your callsign to indicate you are not available.
-<P>
-<H2><A NAME="ss9.91">9.91 set/homenode (0)</A>
-</H2>
-
-<P><CODE><B>set/homenode <node_call></B> Set your home cluster</CODE>
-<P>
-<P>Tell the cluster system where you normally connect to. Any Messages sent
-to you will normally find their way there should you not be connected.
-eg:-
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
- SET/HOMENODE gb7djk
-</PRE>
-</CODE></BLOCKQUOTE>
-<P>
-<H2><A NAME="ss9.92">9.92 set/hops (8)</A>
-</H2>
-
-<P><CODE><B>set/hops <node_call> ann|spots|wwv|wcy <n></B>
-Set hop count</CODE>
-<P>
-<P>Set the hop count for a particular type of broadcast for a node.
-<P>This command allows you to set up special hop counts for a node
-for currently: announce, spots, wwv and wcy broadcasts.
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
-eg:
- set/hops gb7djk ann 10
- set/hops gb7mbc spots 20
-</PRE>
-</CODE></BLOCKQUOTE>
-<P>Set SHOW/HOPS for information on what is already set. This command
-creates a filter and works in conjunction with the filter system.
-<P>
-<H2><A NAME="ss9.93">9.93 set/isolate (9)</A>
-</H2>
-
-<P><CODE><B>set/isolate <node call></B> Isolate a node from the rest of the network</CODE>
-<P>
-<P>Connect a node to your system in such a way that you are a full protocol
-member of its network and can see all spots on it, but nothing either leaks
-out from it nor goes back into from the rest of the nodes connected to you.
-<P>You can potentially connect several nodes in this way.
-<P>You can see which nodes are isolated with the show/isolate (1) command.
-<P>You can remove the isolation with the command unset/isolate.
-<P>
-<H2><A NAME="ss9.94">9.94 set/language (0)</A>
-</H2>
-
-<P><CODE><B>set/language <language></B> Set the language you wish to use</CODE>
-<P>
-<P>You can select the language that you want the cluster to use. Currently
-the languages available are <EM>en</EM> (English) and <EM>nl</EM> (Dutch).
-<P>
-<H2><A NAME="ss9.95">9.95 set/location (0)</A>
-</H2>
-
-<P><CODE><B>set/location <lat and long></B> Set your latitude and longitude</CODE>
-<P>
-<P>You can set your latitude and longitude manually or alternatively use the
-<EM>set/qra</EM> command which will do the conversion for you.
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
- set/location 54 04 N 2 02 E
-</PRE>
-</CODE></BLOCKQUOTE>
-<P>
-<P>
-<H2><A NAME="ss9.96">9.96 set/sys_location (9)</A>
-</H2>
-
-<P><CODE><B>set/sys_location <lat & long></B> Set your cluster latitude and longitude</CODE>
-<P>
-<P>In order to get accurate headings and such like you must tell the system
-what your latitude and longitude is. If you have not yet done a SET/QRA
-then this command will set your QRA locator for you. For example:-
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
- SET/LOCATION 52 22 N 0 57 E
-</PRE>
-</CODE></BLOCKQUOTE>
-<P>
-<H2><A NAME="ss9.97">9.97 set/logininfo (0)</A>
-</H2>
-
-<P><CODE><B>set/logininfo</B> Show logins and logouts of nodes and users</CODE>
-<P>
-<P>Show users and nodes when they log in and out of the local cluster. You
-can stop these messages by using the <EM>unset/logininfo</EM> command.
-<P>
-<P>
-<H2><A NAME="ss9.98">9.98 set/lockout (9)</A>
-</H2>
-
-<P><CODE><B>set/lockout <call></B> Stop a callsign connecting to the cluster</CODE>
-<P>
-<P>You can show who is locked out with the <EM>show/lockout</EM> command.
-To allow the user to connect again, use the <EM>unset/lockout</EM> command.
-<P>
-<H2><A NAME="ss9.99">9.99 set/name (0)</A>
-</H2>
-
-<P><CODE><B>set/name <your_name></B> Set your name</CODE>
-<P>
-<P>Tell the cluster what your name is, eg:-
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
- set/name Dirk
-</PRE>
-</CODE></BLOCKQUOTE>
-<P>
-<H2><A NAME="ss9.100">9.100 set/node (9)</A>
-</H2>
-
-<P><CODE><B>set/node <call> [<call> ...]</B> Make the callsign an AK1A cluster</CODE>
-<P>
-<P>Tell the system that the call(s) are to be treated as AK1A cluster and
-fed PC Protocol rather normal user commands.
-<P>From version 1.41 you can also set the following types of cluster
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
- set/spider
- set/dxnet
- set/clx
- set/arcluster
-</PRE>
-</CODE></BLOCKQUOTE>
-<P>To see what your nodes are set to, use the <EM>show/nodes</EM> command.
-<P>
-<H2><A NAME="ss9.101">9.101 set/obscount (9)</A>
-</H2>
-
-<P><CODE><B>set/obscount <count> <node call></B> Set the 'pump-up' obsolescence counter</CODE>
-<P>
-<P>From version 1.35 onwards neighbouring nodes are pinged at regular intervals (see
-SET/PINGINTERVAL), usually 300 seconds or 5 minutes. There is a 'pump-up'
-counter which is decremented on every outgoing ping and then reset to
-the 'obscount' value on every incoming ping. The default value of this
-parameter is 2.
-<P>What this means is that a neighbouring node will be pinged twice at
-(default) 300 second intervals and if no reply has been heard just before
-what would be the third attempt, that node is disconnected.
-<P>If a ping is heard then the obscount is reset to the full value. Using
-default values, if a node has not responded to a ping within 15 minutes,
-it is disconnected.
-<P>
-<H2><A NAME="ss9.102">9.102 set/page (0)</A>
-</H2>
-
-<P><CODE><B>set/page <n></B> Set the number of lines per page</CODE>
-<P>
-<P>Tell the system how many lines you wish on a page when the number of lines
-of output from a command is more than this. The default is 20. Setting it
-explicitly to 0 will disable paging.
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
- SET/PAGE 30
- SET/PAGE 0
-</PRE>
-</CODE></BLOCKQUOTE>
-<P>The setting is stored in your user profile.
-<P>
-<H2><A NAME="ss9.103">9.103 set/password (0)</A>
-</H2>
-
-<P><CODE><B>set/password</B> Set your own password</CODE>
-<P>
-<P>This command only works for a 'telnet' user (currently). It will
-only work if you have a password already set. This initial password
-can only be set by the sysop.
-<P>When you execute this command it will ask you for your old password,
-then ask you to type in your new password twice (to make sure you
-get it right). You may or may not see the data echoed on the screen
-as you type, depending on the type of telnet client you have.
-<P>
-<H2><A NAME="ss9.104">9.104 set/password (9)</A>
-</H2>
-
-<P><CODE><B>set/password <callsign> <string></B> Set a users password</CODE>
-<P>
-<P>The password for a user can only be set by a full sysop. The string
-can contain any characters.
-<P>The way this field is used depends on context. If it is being used in
-the SYSOP command context then you are offered 5 random numbers and you
-have to supply the corresponding letters. This is now mainly for ax25
-connections.
-<P>If it is being used on incoming telnet connections then, if a password
-is set or the:
-<P>set/var $main::passwdreq = 1
-<P>command is executed in the startup script, then a password prompt is
-given after the normal 'login: ' prompt.
-<P>The command "unset/password" is provided to allow a sysop to remove a
-users password completely in case a user forgets or loses their password.
-<P>
-<H2><A NAME="ss9.105">9.105 set/pinginterval (9)</A>
-</H2>
-
-<P><CODE><B>set/pinginterval <time> <node call></B> Set the ping time to neighbouring nodes</CODE>
-<P>
-<P>As from version 1.35 all neighbouring nodes are pinged at regular intervals
-in order to determine the rolling quality of the link and, in future, to
-affect routing decisions. The default interval is 300 secs or 5 minutes.
-<P>You can use this command to set a different interval. Please don't.
-<P>But if you do the value you enter is treated as minutes up 60 and seconds
-for numbers greater than that.
-<P>This is used also to help determine when a link is down at the far end
-(as certain cluster software doesn't always notice), see SET/OBSCOUNT
-for more information.
-<P>
-<H2><A NAME="ss9.106">9.106 set/privilege (9)</A>
-</H2>
-
-<P><CODE><B>set/privilege <n> <call> [<call> ...]</B> Set the privilege level on a call</CODE>
-<P>
-<P>Set the privilege level on a callsign. The privilege levels that pertain
-to commands are as default:-
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
- 0 - normal user
- 1 - allow remote nodes normal user RCMDs
- 5 - various privileged commands (including shutdown, but not disc-
- connect), the normal level for another node.
- 8 - more privileged commands (including disconnect)
- 9 - local sysop privilege. DO NOT SET ANY REMOTE USER OR NODE TO THIS
- LEVEL.
-</PRE>
-</CODE></BLOCKQUOTE>
-<P>If you are a sysop and you come in as a normal user on a remote connection
-your privilege will automatically be set to 0.
-<P>
-<H2><A NAME="ss9.107">9.107 set/spider (5)</A>
-</H2>
-
-<P><CODE><B>set/spider <node_call> [<node_call> ...]</B> Make
-the node_call a DXSpider type node</CODE>
-<P>
-<P>Set the node_call as a DXSpider type node
-<P>
-<H2><A NAME="ss9.108">9.108 set/sys_qra (9)</A>
-</H2>
-
-<P><CODE><B>set/sys_qra <locator></B> Set your cluster QRA locator</CODE>
-<P>
-<H2><A NAME="ss9.109">9.109 set/qra (0)</A>
-</H2>
-
-<P><CODE><B>set/qra <locator></B> Set your QRA locator</CODE>
-<P>
-<P>Tell the system what your QRA (or Maidenhead) locator is. If you have not
-done a SET/LOCATION then your latitude and longitude will be set roughly
-correctly (assuming your locator is correct ;-). For example:-
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
- SET/QRA JO02LQ
-</PRE>
-</CODE></BLOCKQUOTE>
-<P>
-<H2><A NAME="ss9.110">9.110 set/qth (0)</A>
-</H2>
-
-<P><CODE><B>set/qth <your QTH></B> Set your QTH</CODE>
-<P>
-<P>Tell the system where your are. For example:-
+<P>Please be aware that if you update your system using CVS, it is possible that
+you could be running code that is very beta and not fully tested. There is
+a possibility that it could be unstable.
<P>
-<BLOCKQUOTE><CODE>
-<PRE>
- set/qth East Dereham, Norfolk
-</PRE>
-</CODE></BLOCKQUOTE>
-<P>
-<H2><A NAME="ss9.111">9.111 set/register (9)</A>
-</H2>
-
-<P><CODE><B>set/register <call></B> Mark a user as registered</CODE>
-<P>
-<P>Registration is a concept that you can switch on by executing the
-<P>set/var $main::regreq = 1
-<P>command (usually in your startup file)
-<P>If a user is NOT registered then, firstly, instead of the normal
-motd file (/spider/data/motd) being sent to the user at startup, the
-user is sent the motd_nor file instead. Secondly, the non registered
-user only has READ-ONLY access to the node. The non-registered user
-cannot use DX, ANN etc.
-<P>The only exception to this is that a non-registered user can TALK or
-SEND messages to the sysop.
-<P>To unset a user use the 'unset/register' command
-<P>
-<H2><A NAME="ss9.112">9.112 set/talk (0)</A>
-</H2>
-
-<P><CODE><B>set/talk</B> Allow talk messages to be seen at your console</CODE>
-<P>
-<P>Allow talk messages to arrive at your console. You can switch off
-talks with the <EM>unset/talk</EM> command.
-<P>
-<H2><A NAME="ss9.113">9.113 set/wcy (0)</A>
-</H2>
-
-<P><CODE><B>set/wcy</B> Allow WCY messages to be seen at your console</CODE>
-<P>
-<P>Allow WCY information to be seen at your console. You can switch off
-WCY messages with the <EM>unset/wcy</EM> command.
-<P>
-<H2><A NAME="ss9.114">9.114 set/wwv (0)</A>
-</H2>
-
-<P><CODE><B>set/wwv</B> Allow WWV messages to be seen at your console</CODE>
-<P>
-<P>Allow WWV information to be seen at your console. You can switch off
-WWV messages with the <EM>unset/wwv</EM> command.
-<P>
-<H2><A NAME="ss9.115">9.115 set/wx (0)</A>
-</H2>
-
-<P><CODE><B>set/wx</B> Allow WX messages to be seen at your console</CODE>
-<P>
-<P>Allow WX information to be seen at your console. You can switch off
-WX messages with the <EM>unset/wx</EM> command.
-<P>
-<H2><A NAME="ss9.116">9.116 show/baddx (1)</A>
-</H2>
-
-<P><CODE><B>show/baddx</B>Show all the bad dx calls in the system</CODE>
-<P>
-<P>Display all the bad dx callsigns in the system, see SET/BADDX
-for more information.
-<P>
-<H2><A NAME="ss9.117">9.117 show/badnode (6)</A>
-</H2>
-
-<P><CODE><B>show/badnode</B> Show all the bad nodes in the system</CODE>
-<P>
-<P>Display all the bad node callsigns in the system, see SET/BADNODE
-for more information.
-<P>
-<H2><A NAME="ss9.118">9.118 show/badspotter (1)</A>
-</H2>
-
-<P><CODE><B>show/badspotter</B> Show all the bad spotters in the system</CODE>
-<P>
-<P>Display all the bad spotter's callsigns in the system, see SET/BADSPOTTER
-for more information.
-<P>
-<H2><A NAME="ss9.119">9.119 show/badword (1)</A>
-</H2>
-
-<P><CODE><B>show/badword</B> Show all the bad words in the system</CODE>
-<P>
-<P>Display all the bad words in the system, see SET/BADWORD
-for more information.
-<P>
-<H2><A NAME="ss9.120">9.120 show/configuration (0)</A>
-</H2>
-
-<P><CODE><B>show/configuration [<node>]</B> Show all visible nodes and their users</CODE>
-<P>
-<P>This command allows you to see all the users that can be seen
-and the nodes to which they are connected. With the optional <EM>node</EM>,
-you can specify a particular node to look at.
-<P>This command is normally abbreviated to: sh/c
-<P>BE WARNED: the list that is returned can be VERY long
-<P>
-<H2><A NAME="ss9.121">9.121 show/configuration/node (0)</A>
-</H2>
-
-<P><CODE><B>show/configuration/node</B> Show all the nodes connected</CODE>
-<P>
-<P>Show all the nodes connected locally and the nodes they have connected.
-<P>
-<H2><A NAME="ss9.122">9.122 show/connect (1)</A>
-</H2>
-
-<P><CODE><B>show/connect</B> Show all the active connections</CODE>
-<P>
-<P>This command shows information on all the active connections known to
-the node. This command gives slightly more information than WHO.
-<P>
-<H2><A NAME="ss9.123">9.123 show/date (0)</A>
-</H2>
-
-<P><CODE><B>show/date [<prefix>|<callsign>]</B> Show
-the local time</CODE>
-<P>
-<P>This is very nearly the same as SHOW/TIME, the only difference the format
-of the date string if no arguments are given.
-<P>If no prefixes or callsigns are given then this command returns the local
-time and UTC as the computer has it right now. If you give some prefixes
-then it will show UTC and UTC + the local offset (not including DST) at
-the prefixes or callsigns that you specify.
-<P>
-<H2><A NAME="ss9.124">9.124 show/debug (9)</A>
-</H2>
-
-<P><CODE><B>show/debug</B> Show what levels of debug you are logging</CODE>
-<P>
-<P>The levels can be set with <EM>set/debug</EM>
-<P>
-<H2><A NAME="ss9.125">9.125 show/dx (0)</A>
-</H2>
-
-<P><CODE><B>show/dx [options]</B> interrogate the spot database</CODE>
-<P>
-<P>If you just type SHOW/DX you will get the last so many spots
-(sysop configurable, but usually 10).
-<P>In addition you can add any number of these options in very nearly
-any order to the basic SHOW/DX command, they are:-
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
-
-on <band> - eg 160m 20m 2m 23cm 6mm
-on <region> - eg hf vhf uhf shf (see SHOW/BANDS)
-
-<number> - the number of spots you want
-<from>-<to> - <from> spot no <to> spot no in
- the selected list
-
-<prefix> - for a spotted callsign beginning with <prefix>
-*<suffix> - for a spotted callsign ending in <suffix>
-*<string>* - for a spotted callsign containing <string>
-
-day <number> - starting <number> days ago
-day <from>-<to> - <from> days <to> days ago
-
-info <text> - any spots containing <text> in the info or remarks
-
-by <call> - any spots spotted by <call> (spotter <call>
- is the same).
-
-qsl - this automatically looks for any qsl info on the call
- held in the spot database.
-
-iota [<iota>] - If the iota island number is missing it will
- look for the string iota and anything which looks like
- an iota island number. If you specify then it will look
- for that island.
-
-qra [<locator>] - this will look for the specific locator if
- you specify one or else anything that looks like a locator.
-</PRE>
-</CODE></BLOCKQUOTE>
-<P>e.g.
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
-
- SH/DX 9m0
- SH/DX on 20m info iota
- SH/DX 9a on vhf day 30
- SH/DX rf1p qsl
- SH/DX iota
- SH/DX iota eu-064
- SH/DX qra jn86
-</PRE>
-</CODE></BLOCKQUOTE>
-<P>
-<H2><A NAME="ss9.126">9.126 show/dxcc (0)</A>
-</H2>
-
-<P><CODE><B>show/dxcc <prefix></B> Interrogate the spot database by country</CODE>
-<P>
-<P>This command takes the <prefix> (which can be a full or partial
-callsign if desired), looks up which internal country number it is
-and then displays all the spots as per SH/DX for that country.
-<P>The options for SHOW/DX also apply to this command.
-e.g.
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
-
- SH/DXCC G
- SH/DXCC W on 20m info iota
-</PRE>
-</CODE></BLOCKQUOTE>
-<P>
-<H2><A NAME="ss9.127">9.127 sh/dxstats (0)</A>
-</H2>
-
-<P><CODE><B>sh/dxstats</B> Show the DX Statistics for last 31 days</CODE>
-<P>
-<P>Show the total DX spots for the last 31 days
-<P>
-<P>
-<H2><A NAME="ss9.128">9.128 show/files (0)</A>
-</H2>
-
-<P><CODE><B>show/files [<filearea> [<string>]]</B> List
-the contents of a filearea</CODE>
-<P>
-<P>SHOW/FILES on its own will show you a list of the various fileareas
-available on the system. To see the contents of a particular file
-area type:-
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
- SH/FILES <filearea>
-</PRE>
-</CODE></BLOCKQUOTE>
-<P>where <filearea> is the name of the filearea you want to see the
-contents of.
-<P>You can also use shell globbing characters like '*' and '?' in a
-string to see a selection of files in a filearea eg:-
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
- SH/FILES bulletins arld*
-</PRE>
-</CODE></BLOCKQUOTE>
-<P>See also TYPE - to see the contents of a file.
-<P>
-<H2><A NAME="ss9.129">9.129 show/filter (0)</A>
-</H2>
-
-<P><CODE><B>show/filter</B> Show the filters you have set</CODE>
-<P>
-<P>Show the contents of all the filters that are set by you. This command
-displays all the filters set - for all the various categories.
-<P>
-<H2><A NAME="ss9.130">9.130 show/filter (extended for sysops) (5)</A>
-</H2>
-
-<P><CODE><B>show/filter <callsign></B> Show the filters set by <callsign></CODE>
-<P>
-<P>A sysop can look at any filters that have been set.
-<P>
-<H2><A NAME="ss9.131">9.131 show/hfstats (0)</A>
-</H2>
-
-<P><CODE><B>show/hfstats</B> Show the HF DX Statistics for last 31 days</CODE>
-<P>
-<P>Show the HF DX spots breakdown by band for the last 31 days
-<P>
-<H2><A NAME="ss9.132">9.132 show/hftable (0)</A>
-</H2>
-
-<P><CODE><B>show/hftable</B> Show the HF DX Spotter Table for your country</CODE>
-<P>
-<P>Show the HF DX Spotter table for your country for the last 31 days
-<P>
-<H2><A NAME="ss9.133">9.133 show/hops (8)</A>
-</H2>
-
-<P><CODE><B>show/hops <node_call> [ann|spots|wcy|wwv|]</B> Show the hop counts for a node</CODE>
-<P>
-<P>This command shows the hop counts set up for a node. You can specify
-which category you want to see. If you leave the category out then
-all the categories will be listed.
-<P>
-<H2><A NAME="ss9.134">9.134 show/isolate (1)</A>
-</H2>
-
-<P><CODE><B>show/isolate</B> Show a list of isolated nodes</CODE>
-<P>
-<P>Show which nodes are currently set to be isolated.
-<P>
-<H2><A NAME="ss9.135">9.135 show/lockout (9)</A>
-</H2>
-
-<P><CODE><B>show/lockout</B> Show a list of excluded callsigns</CODE>
-<P>
-<P>Show a list of callsigns that have been excluded (locked out) of the
-cluster locally with the <EM>set/lockout</EM> command
-<P>
-<H2><A NAME="ss9.136">9.136 show/log (8)</A>
-</H2>
-
-<P><CODE><B>show/log [<callsign>]</B> Show excerpts from the system log</CODE>
-<P>
-<P>This command outputs a short section of the system log. On its own
-it will output a general logfile. With the optional callsign it will
-show output from the log associated with that callsign.
-<P>
-<H2><A NAME="ss9.137">9.137 show/moon (0)</A>
-</H2>
-
-<P><CODE><B>show/moon [<prefix>|<callsign>]</B> Show moon
-rise and set times</CODE>
-<P>
-<P>Show the Moon rise and set times for a (list of) prefixes or callsigns,
-together with the azimuth and elevation of the sun currently at those
-locations.
-<P>If you don't specify any prefixes or callsigns, it will show the times for
-your QTH (assuming you have set it with either SET/LOCATION or SET/QRA),
-together with the current azimuth and elevation.
-<P>In addition, it will show the gain or loss dB relative to the nominal
-distance of 385,000Km due to the ellipsoidal nature of the orbit.
-<P>If all else fails it will show the Moonrise and set times for the node
-that you are connected to.
-<P>For example:-
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
- SH/MOON
- SH/MOON G1TLH W5UN
-</PRE>
-</CODE></BLOCKQUOTE>
-<P>
-<H2><A NAME="ss9.138">9.138 show/muf (0)</A>
-</H2>
-
-<P><CODE><B>show/muf <prefix> [<hours>][long]</B> Show
-the likely propagation to <prefix></CODE>
-<P>
-<P>This command allow you to estimate the likelihood of you contacting
-a station with the prefix you have specified. The output assumes a modest
-power of 20dBW and receiver sensitivity of -123dBm (about 0.15muV/10dB SINAD)
-<P>The result predicts the most likely operating frequencies and signal
-levels for high frequency (shortwave) radio propagation paths on
-specified days of the year and hours of the day. It is most useful for
-paths between 250 km and 6000 km, but can be used with reduced accuracy
-for paths shorter or longer than this.
-<P>The command uses a routine MINIMUF 3.5 developed by the U.S. Navy and
-used to predict the MUF given the predicted flux, day of the year,
-hour of the day and geographic coordinates of the transmitter and
-receiver. This routine is reasonably accurate for the purposes here,
-with a claimed RMS error of 3.8 MHz, but much smaller and less complex
-than the programs used by major shortwave broadcasting organizations,
-such as the Voice of America.
-<P>The command will display some header information detailing its
-assumptions, together with the locations, latitude and longitudes and
-bearings. It will then show UTC (UT), local time at the other end
-(LT), calculate the MUFs, Sun zenith angle at the midpoint of the path
-(Zen) and the likely signal strengths. Then for each frequency for which
-the system thinks there is a likelihood of a circuit it prints a value.
-<P>The value is currently a likely S meter reading based on the conventional
-6dB / S point scale. If the value has a '+' appended it means that it is
-1/2 an S point stronger. If the value is preceeded by an 'm' it means that
-there is likely to be much fading and by an 's' that the signal is likely
-to be noisy.
-<P>By default SHOW/MUF will show the next two hours worth of data. You
-can specify anything up to 24 hours worth of data by appending the no of
-hours required after the prefix. For example:-
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
- SH/MUF W
-</PRE>
-</CODE></BLOCKQUOTE>
-<P>produces:
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
- RxSens: -123 dBM SFI: 159 R: 193 Month: 10 Day: 21
- Power : 20 dBW Distance: 6283 km Delay: 22.4 ms
- Location Lat / Long Azim
- East Dereham, Norfolk 52 41 N 0 57 E 47
- United-States-W 43 0 N 87 54 W 299
- UT LT MUF Zen 1.8 3.5 7.0 10.1 14.0 18.1 21.0 24.9 28.0 50.0
- 18 23 11.5 -35 mS0+ mS2 S3
- 19 0 11.2 -41 mS0+ mS2 S3
-</PRE>
-</CODE></BLOCKQUOTE>
-<P>indicating that you will have weak, fading circuits on top band and
-80m but usable signals on 40m (about S3).
-<P>inputting:-
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
- SH/MUF W 24
-</PRE>
-</CODE></BLOCKQUOTE>
-<P>will get you the above display, but with the next 24 hours worth of
-propagation data.
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
- SH/MUF W L 24
- SH/MUF W 24 Long
-</PRE>
-</CODE></BLOCKQUOTE>
-<P>Gives you an estimate of the long path propagation characterics. It
-should be noted that the figures will probably not be very useful, nor
-terrible accurate, but it is included for completeness.
-<P>
-<H2><A NAME="ss9.139">9.139 show/newconfiguration (0)</A>
-</H2>
-
-<P><CODE><B>show/newconfiguration [<node>]</B> Show all the nodes and users visible</CODE>
-<P>
-<P>This command allows you to see all the users that can be seen
-and the nodes to which they are connected.
-<P>This command produces essentially the same information as
-SHOW/CONFIGURATION except that it shows all the duplication of
-any routes that might be present It also uses a different format
-which may not take up quite as much space if you don't have any
-loops.
-<P>BE WARNED: the list that is returned can be VERY long
-<P>
-<H2><A NAME="ss9.140">9.140 show/newconfiguration/node (0)</A>
-</H2>
-
-<P><CODE><B>show/newconfiguration/node</B> Show all the nodes connected locally</CODE>
-<P>
-<P>Show all the nodes connected to this node in the new format.
-<P>
-<H2><A NAME="ss9.141">9.141 show/node (1)</A>
-</H2>
-
-<P><CODE><B>show/node [<node_call> ...]</B> Show the type and version
-number of nodes</CODE>
-<P>
-<P>Show the type and version (if connected) of the nodes specified on the
-command line. If no callsigns are specified then a sorted list of all
-the non-user callsigns known to the system will be displayed.
-<P>
-<H2><A NAME="ss9.142">9.142 show/prefix (0)</A>
-</H2>
-
-<P><CODE><B>show/prefix <callsign></B> Interrogate the prefix database</CODE>
-<P>
-<P>This command takes the <callsign> (which can be a full or partial
-callsign or a prefix), looks up which internal country number
-it is and then displays all the relevant prefixes for that country
-together with the internal country no, the CQ and ITU regions.
-<P>See also SHOW/DXCC
-<P>
-<P>
-<H2><A NAME="ss9.143">9.143 show/program (5)</A>
-</H2>
-
-<P><CODE><B>show/program</B> Show the locations of all the included program modules</CODE>
-<P>
-<P>Show the name and location where every program module was load from. This
-is useful for checking where you think you have loaded a .pm file from.
-<P>
-<H2><A NAME="ss9.144">9.144 show/qra (0)</A>
-</H2>
-
-<P><CODE><B>show/qra <locator> [<locator>]</B> Show the distance
-between locators<BR>
-<B>show/qra <lat> <long></B> Convert latitude and longitude to a locator</CODE>
+<P>I am of course assuming that you have a machine with both DXSpider and
+Internet access running.
<P>
-<P>This is a multipurpose command that allows you either to calculate the
-distance and bearing between two locators or (if only one locator is
-given on the command line) the distance and beraing from your station
-to the locator. For example:-
+<P>BEFORE YOU EVEN CONSIDER STARTING WITH THIS MAKE A BACKUP OF YOUR
+ENTIRE SPIDER TREE!!
<P>
-<BLOCKQUOTE><CODE>
-<PRE>
-SH/QRA IO92QL
-SH/QRA JN06 IN73
-</PRE>
-</CODE></BLOCKQUOTE>
-<P>The first example will show the distance and bearing to the locator from
-yourself, the second example will calculate the distance and bearing from
-the first locator to the second. You can use 4 or 6 character locators.
-<P>It is also possible to convert a latitude and longitude to a locator by
-using this command with a latitude and longitude as an argument, for
-example:-
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
-SH/QRA 52 41 N 0 58 E
-</PRE>
-</CODE></BLOCKQUOTE>
-<P>
-<H2><A NAME="ss9.145">9.145 show/qrz (0)</A>
-</H2>
-
-<P><CODE><B>show/qrz <callsign></B> Show any callbook details on a callsign</CODE>
-<P>
-<P>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
-<P>
-<H2><A NAME="ss9.146">9.146 show/registered (9)</A>
-</H2>
-
-<P><CODE><B>show/registered [<prefix>[</B> Show the registered users</CODE>
-<P>
-<H2><A NAME="ss9.147">9.147 show/route (0)</A>
-</H2>
-
-<P><CODE><B>show/route <callsign></B> Show the route to <callsign></CODE>
-<P>
-<P>This command allows you to see to which node the callsigns specified are
-connected. It is a sort of inverse sh/config.
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
- sh/route n2tly
-</PRE>
-</CODE></BLOCKQUOTE>
-<P>
-<H2><A NAME="ss9.148">9.148 show/satellite (0)</A>
-</H2>
-
-<P><CODE><B>show/satellite <name> [<hours> <interval>]</B>
-Show satellite tracking data</CODE>
-<P>
-<P>Show the tracking data from your location to the satellite of your choice
-from now on for the next few hours.
-<P>If you use this command without a satellite name it will display a list
-of all the satellites known currently to the system.
-<P>If you give a name then you can obtain tracking data of all the passes
-that start and finish 5 degrees below the horizon. As default it will
-give information for the next three hours for every five minute period.
-<P>You can alter the number of hours and the step size, within certain
-limits.
-<P>Each pass in a period is separated with a row of '-----' characters
-<P>So for example:-
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
-SH/SAT AO-10
-SH/SAT FENGYUN1 12 2
-</PRE>
-</CODE></BLOCKQUOTE>
-<P>
-<H2><A NAME="ss9.149">9.149 show/sun (0)</A>
-</H2>
-
-<P><CODE><B>show/sun [<prefix>|<callsign>]</B> Show
-sun rise and set times</CODE>
+<P>Assuming you are connected to the Internet, you need to login to the
+CVS repository and then update your Spider source. There are several
+steps which are listed below ...
<P>
-<P>Show the sun rise and set times for a (list of) prefixes or callsigns,
-together with the azimuth and elevation of the sun currently at those
-locations.
-<P>If you don't specify any prefixes or callsigns, it will show the times for
-your QTH (assuming you have set it with either SET/LOCATION or SET/QRA),
-together with the current azimuth and elevation.
-<P>If all else fails it will show the sunrise and set times for the node
-that you are connected to.
-<P>For example:-
+<P>First login as the user <EM>sysop</EM>. Next you need to connect to the CVS
+repository. You do this with the command below ...
<P>
-<BLOCKQUOTE><CODE>
<PRE>
- SH/SUN
- SH/SUN G1TLH K9CW ZS
+cvs -d:pserver:anonymous@cvs.DXSpider.sourceforge.net:/cvsroot/dxspider login
</PRE>
-</CODE></BLOCKQUOTE>
-<P>
-<H2><A NAME="ss9.150">9.150 show/time (0)</A>
-</H2>
-
-<P><CODE><B>show/time [<prefix>|<callsign>]</B> Show
-the local time</CODE>
-<P>
-<P>If no prefixes or callsigns are given then this command returns the local
-time and UTC as the computer has it right now. If you give some prefixes
-then it will show UTC and UTC + the local offset (not including DST) at
-the prefixes or callsigns that you specify.
-<P>
-<H2><A NAME="ss9.151">9.151 show/vhfstats (0)</A>
-</H2>
-
-<P><CODE><B>show/vhfstats</B> Show the VHF DX Statistics for last 31 days</CODE>
-<P>
-<P>Show the VHF DX spots breakdown by band for the last 31 days
-<P>
-<H2><A NAME="ss9.152">9.152 show/vhftable (0)</A>
-</H2>
-
-<P><CODE><B>show/vhftable</B> Show the VHF DX Spotter Table for your country</CODE>
-<P>
-<P>Show the VHF DX Spotter table for your country for the last 31 days
-<P>
-<H2><A NAME="ss9.153">9.153 show/wcy (0)</A>
-</H2>
-
-<P><CODE><B>show/wcy</B> Show the last 10 WCY broadcasts<BR>
-<B>show/wcy <n></B> Show the last <n> WCY broadcasts</CODE>
-<P>
-<P>Display the most recent WCY information that has been received by the system
-<P>
-<H2><A NAME="ss9.154">9.154 show/wwv (0)</A>
-</H2>
-
-<P><CODE><B>show/wwv</B> Show the last 10 WWV broadcasts<BR>
-<B>show/wwv <n></B> Show the last <n> WWV broadcasts</CODE>
-<P>
-<P>Display the most recent WWV information that has been received by the system
-<P>
-<P>
-<H2><A NAME="ss9.155">9.155 shutdown (5)</A>
-</H2>
-
-<P><CODE><B>shutdown</B> Shutdown the cluster</CODE>
-<P>
-<P>Shutdown the cluster and disconnect all the users. If you have Spider
-set to respawn in /etc/inittab it will of course restart.
-<P>
-<H2><A NAME="ss9.156">9.156 spoof (9)</A>
-</H2>
-
-<P><CODE><B>spoof <callsign> <command></B> Run commands as another user</CODE>
-<P>
-<P>This is a very simple yet powerful command for the sysop. It allows you to
-issue commands as if you were a different user. This is very useful for the
-kind of things that users seem to always get wrong.. like home_node for
-example.
-<P>
-<H2><A NAME="ss9.157">9.157 stat/db (5)</A>
-</H2>
-
-<P><CODE><B>stat/db <dbname></B> Show the status of a database</CODE>
-<P>
-<P>Show the internal status of a database descriptor.
-<P>Depending on your privilege level you will see more or less information.
-This command is unlikely to be of much use to anyone other than a sysop.
-<P>
-<H2><A NAME="ss9.158">9.158 stat/channel (5)</A>
-</H2>
-
-<P><CODE><B>stat/channel <callsign></B> Show the status of a channel on the cluster</CODE>
-<P>
-<P>Show the internal status of the channel object either for the channel that
-you are on or else for the callsign that you asked for.
-<P>Only the fields that are defined (in perl term) will be displayed.
-<P>
-<H2><A NAME="ss9.159">9.159 stat/msg (5)</A>
-</H2>
-
-<P><CODE><B>stat/msg <msgno></B> Show the status of a message</CODE>
+<P>You will get a password prompt. Simply hit return here and your machine should
+return to a normal linux prompt.
<P>
-<P>This command shows the internal status of a message and includes information
-such as to whom it has been forwarded, its size, origin etc etc.
+<P>What happens next depends on whether you have an existing installation that
+you want to update with the latest and greatest or whether you just want
+to see what is there and/or run it on a new machine for testing.
+<P>If you are installing Spider from CVS then change directory to /home/sysop
+<P>If you are wanting to update Spider then cd to /tmp
<P>
-<P>If no message number is given then the status of the message system is
-displayed.
+<P>The next step will create a brand new 'spider' directory in your current
+directory.
<P>
-<H2><A NAME="ss9.160">9.160 stat/route_node (5)</A>
-</H2>
-
-<P><CODE><B>stat/route_node <callsign></B> Show the data in a Route::Node object</CODE>
-<P>
-<H2><A NAME="ss9.161">9.161 stat/route_user (5)</A>
-</H2>
-
-<P><CODE><B>stat/route_user <callsign></B> Show the data in a Route::User object</CODE>
-<P>
-<H2><A NAME="ss9.162">9.162 stat/user (5)</A>
-</H2>
-
-<P><CODE><B>stat/user <callsign></B> Show the full status of a user</CODE>
-<P>
-<P>Shows the full contents of a user record including all the secret flags
-and stuff.
-<P>Only the fields that are defined (in perl term) will be displayed.
-<P>
-<H2><A NAME="ss9.163">9.163 sysop (0)</A>
-</H2>
-
-<P><CODE><B>sysop</B> Regain your privileges if you login remotely</CODE>
-<P>
-<P>The system automatically reduces your privilege level to that of a
-normal user if you login in remotely. This command allows you to
-regain your normal privilege level. It uses the normal system: five
-numbers are returned that are indexes into the character array that is
-your assigned password (see SET/PASSWORD). The indexes start from
-zero.
-<P>You are expected to return a string which contains the characters
-required in the correct order. You may intersperse those characters
-with others to obscure your reply for any watchers. For example (and
-these values are for explanation :-):
-<P>
-<BLOCKQUOTE><CODE>
<PRE>
- password = 012345678901234567890123456789
- > sysop
- 22 10 15 17 3
+cvs -z3 -d:pserver:anonymous@cvs.DXSpider.sourceforge.net:/cvsroot/dxspider co spider
</PRE>
-</CODE></BLOCKQUOTE>
-<P>you type:-
+<P>This command is all on one line.
<P>
-<BLOCKQUOTE><CODE>
-<PRE>
- aa2bbbb0ccc5ddd7xxx3n
- or 2 0 5 7 3
- or 20573
-</PRE>
-</CODE></BLOCKQUOTE>
-<P>They will all match. If there is no password you will still be offered
-numbers but nothing will happen when you input a string. Any match is
-case sensitive.
+<P>Hopefully your screen should show you downloading files. The -z3 simply compresses
+the download to improve speed.
+When this has finished, you will have exactly the same as if you had untarred a full
+tarball PLUS some extra directories and files that CVS needs to do the magic that
+it does.
<P>
-<H2><A NAME="ss9.164">9.164 talk (0)</A>
-</H2>
-
-<P><CODE><B>talk <callsign></B> Enter talk mode with <callsign><BR>
-<B>talk <callsign> <text></B> Send a text message to <callsign><BR>
-<B>talk <callsign> > <node_call> [<text>]</B>
-Send a text message to <callsign> via <node_call></CODE>
+<P>Now if you are doing a new installation, that's it. Carry on as if you have
+just downloaded and untarred the lastest tarball.
<P>
-<P>Send a short message to any other station that is visible on the cluster
-system. You can send it to anyone you can see with a SHOW/CONFIGURATION
-command, they don't have to be connected locally.
-<P>The second form of TALK is used when other cluster nodes are connected
-with restricted information. This usually means that they don't send
-the user information usually associated with logging on and off the cluster.
-<P>If you know that G3JNB is likely to be present on GB7TLH, but you can only
-see GB7TLH in the SH/C list but with no users, then you would use the
-second form of the talk message.
-<P>If you want to have a ragchew with someone you can leave the text message
-out and the system will go into 'Talk' mode. What this means is that a
-short message is sent to the recipient telling them that you are in a 'Talking'
-frame of mind and then you just type - everything you send will go to the
-station that you asked for.
-<P>All the usual announcements, spots and so on will still come out on your
-terminal.
-<P>If you want to do something (such as send a spot) you precede the normal
-command with a '/' character, eg:-
+<P>If you want to upgrade your current installation then do this ...
<P>
<BLOCKQUOTE><CODE>
<PRE>
- /DX 14001 G1TLH What's a B class licensee doing on 20m CW?
- /HELP talk
+tar cvfz /tmp/s.tgz spider
+cd /
+tar xvfzp /tmp/s.tgz
</PRE>
</CODE></BLOCKQUOTE>
-<P>To leave talk mode type:
+<P>This is assuming you downloaded to the /tmp directory of course.
<P>
-<BLOCKQUOTE><CODE>
-<PRE>
- /EX
-</PRE>
-</CODE></BLOCKQUOTE>
+<P>NOTE: the 'p' on the end of the 'xvfz' is IMPORTANT! It keeps the permissions
+correct. YOU WERE LOGGED IN AS THE USER SYSOP WEREN'T YOU?????
+<P>Remember to recompile the C client (cd /spider/src; make)
<P>
-<H2><A NAME="ss9.165">9.165 type (0)</A>
-</H2>
-
-<P><CODE><B>type <filearea>/<name></B> Look at a file in one of the fileareas</CODE>
+<P>At this point the files have been upgraded. You can (usually) restart the cluster
+in your own time. However, if you attempt to use any new commands or features
+expect it to be fatal! At least your cluster will have been restarted then so it
+will be too late to worry about it!
<P>
-<P>Type out the contents of a file in a filearea. So, for example, in
-filearea 'bulletins' you want to look at file 'arld051' you would
-enter:-
+<P>Now the magic part! From now on when you want to update, simply connect to the
+Internet and then, as the user <EM>sysop</EM> ...
<P>
<BLOCKQUOTE><CODE>
<PRE>
- TYPE bulletins/arld051
+cd /spider
+cvs -z3 update -d
</PRE>
</CODE></BLOCKQUOTE>
-<P>See also SHOW/FILES to see what fileareas are available and a
-list of content.
-<P>
-<H2><A NAME="ss9.166">9.166 who (0)</A>
-</H2>
-
-<P><CODE><B>who</B> Show who is physically connected locally</CODE>
-<P>
-<P>This is a quick listing that shows which callsigns are connected and
-what sort of connection they have
-<P>
-<H2><A NAME="ss9.167">9.167 wx (0)</A>
-</H2>
-
-<P><CODE><B>wx <text></B> Send a weather message to local users<BR>
-<B>wx full <text> </B> Send a weather message to all cluster users</CODE>
-<P>
-<P>Weather messages can sometimes be useful if you are experiencing an extreme
-that may indicate enhanced conditions
-<P>
-<H2><A NAME="ss9.168">9.168 wx (enhanced for sysops) (5)</A>
-</H2>
-
-<P><CODE><B>wx sysop <text></B> Send a weather message to other clusters only</CODE>
-<P>
-<P>Send a weather message only to other cluster nodes and not to general users.
-<P>
+<P>and your files will be updated. As above, remember to recompile the "C" client
+if it has been updated (CVS will tell you) and restart if any of the perl scripts
+have been altered or added, again, CVS will tell you.
<P>
+<P>You will find any changes documented in the /spider/Changes file.
<P>
<HR>
-Next
+<A HREF="adminmanual-10.html">Next</A>
<A HREF="adminmanual-8.html">Previous</A>
<A HREF="adminmanual.html#toc9">Contents</A>
</BODY>
<HTML>
<HEAD>
<META NAME="GENERATOR" CONTENT="SGML-Tools 1.0.9">
- <TITLE>The DXSpider Administration Manual v1.49</TITLE>
+ <TITLE>The DXSpider Administration Manual v1.50</TITLE>
<LINK HREF="adminmanual-1.html" REL=next>
Previous
Contents
<HR>
-<H1>The DXSpider Administration Manual v1.49</H1>
+<H1>The DXSpider Administration Manual v1.50</H1>
-<H2>Ian Maude, G0VGS, (g0vgs@gb7mbc.net)</H2>February 2002 revision 1.3
+<H2>Ian Maude, G0VGS, (g0vgs@gb7mbc.net)</H2>July 2002 revision 0.1
<P><HR>
<EM>A reference for SysOps of the DXSpider DXCluster program.</EM>
<HR>
<LI><A HREF="adminmanual-6.html#ss6.6">6.6 Console.pl</A>
<LI><A HREF="adminmanual-6.html#ss6.7">6.7 Updating kepler data</A>
<LI><A HREF="adminmanual-6.html#ss6.8">6.8 The QRZ callbook</A>
+<LI><A HREF="adminmanual-6.html#ss6.9">6.9 Connecting logging programs</A>
</UL>
<P>
-<H2><A NAME="toc7">7.</A> <A HREF="adminmanual-7.html">Security</A></H2>
+<H2><A NAME="toc7">7.</A> <A HREF="adminmanual-7.html">Java Web applet</A></H2>
+
+<P>
+<H2><A NAME="toc8">8.</A> <A HREF="adminmanual-8.html">Security</A></H2>
<UL>
-<LI><A HREF="adminmanual-7.html#ss7.1">7.1 Registration</A>
-<LI><A HREF="adminmanual-7.html#ss7.2">7.2 Passwords</A>
+<LI><A HREF="adminmanual-8.html#ss8.1">8.1 Registration</A>
+<LI><A HREF="adminmanual-8.html#ss8.2">8.2 Passwords</A>
</UL>
<P>
-<H2><A NAME="toc8">8.</A> <A HREF="adminmanual-8.html">CVS</A></H2>
+<H2><A NAME="toc9">9.</A> <A HREF="adminmanual-9.html">CVS</A></H2>
<P>
-<H2><A NAME="toc9">9.</A> <A HREF="adminmanual-9.html">The DXSpider command set</A></H2>
+<H2><A NAME="toc10">10.</A> <A HREF="adminmanual-10.html">The DXSpider command set</A></H2>
<UL>
-<LI><A HREF="adminmanual-9.html#ss9.1">9.1 accept/announce (0)</A>
-<LI><A HREF="adminmanual-9.html#ss9.2">9.2 accept/announce (extended for sysops) (8)</A>
-<LI><A HREF="adminmanual-9.html#ss9.3">9.3 accept/route (8)</A>
-<LI><A HREF="adminmanual-9.html#ss9.4">9.4 accept/spots (0)</A>
-<LI><A HREF="adminmanual-9.html#ss9.5">9.5 accept/spots (extended for sysops) (8)</A>
-<LI><A HREF="adminmanual-9.html#ss9.6">9.6 accept/wcy (0)</A>
-<LI><A HREF="adminmanual-9.html#ss9.7">9.7 accept/wcy (extended for sysops) (8)</A>
-<LI><A HREF="adminmanual-9.html#ss9.8">9.8 accept/wwv (0)</A>
-<LI><A HREF="adminmanual-9.html#ss9.9">9.9 accept/wwv (extended for sysops) (8)</A>
-<LI><A HREF="adminmanual-9.html#ss9.10">9.10 announce (0)</A>
-<LI><A HREF="adminmanual-9.html#ss9.11">9.11 announce full (0)</A>
-<LI><A HREF="adminmanual-9.html#ss9.12">9.12 announce sysop (5)</A>
-<LI><A HREF="adminmanual-9.html#ss9.13">9.13 apropos (0)</A>
-<LI><A HREF="adminmanual-9.html#ss9.14">9.14 bye (0)</A>
-<LI><A HREF="adminmanual-9.html#ss9.15">9.15 catchup (5)</A>
-<LI><A HREF="adminmanual-9.html#ss9.16">9.16 clear/announce (8)</A>
-<LI><A HREF="adminmanual-9.html#ss9.17">9.17 clear/route (8)</A>
-<LI><A HREF="adminmanual-9.html#ss9.18">9.18 clear/spots (0)</A>
-<LI><A HREF="adminmanual-9.html#ss9.19">9.19 clear/spots (extended for sysops) (8)</A>
-<LI><A HREF="adminmanual-9.html#ss9.20">9.20 clear/wcy (0)</A>
-<LI><A HREF="adminmanual-9.html#ss9.21">9.21 clear/wcy (extended for sysops) (8)</A>
-<LI><A HREF="adminmanual-9.html#ss9.22">9.22 clear/wwv (0)</A>
-<LI><A HREF="adminmanual-9.html#ss9.23">9.23 clear/wwv (extended for sysops) (8)</A>
-<LI><A HREF="adminmanual-9.html#ss9.24">9.24 connect (5) </A>
-<LI><A HREF="adminmanual-9.html#ss9.25">9.25 dbavail (0)</A>
-<LI><A HREF="adminmanual-9.html#ss9.26">9.26 dbcreate (9)</A>
-<LI><A HREF="adminmanual-9.html#ss9.27">9.27 dbimport (9)</A>
-<LI><A HREF="adminmanual-9.html#ss9.28">9.28 dbremove (9)</A>
-<LI><A HREF="adminmanual-9.html#ss9.29">9.29 dbshow (0)</A>
-<LI><A HREF="adminmanual-9.html#ss9.30">9.30 debug (9)</A>
-<LI><A HREF="adminmanual-9.html#ss9.31">9.31 delete/user (9)</A>
-<LI><A HREF="adminmanual-9.html#ss9.32">9.32 directory (0)</A>
-<LI><A HREF="adminmanual-9.html#ss9.33">9.33 directory (extended for sysops) (5)</A>
-<LI><A HREF="adminmanual-9.html#ss9.34">9.34 disconnect (8)</A>
-<LI><A HREF="adminmanual-9.html#ss9.35">9.35 dx (0)</A>
-<LI><A HREF="adminmanual-9.html#ss9.36">9.36 export (9)</A>
-<LI><A HREF="adminmanual-9.html#ss9.37">9.37 export_users (9)</A>
-<LI><A HREF="adminmanual-9.html#ss9.38">9.38 filtering (0)</A>
-<LI><A HREF="adminmanual-9.html#ss9.39">9.39 forward/latlong (8)</A>
-<LI><A HREF="adminmanual-9.html#ss9.40">9.40 forward/opername (1)</A>
-<LI><A HREF="adminmanual-9.html#ss9.41">9.41 help (0)</A>
-<LI><A HREF="adminmanual-9.html#ss9.42">9.42 init (5)</A>
-<LI><A HREF="adminmanual-9.html#ss9.43">9.43 kill (0)</A>
-<LI><A HREF="adminmanual-9.html#ss9.44">9.44 kill (5)</A>
-<LI><A HREF="adminmanual-9.html#ss9.45">9.45 kill full (5)</A>
-<LI><A HREF="adminmanual-9.html#ss9.46">9.46 kill/expunge (6)</A>
-<LI><A HREF="adminmanual-9.html#ss9.47">9.47 links (0)</A>
-<LI><A HREF="adminmanual-9.html#ss9.48">9.48 load/aliases (9)</A>
-<LI><A HREF="adminmanual-9.html#ss9.49">9.49 load/badmsg (9)</A>
-<LI><A HREF="adminmanual-9.html#ss9.50">9.50 load/badwords (9)</A>
-<LI><A HREF="adminmanual-9.html#ss9.51">9.51 load/bands (9)</A>
-<LI><A HREF="adminmanual-9.html#ss9.52">9.52 load/cmd_cache (9)</A>
-<LI><A HREF="adminmanual-9.html#ss9.53">9.53 load/forward (9)</A>
-<LI><A HREF="adminmanual-9.html#ss9.54">9.54 load/messages (9)</A>
-<LI><A HREF="adminmanual-9.html#ss9.55">9.55 load/prefixes (9)</A>
-<LI><A HREF="adminmanual-9.html#ss9.56">9.56 merge (5)</A>
-<LI><A HREF="adminmanual-9.html#ss9.57">9.57 msg (9)</A>
-<LI><A HREF="adminmanual-9.html#ss9.58">9.58 pc (8)</A>
-<LI><A HREF="adminmanual-9.html#ss9.59">9.59 ping (1)</A>
-<LI><A HREF="adminmanual-9.html#ss9.60">9.60 rcmd (1)</A>
-<LI><A HREF="adminmanual-9.html#ss9.61">9.61 read (0)</A>
-<LI><A HREF="adminmanual-9.html#ss9.62">9.62 read (extended for sysops) (5) </A>
-<LI><A HREF="adminmanual-9.html#ss9.63">9.63 reject/announce</A>
-<LI><A HREF="adminmanual-9.html#ss9.64">9.64 reject/announce (extended for sysops) (8)</A>
-<LI><A HREF="adminmanual-9.html#ss9.65">9.65 reject/route (8)</A>
-<LI><A HREF="adminmanual-9.html#ss9.66">9.66 reject/spots (0)</A>
-<LI><A HREF="adminmanual-9.html#ss9.67">9.67 reject/spots (extended for sysops) (8)</A>
-<LI><A HREF="adminmanual-9.html#ss9.68">9.68 reject/wcy (0)</A>
-<LI><A HREF="adminmanual-9.html#ss9.69">9.69 reject/wcy (extended for sysops) (8)</A>
-<LI><A HREF="adminmanual-9.html#ss9.70">9.70 reject/wwv (0)</A>
-<LI><A HREF="adminmanual-9.html#ss9.71">9.71 reject/wwv (extended for sysops) (8)</A>
-<LI><A HREF="adminmanual-9.html#ss9.72">9.72 reply (0)</A>
-<LI><A HREF="adminmanual-9.html#ss9.73">9.73 send (0)</A>
-<LI><A HREF="adminmanual-9.html#ss9.74">9.74 set/address (0)</A>
-<LI><A HREF="adminmanual-9.html#ss9.75">9.75 set/announce (0)</A>
-<LI><A HREF="adminmanual-9.html#ss9.76">9.76 set/arcluster (5)</A>
-<LI><A HREF="adminmanual-9.html#ss9.77">9.77 set/baddx (8)</A>
-<LI><A HREF="adminmanual-9.html#ss9.78">9.78 set/badnode (6)</A>
-<LI><A HREF="adminmanual-9.html#ss9.79">9.79 set/badspotter (8)</A>
-<LI><A HREF="adminmanual-9.html#ss9.80">9.80 set/badword (8)</A>
-<LI><A HREF="adminmanual-9.html#ss9.81">9.81 set/beep (0)</A>
-<LI><A HREF="adminmanual-9.html#ss9.82">9.82 set/bbs (5)</A>
-<LI><A HREF="adminmanual-9.html#ss9.83">9.83 set/clx (5)</A>
-<LI><A HREF="adminmanual-9.html#ss9.84">9.84 set/debug (9)</A>
-<LI><A HREF="adminmanual-9.html#ss9.85">9.85 set/dx (0)</A>
-<LI><A HREF="adminmanual-9.html#ss9.86">9.86 set/dxgrid (0)</A>
-<LI><A HREF="adminmanual-9.html#ss9.87">9.87 set/dxnet (5)</A>
-<LI><A HREF="adminmanual-9.html#ss9.88">9.88 set/echo (0)</A>
-<LI><A HREF="adminmanual-9.html#ss9.89">9.89 set/email (0)</A>
-<LI><A HREF="adminmanual-9.html#ss9.90">9.90 set/here (0)</A>
-<LI><A HREF="adminmanual-9.html#ss9.91">9.91 set/homenode (0)</A>
-<LI><A HREF="adminmanual-9.html#ss9.92">9.92 set/hops (8)</A>
-<LI><A HREF="adminmanual-9.html#ss9.93">9.93 set/isolate (9)</A>
-<LI><A HREF="adminmanual-9.html#ss9.94">9.94 set/language (0)</A>
-<LI><A HREF="adminmanual-9.html#ss9.95">9.95 set/location (0)</A>
-<LI><A HREF="adminmanual-9.html#ss9.96">9.96 set/sys_location (9)</A>
-<LI><A HREF="adminmanual-9.html#ss9.97">9.97 set/logininfo (0)</A>
-<LI><A HREF="adminmanual-9.html#ss9.98">9.98 set/lockout (9)</A>
-<LI><A HREF="adminmanual-9.html#ss9.99">9.99 set/name (0)</A>
-<LI><A HREF="adminmanual-9.html#ss9.100">9.100 set/node (9)</A>
-<LI><A HREF="adminmanual-9.html#ss9.101">9.101 set/obscount (9)</A>
-<LI><A HREF="adminmanual-9.html#ss9.102">9.102 set/page (0)</A>
-<LI><A HREF="adminmanual-9.html#ss9.103">9.103 set/password (0)</A>
-<LI><A HREF="adminmanual-9.html#ss9.104">9.104 set/password (9)</A>
-<LI><A HREF="adminmanual-9.html#ss9.105">9.105 set/pinginterval (9)</A>
-<LI><A HREF="adminmanual-9.html#ss9.106">9.106 set/privilege (9)</A>
-<LI><A HREF="adminmanual-9.html#ss9.107">9.107 set/spider (5)</A>
-<LI><A HREF="adminmanual-9.html#ss9.108">9.108 set/sys_qra (9)</A>
-<LI><A HREF="adminmanual-9.html#ss9.109">9.109 set/qra (0)</A>
-<LI><A HREF="adminmanual-9.html#ss9.110">9.110 set/qth (0)</A>
-<LI><A HREF="adminmanual-9.html#ss9.111">9.111 set/register (9)</A>
-<LI><A HREF="adminmanual-9.html#ss9.112">9.112 set/talk (0)</A>
-<LI><A HREF="adminmanual-9.html#ss9.113">9.113 set/wcy (0)</A>
-<LI><A HREF="adminmanual-9.html#ss9.114">9.114 set/wwv (0)</A>
-<LI><A HREF="adminmanual-9.html#ss9.115">9.115 set/wx (0)</A>
-<LI><A HREF="adminmanual-9.html#ss9.116">9.116 show/baddx (1)</A>
-<LI><A HREF="adminmanual-9.html#ss9.117">9.117 show/badnode (6)</A>
-<LI><A HREF="adminmanual-9.html#ss9.118">9.118 show/badspotter (1)</A>
-<LI><A HREF="adminmanual-9.html#ss9.119">9.119 show/badword (1)</A>
-<LI><A HREF="adminmanual-9.html#ss9.120">9.120 show/configuration (0)</A>
-<LI><A HREF="adminmanual-9.html#ss9.121">9.121 show/configuration/node (0)</A>
-<LI><A HREF="adminmanual-9.html#ss9.122">9.122 show/connect (1)</A>
-<LI><A HREF="adminmanual-9.html#ss9.123">9.123 show/date (0)</A>
-<LI><A HREF="adminmanual-9.html#ss9.124">9.124 show/debug (9)</A>
-<LI><A HREF="adminmanual-9.html#ss9.125">9.125 show/dx (0)</A>
-<LI><A HREF="adminmanual-9.html#ss9.126">9.126 show/dxcc (0)</A>
-<LI><A HREF="adminmanual-9.html#ss9.127">9.127 sh/dxstats (0)</A>
-<LI><A HREF="adminmanual-9.html#ss9.128">9.128 show/files (0)</A>
-<LI><A HREF="adminmanual-9.html#ss9.129">9.129 show/filter (0)</A>
-<LI><A HREF="adminmanual-9.html#ss9.130">9.130 show/filter (extended for sysops) (5)</A>
-<LI><A HREF="adminmanual-9.html#ss9.131">9.131 show/hfstats (0)</A>
-<LI><A HREF="adminmanual-9.html#ss9.132">9.132 show/hftable (0)</A>
-<LI><A HREF="adminmanual-9.html#ss9.133">9.133 show/hops (8)</A>
-<LI><A HREF="adminmanual-9.html#ss9.134">9.134 show/isolate (1)</A>
-<LI><A HREF="adminmanual-9.html#ss9.135">9.135 show/lockout (9)</A>
-<LI><A HREF="adminmanual-9.html#ss9.136">9.136 show/log (8)</A>
-<LI><A HREF="adminmanual-9.html#ss9.137">9.137 show/moon (0)</A>
-<LI><A HREF="adminmanual-9.html#ss9.138">9.138 show/muf (0)</A>
-<LI><A HREF="adminmanual-9.html#ss9.139">9.139 show/newconfiguration (0)</A>
-<LI><A HREF="adminmanual-9.html#ss9.140">9.140 show/newconfiguration/node (0)</A>
-<LI><A HREF="adminmanual-9.html#ss9.141">9.141 show/node (1)</A>
-<LI><A HREF="adminmanual-9.html#ss9.142">9.142 show/prefix (0)</A>
-<LI><A HREF="adminmanual-9.html#ss9.143">9.143 show/program (5)</A>
-<LI><A HREF="adminmanual-9.html#ss9.144">9.144 show/qra (0)</A>
-<LI><A HREF="adminmanual-9.html#ss9.145">9.145 show/qrz (0)</A>
-<LI><A HREF="adminmanual-9.html#ss9.146">9.146 show/registered (9)</A>
-<LI><A HREF="adminmanual-9.html#ss9.147">9.147 show/route (0)</A>
-<LI><A HREF="adminmanual-9.html#ss9.148">9.148 show/satellite (0)</A>
-<LI><A HREF="adminmanual-9.html#ss9.149">9.149 show/sun (0)</A>
-<LI><A HREF="adminmanual-9.html#ss9.150">9.150 show/time (0)</A>
-<LI><A HREF="adminmanual-9.html#ss9.151">9.151 show/vhfstats (0)</A>
-<LI><A HREF="adminmanual-9.html#ss9.152">9.152 show/vhftable (0)</A>
-<LI><A HREF="adminmanual-9.html#ss9.153">9.153 show/wcy (0)</A>
-<LI><A HREF="adminmanual-9.html#ss9.154">9.154 show/wwv (0)</A>
-<LI><A HREF="adminmanual-9.html#ss9.155">9.155 shutdown (5)</A>
-<LI><A HREF="adminmanual-9.html#ss9.156">9.156 spoof (9)</A>
-<LI><A HREF="adminmanual-9.html#ss9.157">9.157 stat/db (5)</A>
-<LI><A HREF="adminmanual-9.html#ss9.158">9.158 stat/channel (5)</A>
-<LI><A HREF="adminmanual-9.html#ss9.159">9.159 stat/msg (5)</A>
-<LI><A HREF="adminmanual-9.html#ss9.160">9.160 stat/route_node (5)</A>
-<LI><A HREF="adminmanual-9.html#ss9.161">9.161 stat/route_user (5)</A>
-<LI><A HREF="adminmanual-9.html#ss9.162">9.162 stat/user (5)</A>
-<LI><A HREF="adminmanual-9.html#ss9.163">9.163 sysop (0)</A>
-<LI><A HREF="adminmanual-9.html#ss9.164">9.164 talk (0)</A>
-<LI><A HREF="adminmanual-9.html#ss9.165">9.165 type (0)</A>
-<LI><A HREF="adminmanual-9.html#ss9.166">9.166 who (0)</A>
-<LI><A HREF="adminmanual-9.html#ss9.167">9.167 wx (0)</A>
-<LI><A HREF="adminmanual-9.html#ss9.168">9.168 wx (enhanced for sysops) (5)</A>
+<LI><A HREF="adminmanual-10.html#ss10.1">10.1 accept/announce (0)</A>
+<LI><A HREF="adminmanual-10.html#ss10.2">10.2 accept/announce (extended for sysops) (8)</A>
+<LI><A HREF="adminmanual-10.html#ss10.3">10.3 accept/route (8)</A>
+<LI><A HREF="adminmanual-10.html#ss10.4">10.4 accept/spots (0)</A>
+<LI><A HREF="adminmanual-10.html#ss10.5">10.5 accept/spots (extended for sysops) (8)</A>
+<LI><A HREF="adminmanual-10.html#ss10.6">10.6 accept/wcy (0)</A>
+<LI><A HREF="adminmanual-10.html#ss10.7">10.7 accept/wcy (extended for sysops) (8)</A>
+<LI><A HREF="adminmanual-10.html#ss10.8">10.8 accept/wwv (0)</A>
+<LI><A HREF="adminmanual-10.html#ss10.9">10.9 accept/wwv (extended for sysops) (8)</A>
+<LI><A HREF="adminmanual-10.html#ss10.10">10.10 announce (0)</A>
+<LI><A HREF="adminmanual-10.html#ss10.11">10.11 announce full (0)</A>
+<LI><A HREF="adminmanual-10.html#ss10.12">10.12 announce sysop (5)</A>
+<LI><A HREF="adminmanual-10.html#ss10.13">10.13 apropos (0)</A>
+<LI><A HREF="adminmanual-10.html#ss10.14">10.14 bye (0)</A>
+<LI><A HREF="adminmanual-10.html#ss10.15">10.15 catchup (5)</A>
+<LI><A HREF="adminmanual-10.html#ss10.16">10.16 clear/announce (8)</A>
+<LI><A HREF="adminmanual-10.html#ss10.17">10.17 clear/route (8)</A>
+<LI><A HREF="adminmanual-10.html#ss10.18">10.18 clear/spots (0)</A>
+<LI><A HREF="adminmanual-10.html#ss10.19">10.19 clear/spots (extended for sysops) (8)</A>
+<LI><A HREF="adminmanual-10.html#ss10.20">10.20 clear/wcy (0)</A>
+<LI><A HREF="adminmanual-10.html#ss10.21">10.21 clear/wcy (extended for sysops) (8)</A>
+<LI><A HREF="adminmanual-10.html#ss10.22">10.22 clear/wwv (0)</A>
+<LI><A HREF="adminmanual-10.html#ss10.23">10.23 clear/wwv (extended for sysops) (8)</A>
+<LI><A HREF="adminmanual-10.html#ss10.24">10.24 connect (5) </A>
+<LI><A HREF="adminmanual-10.html#ss10.25">10.25 dbavail (0)</A>
+<LI><A HREF="adminmanual-10.html#ss10.26">10.26 dbcreate (9)</A>
+<LI><A HREF="adminmanual-10.html#ss10.27">10.27 dbimport (9)</A>
+<LI><A HREF="adminmanual-10.html#ss10.28">10.28 dbremove (9)</A>
+<LI><A HREF="adminmanual-10.html#ss10.29">10.29 dbshow (0)</A>
+<LI><A HREF="adminmanual-10.html#ss10.30">10.30 debug (9)</A>
+<LI><A HREF="adminmanual-10.html#ss10.31">10.31 delete/user (9)</A>
+<LI><A HREF="adminmanual-10.html#ss10.32">10.32 demonstrate (9)</A>
+<LI><A HREF="adminmanual-10.html#ss10.33">10.33 directory (0)</A>
+<LI><A HREF="adminmanual-10.html#ss10.34">10.34 directory (extended for sysops) (5)</A>
+<LI><A HREF="adminmanual-10.html#ss10.35">10.35 disconnect (8)</A>
+<LI><A HREF="adminmanual-10.html#ss10.36">10.36 dx (0)</A>
+<LI><A HREF="adminmanual-10.html#ss10.37">10.37 export (9)</A>
+<LI><A HREF="adminmanual-10.html#ss10.38">10.38 export_users (9)</A>
+<LI><A HREF="adminmanual-10.html#ss10.39">10.39 filtering (0)</A>
+<LI><A HREF="adminmanual-10.html#ss10.40">10.40 forward/latlong (8)</A>
+<LI><A HREF="adminmanual-10.html#ss10.41">10.41 forward/opername (1)</A>
+<LI><A HREF="adminmanual-10.html#ss10.42">10.42 help (0)</A>
+<LI><A HREF="adminmanual-10.html#ss10.43">10.43 init (5)</A>
+<LI><A HREF="adminmanual-10.html#ss10.44">10.44 kill (0)</A>
+<LI><A HREF="adminmanual-10.html#ss10.45">10.45 kill (5)</A>
+<LI><A HREF="adminmanual-10.html#ss10.46">10.46 kill full (5)</A>
+<LI><A HREF="adminmanual-10.html#ss10.47">10.47 kill/expunge (6)</A>
+<LI><A HREF="adminmanual-10.html#ss10.48">10.48 links (0)</A>
+<LI><A HREF="adminmanual-10.html#ss10.49">10.49 load/aliases (9)</A>
+<LI><A HREF="adminmanual-10.html#ss10.50">10.50 load/badmsg (9)</A>
+<LI><A HREF="adminmanual-10.html#ss10.51">10.51 load/badwords (9)</A>
+<LI><A HREF="adminmanual-10.html#ss10.52">10.52 load/bands (9)</A>
+<LI><A HREF="adminmanual-10.html#ss10.53">10.53 load/cmd_cache (9)</A>
+<LI><A HREF="adminmanual-10.html#ss10.54">10.54 load/forward (9)</A>
+<LI><A HREF="adminmanual-10.html#ss10.55">10.55 load/messages (9)</A>
+<LI><A HREF="adminmanual-10.html#ss10.56">10.56 load/prefixes (9)</A>
+<LI><A HREF="adminmanual-10.html#ss10.57">10.57 merge (5)</A>
+<LI><A HREF="adminmanual-10.html#ss10.58">10.58 msg (9)</A>
+<LI><A HREF="adminmanual-10.html#ss10.59">10.59 pc (8)</A>
+<LI><A HREF="adminmanual-10.html#ss10.60">10.60 ping (1)</A>
+<LI><A HREF="adminmanual-10.html#ss10.61">10.61 rcmd (1)</A>
+<LI><A HREF="adminmanual-10.html#ss10.62">10.62 read (0)</A>
+<LI><A HREF="adminmanual-10.html#ss10.63">10.63 read (extended for sysops) (5) </A>
+<LI><A HREF="adminmanual-10.html#ss10.64">10.64 reject/announce</A>
+<LI><A HREF="adminmanual-10.html#ss10.65">10.65 reject/announce (extended for sysops) (8)</A>
+<LI><A HREF="adminmanual-10.html#ss10.66">10.66 reject/route (8)</A>
+<LI><A HREF="adminmanual-10.html#ss10.67">10.67 reject/spots (0)</A>
+<LI><A HREF="adminmanual-10.html#ss10.68">10.68 reject/spots (extended for sysops) (8)</A>
+<LI><A HREF="adminmanual-10.html#ss10.69">10.69 reject/wcy (0)</A>
+<LI><A HREF="adminmanual-10.html#ss10.70">10.70 reject/wcy (extended for sysops) (8)</A>
+<LI><A HREF="adminmanual-10.html#ss10.71">10.71 reject/wwv (0)</A>
+<LI><A HREF="adminmanual-10.html#ss10.72">10.72 reject/wwv (extended for sysops) (8)</A>
+<LI><A HREF="adminmanual-10.html#ss10.73">10.73 reply (0)</A>
+<LI><A HREF="adminmanual-10.html#ss10.74">10.74 send (0)</A>
+<LI><A HREF="adminmanual-10.html#ss10.75">10.75 set/address (0)</A>
+<LI><A HREF="adminmanual-10.html#ss10.76">10.76 set/announce (0)</A>
+<LI><A HREF="adminmanual-10.html#ss10.77">10.77 set/arcluster (5)</A>
+<LI><A HREF="adminmanual-10.html#ss10.78">10.78 set/baddx (8)</A>
+<LI><A HREF="adminmanual-10.html#ss10.79">10.79 set/badnode (6)</A>
+<LI><A HREF="adminmanual-10.html#ss10.80">10.80 set/badspotter (8)</A>
+<LI><A HREF="adminmanual-10.html#ss10.81">10.81 set/badword (8)</A>
+<LI><A HREF="adminmanual-10.html#ss10.82">10.82 set/beep (0)</A>
+<LI><A HREF="adminmanual-10.html#ss10.83">10.83 set/bbs (5)</A>
+<LI><A HREF="adminmanual-10.html#ss10.84">10.84 set/clx (5)</A>
+<LI><A HREF="adminmanual-10.html#ss10.85">10.85 set/debug (9)</A>
+<LI><A HREF="adminmanual-10.html#ss10.86">10.86 set/dx (0)</A>
+<LI><A HREF="adminmanual-10.html#ss10.87">10.87 set/dxgrid (0)</A>
+<LI><A HREF="adminmanual-10.html#ss10.88">10.88 set/dxnet (5)</A>
+<LI><A HREF="adminmanual-10.html#ss10.89">10.89 set/echo (0)</A>
+<LI><A HREF="adminmanual-10.html#ss10.90">10.90 set/email (0)</A>
+<LI><A HREF="adminmanual-10.html#ss10.91">10.91 set/here (0)</A>
+<LI><A HREF="adminmanual-10.html#ss10.92">10.92 set/homenode (0)</A>
+<LI><A HREF="adminmanual-10.html#ss10.93">10.93 set/hops (8)</A>
+<LI><A HREF="adminmanual-10.html#ss10.94">10.94 set/isolate (9)</A>
+<LI><A HREF="adminmanual-10.html#ss10.95">10.95 set/language (0)</A>
+<LI><A HREF="adminmanual-10.html#ss10.96">10.96 set/location (0)</A>
+<LI><A HREF="adminmanual-10.html#ss10.97">10.97 set/sys_location (9)</A>
+<LI><A HREF="adminmanual-10.html#ss10.98">10.98 set/logininfo (0)</A>
+<LI><A HREF="adminmanual-10.html#ss10.99">10.99 set/lockout (9)</A>
+<LI><A HREF="adminmanual-10.html#ss10.100">10.100 set/name (0)</A>
+<LI><A HREF="adminmanual-10.html#ss10.101">10.101 set/node (9)</A>
+<LI><A HREF="adminmanual-10.html#ss10.102">10.102 set/obscount (9)</A>
+<LI><A HREF="adminmanual-10.html#ss10.103">10.103 set/page (0)</A>
+<LI><A HREF="adminmanual-10.html#ss10.104">10.104 set/password (0)</A>
+<LI><A HREF="adminmanual-10.html#ss10.105">10.105 set/password (9)</A>
+<LI><A HREF="adminmanual-10.html#ss10.106">10.106 set/pinginterval (9)</A>
+<LI><A HREF="adminmanual-10.html#ss10.107">10.107 set/privilege (9)</A>
+<LI><A HREF="adminmanual-10.html#ss10.108">10.108 set/spider (5)</A>
+<LI><A HREF="adminmanual-10.html#ss10.109">10.109 set/sys_qra (9)</A>
+<LI><A HREF="adminmanual-10.html#ss10.110">10.110 set/qra (0)</A>
+<LI><A HREF="adminmanual-10.html#ss10.111">10.111 set/qth (0)</A>
+<LI><A HREF="adminmanual-10.html#ss10.112">10.112 set/register (9)</A>
+<LI><A HREF="adminmanual-10.html#ss10.113">10.113 set/talk (0)</A>
+<LI><A HREF="adminmanual-10.html#ss10.114">10.114 set/wcy (0)</A>
+<LI><A HREF="adminmanual-10.html#ss10.115">10.115 set/wwv (0)</A>
+<LI><A HREF="adminmanual-10.html#ss10.116">10.116 set/wx (0)</A>
+<LI><A HREF="adminmanual-10.html#ss10.117">10.117 show/baddx (1)</A>
+<LI><A HREF="adminmanual-10.html#ss10.118">10.118 show/badnode (6)</A>
+<LI><A HREF="adminmanual-10.html#ss10.119">10.119 show/badspotter (1)</A>
+<LI><A HREF="adminmanual-10.html#ss10.120">10.120 show/badword (1)</A>
+<LI><A HREF="adminmanual-10.html#ss10.121">10.121 show/configuration (0)</A>
+<LI><A HREF="adminmanual-10.html#ss10.122">10.122 show/configuration/node (0)</A>
+<LI><A HREF="adminmanual-10.html#ss10.123">10.123 show/connect (1)</A>
+<LI><A HREF="adminmanual-10.html#ss10.124">10.124 show/date (0)</A>
+<LI><A HREF="adminmanual-10.html#ss10.125">10.125 show/debug (9)</A>
+<LI><A HREF="adminmanual-10.html#ss10.126">10.126 show/dx (0)</A>
+<LI><A HREF="adminmanual-10.html#ss10.127">10.127 show/dxcc (0)</A>
+<LI><A HREF="adminmanual-10.html#ss10.128">10.128 sh/dxstats (0)</A>
+<LI><A HREF="adminmanual-10.html#ss10.129">10.129 show/files (0)</A>
+<LI><A HREF="adminmanual-10.html#ss10.130">10.130 show/filter (0)</A>
+<LI><A HREF="adminmanual-10.html#ss10.131">10.131 show/filter (extended for sysops) (5)</A>
+<LI><A HREF="adminmanual-10.html#ss10.132">10.132 show/hfstats (0)</A>
+<LI><A HREF="adminmanual-10.html#ss10.133">10.133 show/hftable (0)</A>
+<LI><A HREF="adminmanual-10.html#ss10.134">10.134 show/hops (8)</A>
+<LI><A HREF="adminmanual-10.html#ss10.135">10.135 show/isolate (1)</A>
+<LI><A HREF="adminmanual-10.html#ss10.136">10.136 show/lockout (9)</A>
+<LI><A HREF="adminmanual-10.html#ss10.137">10.137 show/log (8)</A>
+<LI><A HREF="adminmanual-10.html#ss10.138">10.138 show/moon (0)</A>
+<LI><A HREF="adminmanual-10.html#ss10.139">10.139 show/muf (0)</A>
+<LI><A HREF="adminmanual-10.html#ss10.140">10.140 show/newconfiguration (0)</A>
+<LI><A HREF="adminmanual-10.html#ss10.141">10.141 show/newconfiguration/node (0)</A>
+<LI><A HREF="adminmanual-10.html#ss10.142">10.142 show/node (1)</A>
+<LI><A HREF="adminmanual-10.html#ss10.143">10.143 show/prefix (0)</A>
+<LI><A HREF="adminmanual-10.html#ss10.144">10.144 show/program (5)</A>
+<LI><A HREF="adminmanual-10.html#ss10.145">10.145 show/qra (0)</A>
+<LI><A HREF="adminmanual-10.html#ss10.146">10.146 show/qrz (0)</A>
+<LI><A HREF="adminmanual-10.html#ss10.147">10.147 show/registered (9)</A>
+<LI><A HREF="adminmanual-10.html#ss10.148">10.148 show/route (0)</A>
+<LI><A HREF="adminmanual-10.html#ss10.149">10.149 show/satellite (0)</A>
+<LI><A HREF="adminmanual-10.html#ss10.150">10.150 show/sun (0)</A>
+<LI><A HREF="adminmanual-10.html#ss10.151">10.151 show/time (0)</A>
+<LI><A HREF="adminmanual-10.html#ss10.152">10.152 show/vhfstats (0)</A>
+<LI><A HREF="adminmanual-10.html#ss10.153">10.153 show/vhftable (0)</A>
+<LI><A HREF="adminmanual-10.html#ss10.154">10.154 show/wcy (0)</A>
+<LI><A HREF="adminmanual-10.html#ss10.155">10.155 show/wwv (0)</A>
+<LI><A HREF="adminmanual-10.html#ss10.156">10.156 shutdown (5)</A>
+<LI><A HREF="adminmanual-10.html#ss10.157">10.157 spoof (9)</A>
+<LI><A HREF="adminmanual-10.html#ss10.158">10.158 stat/db (5)</A>
+<LI><A HREF="adminmanual-10.html#ss10.159">10.159 stat/channel (5)</A>
+<LI><A HREF="adminmanual-10.html#ss10.160">10.160 stat/msg (5)</A>
+<LI><A HREF="adminmanual-10.html#ss10.161">10.161 stat/route_node (5)</A>
+<LI><A HREF="adminmanual-10.html#ss10.162">10.162 stat/route_user (5)</A>
+<LI><A HREF="adminmanual-10.html#ss10.163">10.163 stat/user (5)</A>
+<LI><A HREF="adminmanual-10.html#ss10.164">10.164 sysop (0)</A>
+<LI><A HREF="adminmanual-10.html#ss10.165">10.165 talk (0)</A>
+<LI><A HREF="adminmanual-10.html#ss10.166">10.166 type (0)</A>
+<LI><A HREF="adminmanual-10.html#ss10.167">10.167 who (0)</A>
+<LI><A HREF="adminmanual-10.html#ss10.168">10.168 wx (0)</A>
+<LI><A HREF="adminmanual-10.html#ss10.169">10.169 wx (enhanced for sysops) (5)</A>
</UL>
<HR>
<A HREF="adminmanual-1.html">Next</A>
<HTML>
<HEAD>
<META NAME="GENERATOR" CONTENT="SGML-Tools 1.0.9">
- <TITLE>The DXSpider Installation Manual v1.49: Linux Installation </TITLE>
+ <TITLE>The DXSpider Installation Manual v1.50: Linux Installation </TITLE>
<LINK HREF="installation-2.html" REL=next>
<LINK HREF="installation.html#toc1" REL=contents>
<H2><A NAME="ss1.1">1.1 Introduction</A>
</H2>
-<P>This section describes the installation of DX Spider v1.47 on a
+<P>This section describes the installation of DX Spider v1.50 on a
<A HREF="http://www.redhat.com">RedHat</A> Linux Distribution.
Wherever possible I will try to include differences for other distributions.
-I do not intend to try and cover the installation of Linux or the setup
-of the AX25 utilities. If you need help on this then read Iains original
-installation guide that comes with the Spider distribution.
<P>
<P>I am assuming a general knowledge of Linux and its commands. You should
know how to use <EM>tar</EM> and how to edit files using your favourite editor.
<A HREF="http://www.cpan.org/modules/by-module/Curses/Curses-1.06.tar.gz">Curses-1.06.tar.gz</A></LI>
<LI>
<A HREF="http://www.cpan.org/modules/by-module/Time/Time-HiRes-01.20.tar.gz">Time-HiRes-01.20.tar.gz</A></LI>
+<LI>
+<A HREF="http://www.cpan.org/modules/by-module/Digest/Digest-SHA1-2.01.tar.gz">Digest-SHA1-2.01.tar.gz</A></LI>
</UL>
<P>
<P>Copy the CPAN modules listed above to a convenient place on your computer. One good
# make test
# make install
# cd ..
+#
+# tar xvfz /usr/local/packages/Digest-SHA1-2.01.tar.gz
+# cd Digest-SHA1-2.01
+# perl Makefile.pl
+# make test
+# make install
+# cd ..
</PRE>
<P>
<P>Do not fall into the trap of thinking they're all the same, just because they
<P>I will assume that you have already downloaded the latest tarball of
the DXSpider software and are ready to install it. I am assuming version
-1.47 for this section but of course you would use the latest version.
+1.50 for this section but of course you would use the latest version.
<P>
<P>Login as root and create a user to run the cluster under. <B><I>UNDER
NO CIRCUMSTANCES USE ROOT AS THIS USER!</I></B>. I am going to use
<BLOCKQUOTE><CODE>
<PRE>
# cd ~sysop
-# tar xvfz spider-1.47.tar.gz
+# tar xvfz spider-1.50.tar.gz
# ln -s ~sysop/spider /spider
# groupadd -g 251 spider (or another number)
</PRE>
<BLOCKQUOTE><CODE>
<PRE>
$ ./cluster.pl
-DXSpider DX Cluster Version 1.47
+DXSpider DX Cluster Version 1.50
Copyright (c) 1998 Dirk Koopman G1TLH
loading prefixes ...
loading band data ...
<HTML>
<HEAD>
<META NAME="GENERATOR" CONTENT="SGML-Tools 1.0.9">
- <TITLE>The DXSpider Installation Manual v1.49: Linux quick installation guide</TITLE>
+ <TITLE>The DXSpider Installation Manual v1.50: Linux quick installation guide</TITLE>
<LINK HREF="installation-3.html" REL=next>
<LINK HREF="installation-1.html" REL=previous>
<LINK HREF="installation.html#toc2" REL=contents>
<HTML>
<HEAD>
<META NAME="GENERATOR" CONTENT="SGML-Tools 1.0.9">
- <TITLE>The DXSpider Installation Manual v1.49: Setting up the AX25 Utilities</TITLE>
+ <TITLE>The DXSpider Installation Manual v1.50: Setting up the AX25 Utilities</TITLE>
<LINK HREF="installation-4.html" REL=next>
<LINK HREF="installation-2.html" REL=previous>
<LINK HREF="installation.html#toc3" REL=contents>
rpms as standard. The other is
<A HREF="ftp://ftp.funet.fi/pub/ham/packet/linux/awznode/">AWZNode</A> by IZ5AWZ.
<P>
+<P>NB: The AX25 stuff in 2.4 kernels appears to have been broken until 2.4.18. I
+strongly suggest you get at least this kernel.
+<P>
<P>For 2.4 kernels you need these files...
<P>
<P>
<HTML>
<HEAD>
<META NAME="GENERATOR" CONTENT="SGML-Tools 1.0.9">
- <TITLE>The DXSpider Installation Manual v1.49: Configuration</TITLE>
+ <TITLE>The DXSpider Installation Manual v1.50: Configuration</TITLE>
<LINK HREF="installation-5.html" REL=next>
<LINK HREF="installation-3.html" REL=previous>
<LINK HREF="installation.html#toc4" REL=contents>
<HTML>
<HEAD>
<META NAME="GENERATOR" CONTENT="SGML-Tools 1.0.9">
- <TITLE>The DXSpider Installation Manual v1.49: Microsoft Windows Installation</TITLE>
+ <TITLE>The DXSpider Installation Manual v1.50: Microsoft Windows Installation</TITLE>
<LINK HREF="installation-6.html" REL=next>
<LINK HREF="installation-4.html" REL=previous>
<LINK HREF="installation.html#toc5" REL=contents>
<HTML>
<HEAD>
<META NAME="GENERATOR" CONTENT="SGML-Tools 1.0.9">
- <TITLE>The DXSpider Installation Manual v1.49: Installing the software</TITLE>
+ <TITLE>The DXSpider Installation Manual v1.50: Installing the software</TITLE>
<LINK HREF="installation-7.html" REL=next>
<LINK HREF="installation-5.html" REL=previous>
<LINK HREF="installation.html#toc6" REL=contents>
<HTML>
<HEAD>
<META NAME="GENERATOR" CONTENT="SGML-Tools 1.0.9">
- <TITLE>The DXSpider Installation Manual v1.49: General Information</TITLE>
+ <TITLE>The DXSpider Installation Manual v1.50: General Information</TITLE>
<LINK HREF="installation-6.html" REL=previous>
<LINK HREF="installation.html#toc7" REL=contents>
<link rel=stylesheet href="style.css" type="text/css" title="default stylesheet">
<HTML>
<HEAD>
<META NAME="GENERATOR" CONTENT="SGML-Tools 1.0.9">
- <TITLE>The DXSpider Installation Manual v1.49</TITLE>
+ <TITLE>The DXSpider Installation Manual v1.50</TITLE>
<LINK HREF="installation-1.html" REL=next>
Previous
Contents
<HR>
-<H1>The DXSpider Installation Manual v1.49</H1>
+<H1>The DXSpider Installation Manual v1.50</H1>
<H2>Iain Philipps, G0RDI (g0rdi@77hz.com) and
-Ian Maude, G0VGS, (g0vgs@gb7mbc.net)</H2>February 2002 revision 1.2
+Ian Maude, G0VGS, (g0vgs@gb7mbc.net)</H2>July 2002 revision 0.1
<P><HR>
<EM>A reference for SysOps of the DXSpider DXCluster program.</EM>
<HR>
<HR>
<H1>The DXSpider CVS Changes addendum </H1>
-<H2>Ian Maude, G0VGS, (ianmaude@btinternet.com)</H2>Version 0.1 March 2001
+<H2>Ian Maude, G0VGS, (ianmaude@btinternet.com)</H2>Version 1.50 July 2002
<P><HR>
<EM>A reference for CVS users of the DXSpider DXCluster program.</EM>
<HR>
<P>If you have any problems with a new CVS version please mail the support
-list or come and report on WW Convers channel 9000 or from a 44 host to
-sys2.pa4ab.ampr.org (44.137.44.16) port 6667 (IRC) and join #9000.
+list.
<P>
-<P>The latest CVS is version 1.47. There are major changes going on currently
-as the code is altered to allow DXSpider to be run under Microsoft Windows.
-<P>There is a separate file for the Windows installation in the /spider/html
-and /spider/txt directories so I will not include that here.
-<P>For Linux users, there are several steps to complete to update from
-version 1.46.
-<P>PLEASE READ ALL THE FOLLOWING BEFORE STARTING
+<P>The latest CVS is version 1.50 build 57.002. There are major changes going on currently
+as the code is being prepared for New Protocol.
<P>
-<UL>
-<LI>tar up your existing perl and cmd directories and put them somewhere
-safe so you can revert to the old version if necessary.</LI>
-<LI>Do a CVS update in the normal way (cvs update -d)</LI>
-<LI>cp /spider/perl/Listeners.pm to /spider/local and edit it as below</LI>
-<LI>comment out the spdlogin line in inetd.conf and 'killall -HUP inetd'</LI>
-<LI>"make" the client in /spider/src (just in case it has changed)</LI>
-<LI>restart the cluster and pray :-)</LI>
-</UL>
-<P>The Listeners.pm file looks something like this ...
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
-#
-# Copy this file to /spider/local and modify it to your requirements
-#
-#
-# This file specifies which local interfaces and ports you will be
-# listening on
-#
-# You can add as many as you like
-#
-
-package main;
-
-use vars qw(@listen);
-
-@listen = (
-# ["localhost", 7300],
-# ["foo.dxcluster.net", 7300],
- );
-
-1;
-</PRE>
-</CODE></BLOCKQUOTE>
-<P>Alter the hostnames and ports to reflect you setup. This file is only
-used for incoming telnet requests. You do not have to use hostnames, it
-is quite ok to use IP addresses and it is also a matter of choice whether
-or not you add the domain.
-<P>Here is an example of a working Listeners.pm file ..
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
-@listen = (
- ["localhost", 8000],
- ["sys2", 8000],
- ["apu", 8000],
- );
-</PRE>
-</CODE></BLOCKQUOTE>
-<P>Now all this is well and good if you have a static IP address. If your IP
-address is dynamic then one line will do, like this ...
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
-@listen = (
- ["0.0.0.0", 8000],
- );
-</PRE>
-</CODE></BLOCKQUOTE>
-<P>From this version, the file client.pl has ceased to be needed. In fact it
-has been removed. If you are still using client.pl in your ax25d.conf then
-replace it with /spider/src/client.
+<P>There are currently no addenda, please look to the /spider/Changes file for any
+small alterations.
<P>
<HR>
Next
<!-- Title information -->
-<title>The DXSpider Administration Manual v1.49</title>
+<title>The DXSpider Administration Manual v1.50</title>
<author>Ian Maude, G0VGS, (g0vgs@gb7mbc.net)</author>
-<date>February 2002 revision 1.3</date>
+<date>July 2002 revision 0.1</date>
<abstract>
A reference for SysOps of the DXSpider DXCluster program.
The <em>set/hops</em> command overrides any hops that you have set otherwise.
<p>
-You can set what hops have been set using the <em>show/hops</em> command.
+You can show what hops have been set using the <em>show/hops</em> command.
<sect1>Isolating networks
<P>
To force the cluster to reread the file use load/forward
+<P>
+NB: If a user tries to send mail to a bulletin address that does not exist
+in this file, they will get an error.
<sect1>The msg command
# startup script example
#
# set maximum no of spots allowed to 100
-# set/var $Spot::maxspots = 1
+# set/var $Spot::maxspots = 100
#
# Set registration on
# set/var $main::reqreg = 1
a user can request with the <em>sh/dx</em> command. Normally the default is
to give 10 spots unless the user specifies more. Without this line enabled,
the maximum a user can request is 100 spots. Depending on your link quality
-you may wish to enable more or less by specifying the number. If you simply
-uncomment the line, the maximum would be 1 spot!
+you may wish to enable more or less by specifying the number.
<P>
The other 2 options are dealt with more fully in the security section.
the setup. Many thanks to Fred Lloyd, the proprieter of
<htmlurl url="http://www.qrz.com" name="qrz.com"> for allowing this access.
+<sect1>Connecting logging programs
+
+<P>
+There appear to be very few logging programs out there that support telnet
+especially the popular ones like LogEQF, Turbolog etc. This can make it
+difficult to connect to your own cluster!
+The way to do it is to make the logging program think it has a TNC attached
+to a com port on the logging PC and 'push' a linux login out to it.
+This is achieved very simply by the use of <em>agetty</em>.
+
+<P>
+All that is required is to add a line in /etc/inittab to have the client
+ready for a connection on the com port of your choice. Remember that in
+Linux, the com ports start at ttyS0 for com1, ttyS1 for com2 etc.
+
+<tscreen><verb>
+c4:2345:respawn:/sbin/agetty -L 9600 ttyS1
+</verb></tscreen>
+
+<P>
+Add this after the standard runlevel lines in /etc/inittab. The above
+line works on ttyS1 (com2). Now as root, issue the command <em>telinit q</em>
+and it should be ready for connection. All that is required is a 3 wire
+serial lead (tx, rx and signal ground). Tell you logging program to use
+8n1 at 9600 baud and you should see a Linux login prompt. Login as normal
+and then telnet from there to the cluster.
+
+<sect>Java Web applet
+
+<P>
+In the spider tree will be a directory <em>spider-web</em>. This is a
+neat little java web applet that can be run from a website. The applet
+must run on the same machine as the cluster. The included README file is
+shown below.
+
+<P>
+I should comment here that the applet is precompiled, that is, ready to go.
+It was compiled using JDK1.3.1. If your version is earlier than this then it
+may not work. Should that be the case you need to recompile or update your
+JDK. To recompile do the following ...
+
+<tscreen><verb>
+cd /spider/spider-web
+rm *.class
+/usr/bin/javac spiderclient.java
+</verb></tscreen>
+
+<P>
+I have used /usr/bin/javac as an example, your path to javac may be different.
+
+<verb>
+Spider-WEB v0.6b
+
+Completely based on a clx web client written in Java by dl6dbh
+(ftp://clx.muc.de/pub/clx/clx-java_10130001.tgz)
+
+The webserver has to run on the same machine as your DxSpider software!
+
+It is assumed that you have Java installed. You need JDK1.3.1 at least.
+
+Installation instructions (Performed as root):
+
+Put all the files in the spider-web directory into a newly created directory
+under the DocumentRoot of your websever for instance 'client'. In my case
+this is: /home/httpd/html/client/ although ymmv. For Suse the correct
+path should be /usr/local/httpd/htdocs/client/ for example.
+
+Move spider.cgi to the cgi-bin directory of your webserver, in my case that is
+/home/httpd/cgi-bin/ although ymmv. For Suse the correct path should be
+/usr/local/httpd/cgi-bin/ for example.
+
+Change the permissions of the files to ensure they are correct, obviously you
+will need to use the correct path the the files according to your system:
+
+chmod 755 /home/httpd/html/cgi-bin/spider.cgi
+chmod -R 755 /home/httpd/html/client/
+
+By default the spider.cgi script should pick up your hostname (As long as this
+is set correctly). If it does not or your hostname differs from the name that
+you attach to the public address that you are using, then edit spider.cgi :
+
+# Uncomment and set the hostname manually here if the above fails.
+# $HOSTNAME = "gb7mbc.spoo.org" ;
+$PORT = "8000" ;
+
+'HOSTNAME' is the hostname of your cluster.
+
+'PORT' is the portnumber that you use to connect to your DxSpider via
+telnet (see Listeners.pm)
+
+NOTE: If you can start the console but cannot connect to the cluster from it,
+then it is possible that the machine you are on cannot resolve the hostname of
+your cluster machine. If this is the case, you need to set your hostname
+manually as above.
+
+You also need to set the $NODECALL variable. This prints the name of your
+choosing (probably your cluster callsign) on the html page.
+
+You now can connect to Spider-Web via http://yourserver/cgi-bin/spider.cgi
+</verb>
+
<sect>Security
<P>
It goes without saying that you should use this command CAREFULLY!
+<sect1>demonstrate (9)
+
+<P>
+<tt>
+<bf>demonstrate <call> <command></bf> Demonstrate a command to another user
+</tt>
+
+<P>
+This command is provided so that sysops can demonstrate commands to
+other users. It runs a command as though that user had typed it in and
+then sends the output to that user, together with the command that
+caused it.
+
+<tscreen><verb>
+ DEMO g7brn sh/dx iota oc209
+ DEMO g1tlh set/here
+</verb></tscreen>
+
+Note that this command is similar to SPOOF and will have the same side
+effects. Commands are run at the privilege of the user which is being
+demonstrated to.
<sect1>directory (0)
<!-- Title information -->
-<title>The DXSpider Installation Manual v1.49</title>
+<title>The DXSpider Installation Manual v1.50</title>
<author>Iain Philipps, G0RDI (g0rdi@77hz.com) and
Ian Maude, G0VGS, (g0vgs@gb7mbc.net)</author>
-<date>February 2002 revision 1.2</date>
+<date>July 2002 revision 0.1</date>
<abstract>
A reference for SysOps of the DXSpider DXCluster program.
<sect1>Introduction
<P>
-This section describes the installation of DX Spider v1.47 on a
+This section describes the installation of DX Spider v1.50 on a
<htmlurl url="http://www.redhat.com" name="RedHat"> Linux Distribution.
Wherever possible I will try to include differences for other distributions.
-I do not intend to try and cover the installation of Linux or the setup
-of the AX25 utilities. If you need help on this then read Iains original
-installation guide that comes with the Spider distribution.
<P>
I am assuming a general knowledge of Linux and its commands. You should
<item> <htmlurl url="http://www.cpan.org/modules/by-module/Net/Net-Telnet-3.02.tar.gz" name="Net-Telnet-3.02.tar.gz">
<item> <htmlurl url="http://www.cpan.org/modules/by-module/Curses/Curses-1.06.tar.gz" name="Curses-1.06.tar.gz">
<item> <htmlurl url="http://www.cpan.org/modules/by-module/Time/Time-HiRes-01.20.tar.gz" name="Time-HiRes-01.20.tar.gz">
+<item> <htmlurl url="http://www.cpan.org/modules/by-module/Digest/Digest-SHA1-2.01.tar.gz" name="Digest-SHA1-2.01.tar.gz">
</itemize>
<P>
# make test
# make install
# cd ..
+#
+# tar xvfz /usr/local/packages/Digest-SHA1-2.01.tar.gz
+# cd Digest-SHA1-2.01
+# perl Makefile.pl
+# make test
+# make install
+# cd ..
</verb>
<P>
<P>
I will assume that you have already downloaded the latest tarball of
the DXSpider software and are ready to install it. I am assuming version
-1.47 for this section but of course you would use the latest version.
+1.50 for this section but of course you would use the latest version.
<P>
Login as root and create a user to run the cluster under. <bf><it>UNDER
<tscreen><verb>
# cd ~sysop
-# tar xvfz spider-1.47.tar.gz
+# tar xvfz spider-1.50.tar.gz
# ln -s ~sysop/spider /spider
# groupadd -g 251 spider (or another number)
</verb></tscreen>
<tscreen><verb>
$ ./cluster.pl
-DXSpider DX Cluster Version 1.47
+DXSpider DX Cluster Version 1.50
Copyright (c) 1998 Dirk Koopman G1TLH
loading prefixes ...
loading band data ...
original by Tomi Manninen, OH2BNS as this is included in the ax25
rpms as standard. The other is <htmlurl url="ftp://ftp.funet.fi/pub/ham/packet/linux/awznode/" name="AWZNode"> by IZ5AWZ.
+<P>
+NB: The AX25 stuff in 2.4 kernels appears to have been broken until 2.4.18. I
+strongly suggest you get at least this kernel.
+
<P>
For 2.4 kernels you need these files...
<title>The DXSpider CVS Changes addendum
<author>Ian Maude, G0VGS, (ianmaude@btinternet.com)
-<date>Version 0.1 March 2001
+<date>Version 1.50 July 2002
<abstract>
A reference for CVS users of the DXSpider DXCluster program.
</abstract>
<P>
If you have any problems with a new CVS version please mail the support
-list or come and report on WW Convers channel 9000 or from a 44 host to
-sys2.pa4ab.ampr.org (44.137.44.16) port 6667 (IRC) and join #9000.
+list.
<P>
-The latest CVS is version 1.47. There are major changes going on currently
-as the code is altered to allow DXSpider to be run under Microsoft Windows.
+The latest CVS is version 1.50 build 57.002. There are major changes going on currently
+as the code is being prepared for New Protocol.
-There is a separate file for the Windows installation in the /spider/html
-and /spider/txt directories so I will not include that here.
-
-For Linux users, there are several steps to complete to update from
-version 1.46.
-
-PLEASE READ ALL THE FOLLOWING BEFORE STARTING
-
-<itemize>
-<item>tar up your existing perl and cmd directories and put them somewhere
-safe so you can revert to the old version if necessary.
-<item>Do a CVS update in the normal way (cvs update -d)
-<item>cp /spider/perl/Listeners.pm to /spider/local and edit it as below
-<item>comment out the spdlogin line in inetd.conf and 'killall -HUP inetd'
-<item>"make" the client in /spider/src (just in case it has changed)
-<item>restart the cluster and pray :-)
-</itemize>
-
-The Listeners.pm file looks something like this ...
-
-<tscreen><verb>
-#
-# Copy this file to /spider/local and modify it to your requirements
-#
-#
-# This file specifies which local interfaces and ports you will be
-# listening on
-#
-# You can add as many as you like
-#
-
-package main;
-
-use vars qw(@listen);
-
-@listen = (
-# ["localhost", 7300],
-# ["foo.dxcluster.net", 7300],
- );
-
-1;
-</verb></tscreen>
-
-Alter the hostnames and ports to reflect you setup. This file is only
-used for incoming telnet requests. You do not have to use hostnames, it
-is quite ok to use IP addresses and it is also a matter of choice whether
-or not you add the domain.
-
-Here is an example of a working Listeners.pm file ..
-
-<tscreen><verb>
-@listen = (
- ["localhost", 8000],
- ["sys2", 8000],
- ["apu", 8000],
- );
-</verb></tscreen>
-
-Now all this is well and good if you have a static IP address. If your IP
-address is dynamic then one line will do, like this ...
-
-<tscreen><verb>
-@listen = (
- ["0.0.0.0", 8000],
- );
-</verb></tscreen>
-
-From this version, the file client.pl has ceased to be needed. In fact it
-has been removed. If you are still using client.pl in your ax25d.conf then
-replace it with /spider/src/client.
+<P>
+There are currently no addenda, please look to the /spider/Changes file for any
+small alterations.
</article>
- The DXSpider Administration Manual v1.49
+ The DXSpider Administration Manual v1.50
Ian Maude, G0VGS, (g0vgs@gb7mbc.net)
- February 2002 revision 1.3
+ July 2002 revision 0.1
A reference for SysOps of the DXSpider DXCluster program.
______________________________________________________________________
6.6 Console.pl
6.7 Updating kepler data
6.8 The QRZ callbook
-
- 7. Security
-
- 7.1 Registration
- 7.2 Passwords
-
- 8. CVS
-
- 9. The DXSpider command set
-
- 9.1 accept/announce (0)
- 9.2 accept/announce (extended for sysops) (8)
- 9.3 accept/route (8)
- 9.4 accept/spots (0)
- 9.5 accept/spots (extended for sysops) (8)
- 9.6 accept/wcy (0)
- 9.7 accept/wcy (extended for sysops) (8)
- 9.8 accept/wwv (0)
- 9.9 accept/wwv (extended for sysops) (8)
- 9.10 announce (0)
- 9.11 announce full (0)
- 9.12 announce sysop (5)
- 9.13 apropos (0)
- 9.14 bye (0)
- 9.15 catchup (5)
- 9.16 clear/announce (8)
- 9.17 clear/route (8)
- 9.18 clear/spots (0)
- 9.19 clear/spots (extended for sysops) (8)
- 9.20 clear/wcy (0)
- 9.21 clear/wcy (extended for sysops) (8)
- 9.22 clear/wwv (0)
- 9.23 clear/wwv (extended for sysops) (8)
- 9.24 connect (5)
- 9.25 dbavail (0)
- 9.26 dbcreate (9)
- 9.27 dbimport (9)
- 9.28 dbremove (9)
- 9.29 dbshow (0)
- 9.30 debug (9)
- 9.31 delete/user (9)
- 9.32 directory (0)
- 9.33 directory (extended for sysops) (5)
- 9.34 disconnect (8)
- 9.35 dx (0)
- 9.36 export (9)
- 9.37 export_users (9)
- 9.38 filtering (0)
- 9.39 forward/latlong (8)
- 9.40 forward/opername (1)
- 9.41 help (0)
- 9.42 init (5)
- 9.43 kill (0)
- 9.44 kill (5)
- 9.45 kill full (5)
- 9.46 kill/expunge (6)
- 9.47 links (0)
- 9.48 load/aliases (9)
- 9.49 load/badmsg (9)
- 9.50 load/badwords (9)
- 9.51 load/bands (9)
- 9.52 load/cmd_cache (9)
- 9.53 load/forward (9)
- 9.54 load/messages (9)
- 9.55 load/prefixes (9)
- 9.56 merge (5)
- 9.57 msg (9)
- 9.58 pc (8)
- 9.59 ping (1)
- 9.60 rcmd (1)
- 9.61 read (0)
- 9.62 read (extended for sysops) (5)
- 9.63 reject/announce
- 9.64 reject/announce (extended for sysops) (8)
- 9.65 reject/route (8)
- 9.66 reject/spots (0)
- 9.67 reject/spots (extended for sysops) (8)
- 9.68 reject/wcy (0)
- 9.69 reject/wcy (extended for sysops) (8)
- 9.70 reject/wwv (0)
- 9.71 reject/wwv (extended for sysops) (8)
- 9.72 reply (0)
- 9.73 send (0)
- 9.74 set/address (0)
- 9.75 set/announce (0)
- 9.76 set/arcluster (5)
- 9.77 set/baddx (8)
- 9.78 set/badnode (6)
- 9.79 set/badspotter (8)
- 9.80 set/badword (8)
- 9.81 set/beep (0)
- 9.82 set/bbs (5)
- 9.83 set/clx (5)
- 9.84 set/debug (9)
- 9.85 set/dx (0)
- 9.86 set/dxgrid (0)
- 9.87 set/dxnet (5)
- 9.88 set/echo (0)
- 9.89 set/email (0)
- 9.90 set/here (0)
- 9.91 set/homenode (0)
- 9.92 set/hops (8)
- 9.93 set/isolate (9)
- 9.94 set/language (0)
- 9.95 set/location (0)
- 9.96 set/sys_location (9)
- 9.97 set/logininfo (0)
- 9.98 set/lockout (9)
- 9.99 set/name (0)
- 9.100 set/node (9)
- 9.101 set/obscount (9)
- 9.102 set/page (0)
- 9.103 set/password (0)
- 9.104 set/password (9)
- 9.105 set/pinginterval (9)
- 9.106 set/privilege (9)
- 9.107 set/spider (5)
- 9.108 set/sys_qra (9)
- 9.109 set/qra (0)
- 9.110 set/qth (0)
- 9.111 set/register (9)
- 9.112 set/talk (0)
- 9.113 set/wcy (0)
- 9.114 set/wwv (0)
- 9.115 set/wx (0)
- 9.116 show/baddx (1)
- 9.117 show/badnode (6)
- 9.118 show/badspotter (1)
- 9.119 show/badword (1)
- 9.120 show/configuration (0)
- 9.121 show/configuration/node (0)
- 9.122 show/connect (1)
- 9.123 show/date (0)
- 9.124 show/debug (9)
- 9.125 show/dx (0)
- 9.126 show/dxcc (0)
- 9.127 sh/dxstats (0)
- 9.128 show/files (0)
- 9.129 show/filter (0)
- 9.130 show/filter (extended for sysops) (5)
- 9.131 show/hfstats (0)
- 9.132 show/hftable (0)
- 9.133 show/hops (8)
- 9.134 show/isolate (1)
- 9.135 show/lockout (9)
- 9.136 show/log (8)
- 9.137 show/moon (0)
- 9.138 show/muf (0)
- 9.139 show/newconfiguration (0)
- 9.140 show/newconfiguration/node (0)
- 9.141 show/node (1)
- 9.142 show/prefix (0)
- 9.143 show/program (5)
- 9.144 show/qra (0)
- 9.145 show/qrz (0)
- 9.146 show/registered (9)
- 9.147 show/route (0)
- 9.148 show/satellite (0)
- 9.149 show/sun (0)
- 9.150 show/time (0)
- 9.151 show/vhfstats (0)
- 9.152 show/vhftable (0)
- 9.153 show/wcy (0)
- 9.154 show/wwv (0)
- 9.155 shutdown (5)
- 9.156 spoof (9)
- 9.157 stat/db (5)
- 9.158 stat/channel (5)
- 9.159 stat/msg (5)
- 9.160 stat/route_node (5)
- 9.161 stat/route_user (5)
- 9.162 stat/user (5)
- 9.163 sysop (0)
- 9.164 talk (0)
- 9.165 type (0)
- 9.166 who (0)
- 9.167 wx (0)
- 9.168 wx (enhanced for sysops) (5)
+ 6.9 Connecting logging programs
+
+ 7. Java Web applet
+
+ 8. Security
+
+ 8.1 Registration
+ 8.2 Passwords
+
+ 9. CVS
+
+ 10. The DXSpider command set
+
+ 10.1 accept/announce (0)
+ 10.2 accept/announce (extended for sysops) (8)
+ 10.3 accept/route (8)
+ 10.4 accept/spots (0)
+ 10.5 accept/spots (extended for sysops) (8)
+ 10.6 accept/wcy (0)
+ 10.7 accept/wcy (extended for sysops) (8)
+ 10.8 accept/wwv (0)
+ 10.9 accept/wwv (extended for sysops) (8)
+ 10.10 announce (0)
+ 10.11 announce full (0)
+ 10.12 announce sysop (5)
+ 10.13 apropos (0)
+ 10.14 bye (0)
+ 10.15 catchup (5)
+ 10.16 clear/announce (8)
+ 10.17 clear/route (8)
+ 10.18 clear/spots (0)
+ 10.19 clear/spots (extended for sysops) (8)
+ 10.20 clear/wcy (0)
+ 10.21 clear/wcy (extended for sysops) (8)
+ 10.22 clear/wwv (0)
+ 10.23 clear/wwv (extended for sysops) (8)
+ 10.24 connect (5)
+ 10.25 dbavail (0)
+ 10.26 dbcreate (9)
+ 10.27 dbimport (9)
+ 10.28 dbremove (9)
+ 10.29 dbshow (0)
+ 10.30 debug (9)
+ 10.31 delete/user (9)
+ 10.32 demonstrate (9)
+ 10.33 directory (0)
+ 10.34 directory (extended for sysops) (5)
+ 10.35 disconnect (8)
+ 10.36 dx (0)
+ 10.37 export (9)
+ 10.38 export_users (9)
+ 10.39 filtering (0)
+ 10.40 forward/latlong (8)
+ 10.41 forward/opername (1)
+ 10.42 help (0)
+ 10.43 init (5)
+ 10.44 kill (0)
+ 10.45 kill (5)
+ 10.46 kill full (5)
+ 10.47 kill/expunge (6)
+ 10.48 links (0)
+ 10.49 load/aliases (9)
+ 10.50 load/badmsg (9)
+ 10.51 load/badwords (9)
+ 10.52 load/bands (9)
+ 10.53 load/cmd_cache (9)
+ 10.54 load/forward (9)
+ 10.55 load/messages (9)
+ 10.56 load/prefixes (9)
+ 10.57 merge (5)
+ 10.58 msg (9)
+ 10.59 pc (8)
+ 10.60 ping (1)
+ 10.61 rcmd (1)
+ 10.62 read (0)
+ 10.63 read (extended for sysops) (5)
+ 10.64 reject/announce
+ 10.65 reject/announce (extended for sysops) (8)
+ 10.66 reject/route (8)
+ 10.67 reject/spots (0)
+ 10.68 reject/spots (extended for sysops) (8)
+ 10.69 reject/wcy (0)
+ 10.70 reject/wcy (extended for sysops) (8)
+ 10.71 reject/wwv (0)
+ 10.72 reject/wwv (extended for sysops) (8)
+ 10.73 reply (0)
+ 10.74 send (0)
+ 10.75 set/address (0)
+ 10.76 set/announce (0)
+ 10.77 set/arcluster (5)
+ 10.78 set/baddx (8)
+ 10.79 set/badnode (6)
+ 10.80 set/badspotter (8)
+ 10.81 set/badword (8)
+ 10.82 set/beep (0)
+ 10.83 set/bbs (5)
+ 10.84 set/clx (5)
+ 10.85 set/debug (9)
+ 10.86 set/dx (0)
+ 10.87 set/dxgrid (0)
+ 10.88 set/dxnet (5)
+ 10.89 set/echo (0)
+ 10.90 set/email (0)
+ 10.91 set/here (0)
+ 10.92 set/homenode (0)
+ 10.93 set/hops (8)
+ 10.94 set/isolate (9)
+ 10.95 set/language (0)
+ 10.96 set/location (0)
+ 10.97 set/sys_location (9)
+ 10.98 set/logininfo (0)
+ 10.99 set/lockout (9)
+ 10.100 set/name (0)
+ 10.101 set/node (9)
+ 10.102 set/obscount (9)
+ 10.103 set/page (0)
+ 10.104 set/password (0)
+ 10.105 set/password (9)
+ 10.106 set/pinginterval (9)
+ 10.107 set/privilege (9)
+ 10.108 set/spider (5)
+ 10.109 set/sys_qra (9)
+ 10.110 set/qra (0)
+ 10.111 set/qth (0)
+ 10.112 set/register (9)
+ 10.113 set/talk (0)
+ 10.114 set/wcy (0)
+ 10.115 set/wwv (0)
+ 10.116 set/wx (0)
+ 10.117 show/baddx (1)
+ 10.118 show/badnode (6)
+ 10.119 show/badspotter (1)
+ 10.120 show/badword (1)
+ 10.121 show/configuration (0)
+ 10.122 show/configuration/node (0)
+ 10.123 show/connect (1)
+ 10.124 show/date (0)
+ 10.125 show/debug (9)
+ 10.126 show/dx (0)
+ 10.127 show/dxcc (0)
+ 10.128 sh/dxstats (0)
+ 10.129 show/files (0)
+ 10.130 show/filter (0)
+ 10.131 show/filter (extended for sysops) (5)
+ 10.132 show/hfstats (0)
+ 10.133 show/hftable (0)
+ 10.134 show/hops (8)
+ 10.135 show/isolate (1)
+ 10.136 show/lockout (9)
+ 10.137 show/log (8)
+ 10.138 show/moon (0)
+ 10.139 show/muf (0)
+ 10.140 show/newconfiguration (0)
+ 10.141 show/newconfiguration/node (0)
+ 10.142 show/node (1)
+ 10.143 show/prefix (0)
+ 10.144 show/program (5)
+ 10.145 show/qra (0)
+ 10.146 show/qrz (0)
+ 10.147 show/registered (9)
+ 10.148 show/route (0)
+ 10.149 show/satellite (0)
+ 10.150 show/sun (0)
+ 10.151 show/time (0)
+ 10.152 show/vhfstats (0)
+ 10.153 show/vhftable (0)
+ 10.154 show/wcy (0)
+ 10.155 show/wwv (0)
+ 10.156 shutdown (5)
+ 10.157 spoof (9)
+ 10.158 stat/db (5)
+ 10.159 stat/channel (5)
+ 10.160 stat/msg (5)
+ 10.161 stat/route_node (5)
+ 10.162 stat/route_user (5)
+ 10.163 stat/user (5)
+ 10.164 sysop (0)
+ 10.165 talk (0)
+ 10.166 type (0)
+ 10.167 who (0)
+ 10.168 wx (0)
+ 10.169 wx (enhanced for sysops) (5)
______________________________________________________________________
networks, is probably all that you need.
+
The new functionality introduced in version 1.48 allows filtering the
node and user protocol frames on a "per interface" basis. We call this
route filtering. This is used instead of isolation.
"national" network. Here in the UK that means nodes from the UK and
Eire, in EU it is more complex as the networks there grew up in a more
intertwined way.
+ The generic commands are:-
- The generic commands are:-
-
reject/route node_default <filter_option>
or
rej/route node_default input call_dxcc 61,38 and not channel_dxcc 61,38
-
-
What this does is accept node and user information for our national
network from nodes that are in our national network, but rejects such
information from anyone else. Although it doesn't explicitly say so,
acc/route gb7baa input all
-
-
or restricting it quite a lot, in fact making it very nearly like an
isolated node, like this:-
The set/hops command overrides any hops that you have set otherwise.
- You can set what hops have been set using the show/hops command.
+ You can show what hops have been set using the show/hops command.
1.12. Isolating networks
To force the cluster to reread the file use load/forward
+ NB: If a user tries to send mail to a bulletin address that does not
+ exist in this file, they will get an error.
+
3.4. The msg command
-
-
-
MSG TO <msgno> <call> - change TO callsign to <call>
MSG FRom <msgno> <call> - change FROM callsign to <call>
MSG PRrivate <msgno> - set private flag
# startup script example
#
# set maximum no of spots allowed to 100
- # set/var $Spot::maxspots = 1
+ # set/var $Spot::maxspots = 100
#
# Set registration on
# set/var $main::reqreg = 1
Normally the default is to give 10 spots unless the user specifies
more. Without this line enabled, the maximum a user can request is
100 spots. Depending on your link quality you may wish to enable more
- or less by specifying the number. If you simply uncomment the line,
- the maximum would be 1 spot!
+ or less by specifying the number.
The other 2 options are dealt with more fully in the security section.
dbcreate <name>
+
To simply create a database locally, you just tell the command the
name of the database. This does not create the actual database, it
simply defines it to say that it exists.
proprieter of qrz.com for allowing this access.
- 7. Security
+ 6.9. Connecting logging programs
+
+ There appear to be very few logging programs out there that support
+ telnet especially the popular ones like LogEQF, Turbolog etc. This
+ can make it difficult to connect to your own cluster! The way to do
+ it is to make the logging program think it has a TNC attached to a com
+ port on the logging PC and 'push' a linux login out to it. This is
+ achieved very simply by the use of agetty.
+
+
+ All that is required is to add a line in /etc/inittab to have the
+ client ready for a connection on the com port of your choice.
+ Remember that in Linux, the com ports start at ttyS0 for com1, ttyS1
+ for com2 etc.
+
+
+
+ c4:2345:respawn:/sbin/agetty -L 9600 ttyS1
+
+
+
+
+
+ Add this after the standard runlevel lines in /etc/inittab. The above
+ line works on ttyS1 (com2). Now as root, issue the command telinit q
+ and it should be ready for connection. All that is required is a 3
+ wire serial lead (tx, rx and signal ground). Tell you logging program
+ to use 8n1 at 9600 baud and you should see a Linux login prompt.
+ Login as normal and then telnet from there to the cluster.
+
+
+ 7. Java Web applet
+
+ In the spider tree will be a directory spider-web. This is a neat
+ little java web applet that can be run from a website. The applet
+ must run on the same machine as the cluster. The included README file
+ is shown below.
+
+
+ I should comment here that the applet is precompiled, that is, ready
+ to go. It was compiled using JDK1.3.1. If your version is earlier
+ than this then it may not work. Should that be the case you need to
+ recompile or update your JDK. To recompile do the following ...
+
+
+
+ cd /spider/spider-web
+ rm *.class
+ /usr/bin/javac spiderclient.java
+
+
+
+
+
+ I have used /usr/bin/javac as an example, your path to javac may be
+ different.
+
+
+ Spider-WEB v0.6b
+
+ Completely based on a clx web client written in Java by dl6dbh
+ (ftp://clx.muc.de/pub/clx/clx-java_10130001.tgz)
+
+ The webserver has to run on the same machine as your DxSpider software!
+
+ It is assumed that you have Java installed. You need JDK1.3.1 at least.
+
+ Installation instructions (Performed as root):
+
+ Put all the files in the spider-web directory into a newly created directory
+ under the DocumentRoot of your websever for instance 'client'. In my case
+ this is: /home/httpd/html/client/ although ymmv. For Suse the correct
+ path should be /usr/local/httpd/htdocs/client/ for example.
+
+ Move spider.cgi to the cgi-bin directory of your webserver, in my case that is
+ /home/httpd/cgi-bin/ although ymmv. For Suse the correct path should be
+ /usr/local/httpd/cgi-bin/ for example.
+
+ Change the permissions of the files to ensure they are correct, obviously you
+ will need to use the correct path the the files according to your system:
+
+ chmod 755 /home/httpd/html/cgi-bin/spider.cgi
+ chmod -R 755 /home/httpd/html/client/
+
+ By default the spider.cgi script should pick up your hostname (As long as this
+ is set correctly). If it does not or your hostname differs from the name that
+ you attach to the public address that you are using, then edit spider.cgi :
+
+ # Uncomment and set the hostname manually here if the above fails.
+ # $HOSTNAME = "gb7mbc.spoo.org" ;
+ $PORT = "8000" ;
+
+
+ telnet (see Listeners.pm)
+
+ NOTE: If you can start the console but cannot connect to the cluster from it,
+ then it is possible that the machine you are on cannot resolve the hostname of
+ your cluster machine. If this is the case, you need to set your hostname
+ manually as above.
+
+ You also need to set the $NODECALL variable. This prints the name of your
+ choosing (probably your cluster callsign) on the html page.
+
+ You now can connect to Spider-Web via http://yourserver/cgi-bin/spider.cgi
+
+
+
+
+ 8. Security
From version 1.49 DXSpider has some additional security features.
These are not by any means meant to be exhaustive, however they do
security.
- 7.1. Registration
+ 8.1. Registration
The basic principle of registration is simple. If a user is not
registered by the sysop, then they have read-only access to the
/spider/scripts/startup. To read more on the startup file, see the
section on Information, files and useful programs.
+
To unregister a user use unset/register and to show the list of
registered users, use the command show/register.
- 7.2. Passwords
+ 8.2. Passwords
At the moment, passwords only affect users who login to a DXSpider
cluster node via telnet. If a user requires a password, they can
+
at the cluster prompt. This can also be added to the
/spider/scripts/startup file as above to make the change permanent.
- 8. CVS
+ 9. CVS
CVS stands for "Concurrent Versions System" and the CVS for DXSpider
is held at Sourceforge. This means that it is possible to update your
-
and your files will be updated. As above, remember to recompile the
"C" client if it has been updated (CVS will tell you) and restart if
any of the perl scripts have been altered or added, again, CVS will
You will find any changes documented in the /spider/Changes file.
- 9. The DXSpider command set
+ 10. The DXSpider command set
Below is a complete list of commands available from the cluster
prompt. Most maintenance tasks are automatic but there are some
is the permissions level needed to use the command.
- 9.1. accept/announce (0)
+ 10.1. accept/announce (0)
accept/announce [0-9] <pattern> Set an accept filter line for announce
-
-
-
-
-
-
-
-
-
- info <string> eg: iota or qsl
- by <prefixes> eg: G,M,2
- origin <prefixes>
- origin_dxcc <numbers> eg: 61,62 (from eg: sh/pre G)
- origin_itu <numbers>
- origin_zone <numbers>
- by_dxcc <numbers>
- by_itu <numbers>
- by_zone <numbers>
- channel <prefixes>
- wx 1 filter WX announces
- dest <prefixes> eg: 6MUK,WDX (distros)
+ info <string> eg: iota or qsl
+ by <prefixes> eg: G,M,2
+ origin <prefixes>
+ origin_dxcc <numbers> eg: 61,62 (from eg: sh/pre G)
+ origin_itu <numbers>
+ origin_zone <numbers>
+ by_dxcc <numbers>
+ by_itu <numbers>
+ by_zone <numbers>
+ channel <prefixes>
+ wx 1 filter WX announces
+ dest <prefixes> eg: 6MUK,WDX (distros)
- acc/ann by G,M,2
+
+ acc/ann by G,M,2
but this probably for advanced users...
- 9.2. accept/announce (extended for sysops) (8)
+ 10.2. accept/announce (extended for sysops) (8)
accept/announce <call> [input] [0-9]<pattern> Announce filter sysop
version
- 9.3. accept/route (8)
+
+
+ 10.3. accept/route (8)
accept/route <call> [0-9] <pattern> Set an 'accept' filter line for
routing
origin_zone <numbers>
-
-
-
some examples:-
- 9.4. accept/spots (0)
+ 10.4. accept/spots (0)
accept/spots [0-9] <pattern> Set an accept filter line for spots
passed onto the user. See HELP FILTERS for more info. Please read this
to understand how filters work - it will save a lot of grief later on.
-
You can use any of the following things in this line:-
- acc/spot 1 on hf/cw
- acc/spot 2 on vhf and (by_zone 14,15,16 or call_zone 14,15,16)
+
+ acc/spot 1 on hf/cw
+ acc/spot 2 on vhf and (by_zone 14,15,16 or call_zone 14,15,16)
but this probably for advanced users...
- 9.5. accept/spots (extended for sysops) (8)
+ 10.5. accept/spots (extended for sysops) (8)
accept/spots <call> [input] [0-9] <pattern> Spot filter sysop version
accept/spot user_default by G,M,2
- 9.6. accept/wcy (0)
+
+
+
+
+ 10.6. accept/wcy (0)
accept/wcy [0-9] <pattern> set an accept WCY filter
See HELP FILTER for information.
- 9.7. accept/wcy (extended for sysops) (8)
+ 10.7. accept/wcy (extended for sysops) (8)
accept/wcy <call> [input] [0-9] <pattern> WCY filter sysop version
- 9.8. accept/wwv (0)
+ 10.8. accept/wwv (0)
accept/wwv [0-9] <pattern> Set an accept WWV filter
-
-
-
-
-
-
- by <prefixes> eg: G,M,2
- origin <prefixes>
- origin_dxcc <numbers> eg: 61,62 (from eg: sh/pre G)
- origin_itu <numbers>
- origin_zone <numbers>
- by_dxcc <numbers>
- by_itu <numbers>
- by_zone <numbers>
- channel <prefixes>
+ by <prefixes> eg: G,M,2
+ origin <prefixes>
+ origin_dxcc <numbers> eg: 61,62 (from eg: sh/pre G)
+ origin_itu <numbers>
+ origin_zone <numbers>
+ by_dxcc <numbers>
+ by_itu <numbers>
+ by_zone <numbers>
+ channel <prefixes>
See HELP FILTER for information.
- 9.9. accept/wwv (extended for sysops) (8)
+ 10.9. accept/wwv (extended for sysops) (8)
accept/wwv <call> [input] [0-9] <pattern> WWV filter sysop version
+
This version allows a sysop to set a filter for a callsign as well as
the default for nodes and users eg:-
- 9.10. announce (0)
+ 10.10. announce (0)
announce <text> Send an announcement to local users
sysop will override set/noannounce.
- 9.11. announce full (0)
+ 10.11. announce full (0)
announce full <text> Send an announcement cluster wide
This command will send your announcement across the whole cluster
network.
- 9.12. announce sysop (5)
+
+
+
+ 10.12. announce sysop (5)
announce sysop <text>
Send an announcement to Sysops only
- 9.13. apropos (0)
+ 10.13. apropos (0)
apropos <string> Search the help database
print the names of all the commands that may be relevant.
- 9.14. bye (0)
+ 10.14. bye (0)
bye Exit from the cluster
This will disconnect you from the cluster
- 9.15. catchup (5)
+ 10.15. catchup (5)
catchup <node_call> All|[<msgno> ...] Mark a message as sent
Order is not important.
- 9.16. clear/announce (8)
+ 10.16. clear/announce (8)
clear/announce [input] <callsign> [0-9|all] Clear an announce filter
line
node_default or user_default.
- 9.17. clear/route (8)
+ 10.17. clear/route (8)
clear/route [input] ^lt;callsign> [0-9|all] Clear a route filter line
node_default or user_default.
- 9.18. clear/spots (0)
+ 10.18. clear/spots (0)
clear/spots [1|all] Clear a spot filter line
- acc/spot 1 on hf/cw
- acc/spot 2 on vhf and (by_zone 14,15,16 or call_zone 14,15,16)
+ acc/spot 1 on hf/cw
+ acc/spot 2 on vhf and (by_zone 14,15,16 or call_zone 14,15,16)
the filter will be completely removed.
- 9.19. clear/spots (extended for sysops) (8)
+ 10.19. clear/spots (extended for sysops) (8)
clear/spots [input] <callsign> [0-9|all] Clear a spot filter line
node_default or user_default.
- 9.20. clear/wcy (0)
+ 10.20. clear/wcy (0)
clear/wcy [1|all] Clear a WCY filter line
see CLEAR/SPOTS for a more detailed explanation.
- 9.21. clear/wcy (extended for sysops) (8)
+ 10.21. clear/wcy (extended for sysops) (8)
clear/wcy [input] <callsign> [0-9|all] Clear a WCY filter line
node_default or user_default.
- 9.22. clear/wwv (0)
+
+ 10.22. clear/wwv (0)
clear/wwv [1|all] Clear a WWV filter line
see CLEAR/SPOTS for a more detailed explanation.
- 9.23. clear/wwv (extended for sysops) (8)
+ 10.23. clear/wwv (extended for sysops) (8)
clear/wwv [input] <callsign> [0-9|all] Clear a WWV filter line
node_default or user_default.
- 9.24. connect (5)
+ 10.24. connect (5)
connect <callsign> Start a connection to another DX Cluster
cluster <callsign>.
- 9.25. dbavail (0)
+ 10.25. dbavail (0)
dbavail Show a list of all the databases in the system
defined in the system. It is also aliased to SHOW/COMMAND.
- 9.26. dbcreate (9)
+ 10.26. dbcreate (9)
dbcreate <name> Create a database entry
dbcreate <name> chain <name> [<name>..] Create a chained database
DBCREATE sdx_qsl chain sql_ad
+
No checking is done to see if the any of the chained databases exist,
in fact it is usually better to do the above statement first then do
each of the chained databases.
to allow
-
SH/BUCK g1tlh
to work as they may be used to.
databases. See DBSHOW for generic database enquiry
- 9.27. dbimport (9)
+ 10.27. dbimport (9)
dbimport <dbname> Import AK1A data into a database
oblast database held locally.
- 9.28. dbremove (9)
+ 10.28. dbremove (9)
dbremove <dbname> Delete a database
+
DBREMOVE will completely remove a database entry and also delete any
data file that is associated with it.
You have been warned.
- 9.29. dbshow (0)
+ 10.29. dbshow (0)
dbshow <dbname> <key> Display an entry, if it exists, in a database
but if he hasn't and the database really does exist (use DBAVAIL or
SHOW/COMMAND to find out) you can do the same thing with:
+
+
+
DBSHOW buck G1TLH
- 9.30. debug (9)
+ 10.30. debug (9)
debug Set the cluster program into debug mode
It will interrupt the cluster just after the debug command has
finished.
-
- 9.31. delete/user (9)
+ 10.31. delete/user (9)
delete/user <callsign> Delete a user from the User Database
It goes without saying that you should use this command CAREFULLY!
+ 10.32. demonstrate (9)
+
+ demonstrate <call> <command> Demonstrate a command to another user
+
+
+ This command is provided so that sysops can demonstrate commands to
+ other users. It runs a command as though that user had typed it in and
+ then sends the output to that user, together with the command that
+ caused it.
+
+
+
+ DEMO g7brn sh/dx iota oc209
+ DEMO g1tlh set/here
+
+
+
+
+ Note that this command is similar to SPOOF and will have the same side
+ effects. Commands are run at the privilege of the user which is being
+ demonstrated to.
- 9.32. directory (0)
+
+ 10.33. directory (0)
directory List messages
directory own List your own messages
-
-
- DIR TO G1TLH 5
- or
- DIR SUBJECT IOTA 200-250
-
+ DIR TO G1TLH 5
+ or
+ DIR SUBJECT IOTA 200-250
- 9.33. directory (extended for sysops) (5)
+ 10.34. directory (extended for sysops) (5)
Works just like the user command except that sysops can see ALL
messages.
- 9.34. disconnect (8)
+ 10.35. disconnect (8)
disconnect <call> [<call> ...] Disconnect a user or node
Disconnect any <call> connected locally
- 9.35. dx (0)
+ 10.36. dx (0)
dx [by <call>] <freq> <call> <remarks> Send a DX spot
-
- DX by G1TLH FR0G 144.600 he isn't on the cluster
+ DX by G1TLH FR0G 144.600 he isn't on the cluster
The <freq> is compared against the available bands set up in the
cluster. See SHOW/BANDS for more information.
-
- 9.36. export (9)
+ 10.37. export (9)
export <msgno> <filename> Export a message to a file
EXPORT 2345 /tmp/a
- 9.37. export_users (9)
+ 10.38. export_users (9)
export_users [<filename>] Export the users database to ascii
check is made on the filename (if any) that you specify.
- 9.38. filtering (0)
+ 10.39. filtering (0)
filtering Filtering things in DXSpider
The next filter line lets through just VHF/UHF spots from EU.
- 9.39. forward/latlong (8)
+ 10.40. forward/latlong (8)
forward/latlong <node_call> Send latitude and longitude information to
another cluster
so it is not recommended on slow links.
- 9.40. forward/opername (1)
+ 10.41. forward/opername (1)
forward/opername <call> Send out information on this <call> to all
clusters
available.
- 9.41. help (0)
+ 10.42. help (0)
help <cmd> Get help on a command
+
All commands can be abbreviated, so SHOW/DX can be abbreviated to
SH/DX, ANNOUNCE can be shortened to AN and so on.
commands to look at with HELP.
- 9.42. init (5)
+ 10.43. init (5)
init <node call> Re-initialise a link to an AK1A compatible node
Best of luck - you will need it.
- 9.43. kill (0)
+ 10.44. kill (0)
kill <msgno> [<msgno> ..] Delete a message from the local system
the sysop).
- 9.44. kill (5)
+ 10.45. kill (5)
kill <msgno> [<msgno> ...] Remove or erase a message from the system
kill from <call> Remove all messages from a callsign
As a sysop you can kill any message on the system.
- 9.45. kill full (5)
+ 10.46. kill full (5)
kill full <msgno> [<msgno>] Delete a message from the whole cluster
same subject will be deleted. Beware!
-
-
- 9.46. kill/expunge (6)
+ 10.47. kill/expunge (6)
kill/expunge <msgno> [<msgno>..]Expunge a message
message for deletion. The actual deletion only happens later (usually
two days later).
+
The KILL EXPUNGE command causes the message to be truly deleted more
or less immediately.
- 9.47. links (0)
+ 10.48. links (0)
links Show which nodes are physically connected
- 9.48. load/aliases (9)
+ 10.49. load/aliases (9)
load/aliases Reload the command alias table
running in order for the changes to take effect.
- 9.49. load/badmsg (9)
+ 10.50. load/badmsg (9)
load/badmsg Reload the bad message table
deleted on receipt.
- 9.50. load/badwords (9)
+ 10.51. load/badwords (9)
load/badwords Reload the bad words table
ignored.
- 9.51. load/bands (9)
+ 10.52. load/bands (9)
load/bands Reload the band limits table
+
Reload the /spider/data/bands.pl file if you have changed it manually
whilst the cluster is running.
- 9.52. load/cmd_cache (9)
+ 10.53. load/cmd_cache (9)
load/cmd_cache Reload the automatic command cache
-
Normally, if you change a command file in the cmd or local_cmd tree it
will automatially be picked up by the cluster program. Sometimes it
can get confused if you are doing a lot of moving commands about or
was just after a cluster restart.
- 9.53. load/forward (9)
+ 10.54. load/forward (9)
load/forward Reload the msg forwarding routing table
whilst the cluster is running.
- 9.54. load/messages (9)
+ 10.55. load/messages (9)
load/messages Reload the system messages file
unknown message 'xxxx' in lang 'en'
- 9.55. load/prefixes (9)
+ 10.56. load/prefixes (9)
load/prefixes Reload the prefix table
manually whilst the cluster is running.
- 9.56. merge (5)
+ 10.57. merge (5)
merge <node> [<no spots>/<no wwv>] Ask for the latest spots and WWV
data).
- 9.57. msg (9)
+ 10.58. msg (9)
msg <cmd> <msgno> [data ...] Alter various message parameters
+
Alter message parameters like To, From, Subject, whether private or
bulletin or return receipt (RR) is required or whether to keep this
message from timing out.
- MSG TO <msgno> <call> - change TO callsign to <call>
- MSG FRom <msgno> <call> - change FROM callsign to <call>
- MSG PRrivate <msgno> - set private flag
- MSG NOPRrivate <msgno> - unset private flag
- MSG RR <msgno> - set RR flag
- MSG NORR <msgno> - unset RR flag
- MSG KEep <msgno> - set the keep flag (message won't be deleted ever)
- MSG NOKEep <msgno> - unset the keep flag
- MSG SUbject <msgno> <new> - change the subject to <new>
- MSG WAittime <msgno> - remove any waitting time for this message
- MSG NOREad <msgno> - mark message as unread
- MSG REad <msgno> - mark message as read
- MSG QUeue - queue any outstanding bulletins
- MSG QUeue 1 - queue any outstanding private messages
+
+
+ MSG TO <msgno> <call> - change TO callsign to <call>
+ MSG FRom <msgno> <call> - change FROM callsign to <call>
+ MSG PRrivate <msgno> - set private flag
+ MSG NOPRrivate <msgno> - unset private flag
+ MSG RR <msgno> - set RR flag
+ MSG NORR <msgno> - unset RR flag
+ MSG KEep <msgno> - set the keep flag (message won't be deleted ever)
+ MSG NOKEep <msgno> - unset the keep flag
+ MSG SUbject <msgno> <new> - change the subject to <new>
+ MSG WAittime <msgno> - remove any waitting time for this message
+ MSG NOREad <msgno> - mark message as unread
+ MSG REad <msgno> - mark message as read
+ MSG QUeue - queue any outstanding bulletins
+ MSG QUeue 1 - queue any outstanding private messages
This will display more information on the message than DIR does.
- 9.58. pc (8)
+ 10.59. pc (8)
pc <call> <text> Send text (eg PC Protocol) to <call>
pc G1TLH Try doing that properly!!!
- 9.59. ping (1)
+ 10.60. ping (1)
ping <node> Check the link quality between nodes
-
-
-
- 9.60. rcmd (1)
+ 10.61. rcmd (1)
rcmd <node call> <cmd> Send a command to another DX cluster
This command allows you to send nearly any command to another DX
Cluster node that is connected to the system.
+
Whether you get any output is dependant on a) whether the other system
knows that the node callsign of this cluster is in fact a node b)
whether the other system is allowing RCMDs from this node and c)
whether you have permission to send this command at all.
- 9.61. read (0)
+ 10.62. read (0)
read Read the next unread personal message addressed to you
read <msgno> Read the specified message
- 9.62. read (extended for sysops) (5)
+ 10.63. read (extended for sysops) (5)
read <msgno> Read a message on the system
As a sysop you may read any message on the system
- 9.63. reject/announce
+ 10.64. reject/announce
reject/announce [0-9] <pattern> Set a reject filter for announce
-
some examples:-
but this probably for advanced users...
- 9.64. reject/announce (extended for sysops) (8)
+ 10.65. reject/announce (extended for sysops) (8)
reject/announce <call> [input] [0-9] <pattern> Announce filter sysop
version
- 9.65. reject/route (8)
+ 10.66. reject/route (8)
reject/route <call> [0-9] <pattern> Set an 'reject' filter line for
routing
origin_itu <numbers>
origin_zone <numbers>
+
+
+
+
some examples:-
- rej/route gb7djk call_dxcc 61,38 (everything except UK+EIRE nodes)
+
+ rej/route gb7djk call_dxcc 61,38 (everything except UK+EIRE nodes)
- 9.66. reject/spots (0)
+ 10.67. reject/spots (0)
reject/spots [0-9] <pattern> Set a reject filter line for spots
rej/spot 1 on hf
rej/spot 2 on vhf and not (by_zone 14,15,16 or call_zone 14,15,16)
+
+
+
+
You can use the tag 'all' to reject everything eg:
but this probably for advanced users...
- 9.67. reject/spots (extended for sysops) (8)
+ 10.68. reject/spots (extended for sysops) (8)
reject/spots <call> [input] [0-9] <pattern> Reject spot filter sysop
version
- 9.68. reject/wcy (0)
+ 10.69. reject/wcy (0)
reject/wcy [0-9] <pattern> Set a reject WCY filter
- 9.69. reject/wcy (extended for sysops) (8)
+ 10.70. reject/wcy (extended for sysops) (8)
reject/wcy <call> [input] [0-9] <pattern> WCY reject filter sysop
version
reject/wcy gb7djk all
- 9.70. reject/wwv (0)
+ 10.71. reject/wwv (0)
reject/wwv [0-9] <pattern> Set a reject WWV filter
See HELP FILTER for information.
- 9.71. reject/wwv (extended for sysops) (8)
+ 10.72. reject/wwv (extended for sysops) (8)
reject/wwv <call> [input] [0-9] <pattern> WWV reject filter sysop
version
reject/wwv user_default by W
- 9.72. reply (0)
+ 10.73. reply (0)
reply Reply (privately) to the last message that you have read
reply <msgno> Reply (privately) to the specified message
further details)
- 9.73. send (0)
+ 10.74. send (0)
send <call> [<call> ...] Send a message to one or more callsigns
send RR <call> Send a message and ask for a read receipt
is an alias for SEND PRIVATE
- 9.74. set/address (0)
+ 10.75. set/address (0)
set/address <your_address> Record your postal address
Literally, record your address details on the cluster.
- 9.75. set/announce (0)
+ 10.76. set/announce (0)
set/announce Allow announce messages
Allow announce messages to arrive at your terminal.
- 9.76. set/arcluster (5)
+ 10.77. set/arcluster (5)
set/arcluster <node_call> [<node_call> ...] Make the node_call an AR-
Cluster type node
Set the node_call as an AR-Cluster type node
- 9.77. set/baddx (8)
+ 10.78. set/baddx (8)
set/baddx <call> Stop words we do not wish to see in the callsign
field of a dx spot being propagated
- 9.78. set/badnode (6)
+ 10.79. set/badnode (6)
set/badnode <node_call> Stop spots from this node_call being
propagated
FILTERing.
- 9.79. set/badspotter (8)
+ 10.80. set/badspotter (8)
set/badspotter <call> Stop spots from this callsign being propagated
FILTERing.
- 9.80. set/badword (8)
+ 10.81. set/badword (8)
set/badword <word> Stop things with this word being propogated
- 9.81. set/beep (0)
+ 10.82. set/beep (0)
set/beep Add beeps to terminal messages
Add a beep to DX and other terminal messages.
- 9.82. set/bbs (5)
+ 10.83. set/bbs (5)
set/bbs <call> [<call>..]Make <call> a BBS
- 9.83. set/clx (5)
+ 10.84. set/clx (5)
set/clx <node_call> [<node_call> ...] Make the node_call a CLX type
node
Set the node_call as a CLX type node
- 9.84. set/debug (9)
+ 10.85. set/debug (9)
set/debug <name> Add a debug level to the debug set
You can remove a debug level with unset/debug <name>
- 9.85. set/dx (0)
+ 10.86. set/dx (0)
set/dxAllow DX messages to arrive at your terminal
You can stop DX messages with the unset/dx command
- 9.86. set/dxgrid (0)
+ 10.87. set/dxgrid (0)
set/dxgridAllow grid squares on the end of DX messages
to remove the grid squares.
- 9.87. set/dxnet (5)
+ 10.88. set/dxnet (5)
set/dxnet <node_call> [<node_call> ...] Make the node_call a DXNet
type node
Set the node_call as a DXNet type node
- 9.88. set/echo (0)
+ 10.89. set/echo (0)
set/echo Make the cluster echo your input
YOU DO NOT NEED TO USE THIS COMMAND IF YOU ARE CONNECTED VIA AX25.
- 9.89. set/email (0)
+ 10.90. set/email (0)
set/email <email_address> Set email address(es) and forward your
personals
UNSET/EMAIL
- 9.90. set/here (0)
+ 10.91. set/here (0)
set/here Set the here flag
brackets around your callsign to indicate you are not available.
- 9.91. set/homenode (0)
+ 10.92. set/homenode (0)
set/homenode <node_call> Set your home cluster
- 9.92. set/hops (8)
+ 10.93. set/hops (8)
set/hops <node_call> ann|spots|wwv|wcy <n> Set hop count
creates a filter and works in conjunction with the filter system.
- 9.93. set/isolate (9)
+ 10.94. set/isolate (9)
set/isolate <node call> Isolate a node from the rest of the network
You can remove the isolation with the command unset/isolate.
- 9.94. set/language (0)
+ 10.95. set/language (0)
set/language <language> Set the language you wish to use
Currently the languages available are en (English) and nl (Dutch).
- 9.95. set/location (0)
+ 10.96. set/location (0)
set/location <lat and long> Set your latitude and longitude
- 9.96. set/sys_location (9)
+ 10.97. set/sys_location (9)
set/sys_location <lat & long> Set your cluster latitude and longitude
- 9.97. set/logininfo (0)
+ 10.98. set/logininfo (0)
set/logininfo Show logins and logouts of nodes and users
- 9.98. set/lockout (9)
+ 10.99. set/lockout (9)
set/lockout <call> Stop a callsign connecting to the cluster
allow the user to connect again, use the unset/lockout command.
- 9.99. set/name (0)
+ 10.100. set/name (0)
set/name <your_name> Set your name
- 9.100. set/node (9)
+ 10.101. set/node (9)
set/node <call> [<call> ...] Make the callsign an AK1A cluster
- 9.101. set/obscount (9)
+ 10.102. set/obscount (9)
set/obscount <count> <node call> Set the 'pump-up' obsolescence
counter
minutes, it is disconnected.
- 9.102. set/page (0)
+ 10.103. set/page (0)
set/page <n> Set the number of lines per page
The setting is stored in your user profile.
- 9.103. set/password (0)
+ 10.104. set/password (0)
set/password Set your own password
type, depending on the type of telnet client you have.
- 9.104. set/password (9)
+ 10.105. set/password (9)
set/password <callsign> <string> Set a users password
password.
- 9.105. set/pinginterval (9)
+ 10.106. set/pinginterval (9)
set/pinginterval <time> <node call> Set the ping time to neighbouring
nodes
for more information.
- 9.106. set/privilege (9)
+ 10.107. set/privilege (9)
set/privilege <n> <call> [<call> ...] Set the privilege level on a
call
- 9.107. set/spider (5)
+ 10.108. set/spider (5)
set/spider <node_call> [<node_call> ...] Make the node_call a DXSpider
type node
Set the node_call as a DXSpider type node
- 9.108. set/sys_qra (9)
+ 10.109. set/sys_qra (9)
set/sys_qra <locator> Set your cluster QRA locator
- 9.109. set/qra (0)
+ 10.110. set/qra (0)
set/qra <locator> Set your QRA locator
- 9.110. set/qth (0)
+ 10.111. set/qth (0)
set/qth <your QTH> Set your QTH
- 9.111. set/register (9)
+ 10.112. set/register (9)
set/register <call> Mark a user as registered
To unset a user use the 'unset/register' command
- 9.112. set/talk (0)
+ 10.113. set/talk (0)
set/talk Allow talk messages to be seen at your console
talks with the unset/talk command.
- 9.113. set/wcy (0)
+ 10.114. set/wcy (0)
set/wcy Allow WCY messages to be seen at your console
WCY messages with the unset/wcy command.
- 9.114. set/wwv (0)
+ 10.115. set/wwv (0)
set/wwv Allow WWV messages to be seen at your console
WWV messages with the unset/wwv command.
- 9.115. set/wx (0)
+ 10.116. set/wx (0)
set/wx Allow WX messages to be seen at your console
WX messages with the unset/wx command.
- 9.116. show/baddx (1)
+ 10.117. show/baddx (1)
show/baddxShow all the bad dx calls in the system
information.
- 9.117. show/badnode (6)
+ 10.118. show/badnode (6)
show/badnode Show all the bad nodes in the system
more information.
- 9.118. show/badspotter (1)
+ 10.119. show/badspotter (1)
show/badspotter Show all the bad spotters in the system
SET/BADSPOTTER for more information.
- 9.119. show/badword (1)
+ 10.120. show/badword (1)
show/badword Show all the bad words in the system
information.
- 9.120. show/configuration (0)
+ 10.121. show/configuration (0)
show/configuration [<node>] Show all visible nodes and their users
BE WARNED: the list that is returned can be VERY long
- 9.121. show/configuration/node (0)
+ 10.122. show/configuration/node (0)
show/configuration/node Show all the nodes connected
connected.
- 9.122. show/connect (1)
+ 10.123. show/connect (1)
show/connect Show all the active connections
the node. This command gives slightly more information than WHO.
- 9.123. show/date (0)
+ 10.124. show/date (0)
show/date [<prefix>|<callsign>] Show the local time
including DST) at the prefixes or callsigns that you specify.
- 9.124. show/debug (9)
+ 10.125. show/debug (9)
show/debug Show what levels of debug you are logging
- 9.125. show/dx (0)
+ 10.126. show/dx (0)
show/dx [options] interrogate the spot database
- 9.126. show/dxcc (0)
+ 10.127. show/dxcc (0)
show/dxcc <prefix> Interrogate the spot database by country
- 9.127. sh/dxstats (0)
+ 10.128. sh/dxstats (0)
sh/dxstats Show the DX Statistics for last 31 days
- 9.128. show/files (0)
+ 10.129. show/files (0)
show/files [<filearea> [<string>]] List the contents of a filearea
See also TYPE - to see the contents of a file.
- 9.129. show/filter (0)
+ 10.130. show/filter (0)
show/filter Show the filters you have set
displays all the filters set - for all the various categories.
- 9.130. show/filter (extended for sysops) (5)
+ 10.131. show/filter (extended for sysops) (5)
show/filter <callsign> Show the filters set by <callsign>
A sysop can look at any filters that have been set.
- 9.131. show/hfstats (0)
+ 10.132. show/hfstats (0)
show/hfstats Show the HF DX Statistics for last 31 days
Show the HF DX spots breakdown by band for the last 31 days
- 9.132. show/hftable (0)
+ 10.133. show/hftable (0)
show/hftable Show the HF DX Spotter Table for your country
Show the HF DX Spotter table for your country for the last 31 days
- 9.133. show/hops (8)
+ 10.134. show/hops (8)
show/hops <node_call> [ann|spots|wcy|wwv|] Show the hop counts for a
node
the categories will be listed.
- 9.134. show/isolate (1)
+ 10.135. show/isolate (1)
show/isolate Show a list of isolated nodes
Show which nodes are currently set to be isolated.
- 9.135. show/lockout (9)
+ 10.136. show/lockout (9)
show/lockout Show a list of excluded callsigns
cluster locally with the set/lockout command
- 9.136. show/log (8)
+ 10.137. show/log (8)
show/log [<callsign>] Show excerpts from the system log
show output from the log associated with that callsign.
- 9.137. show/moon (0)
+ 10.138. show/moon (0)
show/moon [<prefix>|<callsign>] Show moon rise and set times
- 9.138. show/muf (0)
+ 10.139. show/muf (0)
show/muf <prefix> [<hours>][long] Show the likely propagation to
<prefix>
terrible accurate, but it is included for completeness.
- 9.139. show/newconfiguration (0)
+ 10.140. show/newconfiguration (0)
show/newconfiguration [<node>] Show all the nodes and users visible
BE WARNED: the list that is returned can be VERY long
- 9.140. show/newconfiguration/node (0)
+ 10.141. show/newconfiguration/node (0)
show/newconfiguration/node Show all the nodes connected locally
Show all the nodes connected to this node in the new format.
- 9.141. show/node (1)
+ 10.142. show/node (1)
show/node [<node_call> ...] Show the type and version number of nodes
the non-user callsigns known to the system will be displayed.
- 9.142. show/prefix (0)
+ 10.143. show/prefix (0)
show/prefix <callsign> Interrogate the prefix database
- 9.143. show/program (5)
+ 10.144. show/program (5)
show/program Show the locations of all the included program modules
from.
- 9.144. show/qra (0)
+ 10.145. show/qra (0)
show/qra <locator> [<locator>] Show the distance between locators
show/qra <lat> <long> Convert latitude and longitude to a locator
- 9.145. show/qrz (0)
+ 10.146. show/qrz (0)
show/qrz <callsign> Show any callbook details on a callsign
provided for users of this software by http://www.qrz.com
- 9.146. show/registered (9)
+ 10.147. show/registered (9)
show/registered [<prefix>[ Show the registered users
- 9.147. show/route (0)
+ 10.148. show/route (0)
show/route <callsign> Show the route to <callsign>
- 9.148. show/satellite (0)
+ 10.149. show/satellite (0)
show/satellite <name> [<hours> <interval>] Show satellite tracking
data
- 9.149. show/sun (0)
+ 10.150. show/sun (0)
show/sun [<prefix>|<callsign>] Show sun rise and set times
- 9.150. show/time (0)
+ 10.151. show/time (0)
show/time [<prefix>|<callsign>] Show the local time
including DST) at the prefixes or callsigns that you specify.
- 9.151. show/vhfstats (0)
+ 10.152. show/vhfstats (0)
show/vhfstats Show the VHF DX Statistics for last 31 days
Show the VHF DX spots breakdown by band for the last 31 days
- 9.152. show/vhftable (0)
+ 10.153. show/vhftable (0)
show/vhftable Show the VHF DX Spotter Table for your country
Show the VHF DX Spotter table for your country for the last 31 days
- 9.153. show/wcy (0)
+ 10.154. show/wcy (0)
show/wcy Show the last 10 WCY broadcasts
show/wcy <n> Show the last <n> WCY broadcasts
system
- 9.154. show/wwv (0)
+ 10.155. show/wwv (0)
show/wwv Show the last 10 WWV broadcasts
show/wwv <n> Show the last <n> WWV broadcasts
- 9.155. shutdown (5)
+ 10.156. shutdown (5)
shutdown Shutdown the cluster
set to respawn in /etc/inittab it will of course restart.
- 9.156. spoof (9)
+ 10.157. spoof (9)
spoof <callsign> <command> Run commands as another user
like home_node for example.
- 9.157. stat/db (5)
+ 10.158. stat/db (5)
stat/db <dbname> Show the status of a database
other than a sysop.
- 9.158. stat/channel (5)
+ 10.159. stat/channel (5)
stat/channel <callsign> Show the status of a channel on the cluster
Only the fields that are defined (in perl term) will be displayed.
- 9.159. stat/msg (5)
+ 10.160. stat/msg (5)
stat/msg <msgno> Show the status of a message
displayed.
- 9.160. stat/route_node (5)
+ 10.161. stat/route_node (5)
stat/route_node <callsign> Show the data in a Route::Node object
- 9.161. stat/route_user (5)
+ 10.162. stat/route_user (5)
stat/route_user <callsign> Show the data in a Route::User object
- 9.162. stat/user (5)
+ 10.163. stat/user (5)
stat/user <callsign> Show the full status of a user
Only the fields that are defined (in perl term) will be displayed.
- 9.163. sysop (0)
+ 10.164. sysop (0)
sysop Regain your privileges if you login remotely
case sensitive.
- 9.164. talk (0)
+ 10.165. talk (0)
talk <callsign> Enter talk mode with <callsign>
talk <callsign> <text> Send a text message to <callsign>
- 9.165. type (0)
+ 10.166. type (0)
type <filearea>/<name> Look at a file in one of the fileareas
content.
- 9.166. who (0)
+ 10.167. who (0)
who Show who is physically connected locally
what sort of connection they have
- 9.167. wx (0)
+ 10.168. wx (0)
wx <text> Send a weather message to local users
wx full <text> Send a weather message to all cluster users
extreme that may indicate enhanced conditions
- 9.168. wx (enhanced for sysops) (5)
+ 10.169. wx (enhanced for sysops) (5)
wx sysop <text> Send a weather message to other clusters only
- The DXSpider Installation Manual v1.49
+ The DXSpider Installation Manual v1.50
Iain Philipps, G0RDI (g0rdi@77hz.com) and Ian Maude, G0VGS,
(g0vgs@gb7mbc.net)
- February 2002 revision 1.2
+ July 2002 revision 0.1
A reference for SysOps of the DXSpider DXCluster program.
______________________________________________________________________
1.1. Introduction
- This section describes the installation of DX Spider v1.47 on a RedHat
+ This section describes the installation of DX Spider v1.50 on a RedHat
Linux Distribution. Wherever possible I will try to include
- differences for other distributions. I do not intend to try and cover
- the installation of Linux or the setup of the AX25 utilities. If you
- need help on this then read Iains original installation guide that
- comes with the Spider distribution.
-
-
+ differences for other distributions.
I am assuming a general knowledge of Linux and its commands. You
should know how to use tar and how to edit files using your favourite
editor.
o Time-HiRes-01.20.tar.gz
+ o Digest-SHA1-2.01.tar.gz
+
Copy the CPAN modules listed above to a convenient place on your
computer. One good place would be /usr/local/packages, and the
+
+
+
# make test
# make install
# cd ..
+ #
+ # tar xvfz /usr/local/packages/Digest-SHA1-2.01.tar.gz
+ # cd Digest-SHA1-2.01
+ # perl Makefile.pl
+ # make test
+ # make install
+ # cd ..
I will assume that you have already downloaded the latest tarball of
the DXSpider software and are ready to install it. I am assuming
- version 1.47 for this section but of course you would use the latest
+ version 1.50 for this section but of course you would use the latest
version.
your own choice.
+
# adduser -m sysop
# cd ~sysop
- # tar xvfz spider-1.47.tar.gz
+ # tar xvfz spider-1.50.tar.gz
# ln -s ~sysop/spider /spider
# groupadd -g 251 spider (or another number)
The next step is to set the permissions on the Spider directory tree
and files ....
+
+
# chown -R sysop.spider spider
# find . -type d -exec chmod 2775 {} \;
# find . -type f -exec chmod 775 {} \;
-
This is the call sign of your cluster. If you use an SSID then
include it here also.
+
+
This is the sysop user callsign, normally your own.
use it though it has to be "made". CD to /spider/src and type make.
You should see the output on your screen and hopefully now have a
small C program called client. Leave it in this directory.
-
-
-
1.6. Starting up for the first time
We can now bring spider up for the first time and see if all is well
-
- $ ./cluster.pl
- DXSpider DX Cluster Version 1.47
- Copyright (c) 1998 Dirk Koopman G1TLH
- loading prefixes ...
- loading band data ...
- loading user file system ...
- starting listener ...
- reading existing message headers
- reading cron jobs
- orft we jolly well go ...
+ $ ./cluster.pl
+ DXSpider DX Cluster Version 1.50
+ Copyright (c) 1998 Dirk Koopman G1TLH
+ loading prefixes ...
+ loading band data ...
+ loading user file system ...
+ starting listener ...
+ reading existing message headers
+ reading cron jobs
+ orft we jolly well go ...
+
+
+
2. Linux quick installation guide
This section is designed for experienced Spider sysops who want to
as standard. The other is AWZNode by IZ5AWZ.
+ NB: The AX25 stuff in 2.4 kernels appears to have been broken until
+ 2.4.18. I strongly suggest you get at least this kernel.
+
+
For 2.4 kernels you need these files...
+
o libax25-0.0.7-7.i386.rpm
o ax25-tools-0.0.6-13.i386.rpm
NOTE:- before we start it is important to realise that every interface
requires a different SSID. You should be able to follow this in the
following examples.
-
-
3.5. axports
This file sets up the ax25 ports you want to use. An example is below
+
+
Note that the portnames have to be unique.
+
+
+
3.7. nrbroadcast
This file sets up the netrom broadcast qualities. An example is below
The file headings are as follows ...
-
axport - The port name in axports that you wish to broadcast
NET/ROM on.
min_obs - The minimum obsolescence value for the port
- [gb7mbc-0 via 2m]
- parameters 2 1 6 900 * 15 0
- NOCALL * * * * * * L
- default * * * * * * - sysop /spider/src/client client %u ax25
- [gb7mbc-1 via 2m]
- parameters 2 1 6 900 * 15 0
- NOCALL * * * * * * L
- default * * * * * * 0 root /usr/sbin/node node
- [gb7mbc-0 via 4m]
- parameters 2 1 6 900 * 15 0
- NOCALL * * * * * * L
- default * * * * * * - sysop /spider/src/client client %u ax25
- [gb7mbc-1 via 4m]
- parameters 2 1 6 900 * 15 0
- NOCALL * * * * * * L
- default * * * * * * 0 root /usr/sbin/node node
- <netrom2>
- parameters 1 10 * * * 3 *
- NOCALL * * * * * * L
- default * * * * * * - sysop /spider/src/client client %u ax25
- <netrom>
- parameters 1 10 * * * 3 *
- NOCALL * * * * * * L
- default * * * * * * 0 root /usr/sbin/node node
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ [gb7mbc-0 via 2m]
+ parameters 2 1 6 900 * 15 0
+ NOCALL * * * * * * L
+ default * * * * * * - sysop /spider/src/client client %u ax25
+
+ [gb7mbc-1 via 2m]
+ parameters 2 1 6 900 * 15 0
+ NOCALL * * * * * * L
+ default * * * * * * 0 root /usr/sbin/node node
+
+ [gb7mbc-0 via 4m]
+ parameters 2 1 6 900 * 15 0
+ NOCALL * * * * * * L
+ default * * * * * * - sysop /spider/src/client client %u ax25
+
+ [gb7mbc-1 via 4m]
+ parameters 2 1 6 900 * 15 0
+ NOCALL * * * * * * L
+ default * * * * * * 0 root /usr/sbin/node node
+
+ <netrom2>
+ parameters 1 10 * * * 3 *
+ NOCALL * * * * * * L
+ default * * * * * * - sysop /spider/src/client client %u ax25
+
+ <netrom>
+ parameters 1 10 * * * 3 *
+ NOCALL * * * * * * L
+ default * * * * * * 0 root /usr/sbin/node node
in interface order.
-
You should be able to see that the normal line for access to the
cluster is like this ..
+
For most purposes this is not desirable. The only time you probably
will need this is when you need to allow other cluster nodes that are
using SSID's in. In this case it would probably be better to use the
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
# /etc/ax25/node.conf - LinuxNode configuration file
The DXSpider CVS Changes addendum
Ian Maude, G0VGS, (ianmaude@btinternet.com)
- Version 0.1 March 2001
+ Version 1.50 July 2002
A reference for CVS users of the DXSpider DXCluster program.
If you have any problems with a new CVS version please mail the
- support list or come and report on WW Convers channel 9000 or from a
- 44 host to sys2.pa4ab.ampr.org (44.137.44.16) port 6667 (IRC) and join
- #9000.
+ support list.
- The latest CVS is version 1.47. There are major changes going on
- currently as the code is altered to allow DXSpider to be run under
- Microsoft Windows.
+ The latest CVS is version 1.50 build 57.002. There are major changes
+ going on currently as the code is being prepared for New Protocol.
- There is a separate file for the Windows installation in the
- /spider/html and /spider/txt directories so I will not include that
- here.
- For Linux users, there are several steps to complete to update from
- version 1.46.
+ There are currently no addenda, please look to the /spider/Changes
+ file for any small alterations.
- PLEASE READ ALL THE FOLLOWING BEFORE STARTING
- +\bo tar up your existing perl and cmd directories and put them
- somewhere safe so you can revert to the old version if necessary.
- +\bo Do a CVS update in the normal way (cvs update -d)
- +\bo cp /spider/perl/Listeners.pm to /spider/local and edit it as below
- +\bo comment out the spdlogin line in inetd.conf and 'killall -HUP
- inetd'
- +\bo "make" the client in /spider/src (just in case it has changed)
- +\bo restart the cluster and pray :-)
- The Listeners.pm file looks something like this ...
- #
- # Copy this file to /spider/local and modify it to your requirements
- #
- #
- # This file specifies which local interfaces and ports you will be
- # listening on
- #
- # You can add as many as you like
- #
- package main;
- use vars qw(@listen);
- @listen = (
- # ["localhost", 7300],
- # ["foo.dxcluster.net", 7300],
- );
- 1;
- Alter the hostnames and ports to reflect you setup. This file is only
- used for incoming telnet requests. You do not have to use hostnames,
- it is quite ok to use IP addresses and it is also a matter of choice
- whether or not you add the domain.
-
- Here is an example of a working Listeners.pm file ..
-
-
-
- @listen = (
- ["localhost", 8000],
- ["sys2", 8000],
- ["apu", 8000],
- );
-
-
-
-
- Now all this is well and good if you have a static IP address. If
- your IP address is dynamic then one line will do, like this ...
-
-
-
- @listen = (
- ["0.0.0.0", 8000],
- );
-
-
-
-
- From this version, the file client.pl has ceased to be needed. In
- fact it has been removed. If you are still using client.pl in your
- ax25d.conf then replace it with /spider/src/client.
-
projects / spider.git / commitdiff