+++ /dev/null
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN">
-<HTML>
-<HEAD>
- <META NAME="GENERATOR" CONTENT="SGML-Tools 1.0.9">
- <TITLE>The DXSpider Installation and Administration Manual: Installation (Original version by Iain Philipps, G0RDI)</TITLE>
- <LINK HREF="adminmanual-2.html" REL=next>
-
- <LINK HREF="adminmanual.html#toc1" REL=contents>
-<link rel=stylesheet href="style.css" type="text/css" title="default stylesheet">
-</HEAD>
-<BODY>
-<A HREF="adminmanual-2.html">Next</A>
-Previous
-<A HREF="adminmanual.html#toc1">Contents</A>
-<HR>
-<H2><A NAME="s1">1. Installation (Original version by Iain Philipps, G0RDI)</A></H2>
-
-<H2><A NAME="ss1.1">1.1 Introduction</A>
-</H2>
-
-<P>This section describes the installation of DX Spider v1.46 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.
-<P>
-<P>The crucial ingredient for all of this is
-<A HREF="http://www.perl.org">Perl</A>. Earlier versions of
-Spider required perl 5.004, however it is now <I>STRONGLY</I> recommended
-that you use at least version 5.005_03 as this is the version being used
-in the development of Spider.
-<P>
-<P>In addition to the standard Red Hat distribution you will require the
-following modules from
-<A HREF="http://www.cpan.org/CPAN.html">http://www.cpan.org/CPAN.html</A> ...
-<P>
-<P>
-<UL>
-<LI> Data-Dumper-2.101.tar.gz</LI>
-<LI> TimeDate-1.10.tar.gz</LI>
-<LI> IO-1.20.tar.gz (for perl 5.00403 and lower)</LI>
-<LI> Net-Telnet-3.02.tar.gz</LI>
-<LI> Curses-1.05.tar.gz</LI>
-<LI> Time-HiRes-01.20.tar.gz
-</LI>
-</UL>
-<P>
-<P>
-<P><EM>Do</EM> get the latest versions of these packages and install them
-but use the above list as the earliest versions usable.
-<P>
-<H2><A NAME="ss1.2">1.2 Preparation</A>
-</H2>
-
-<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.46 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
-the name <EM>sysop</EM>. You can call it anything you wish. Depending
-on your security requirements you may wish to use an existing user,
-however this is your own choice.
-<P>
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
-# adduser -m sysop
-</PRE>
-</CODE></BLOCKQUOTE>
-<P>
-<P>Now set a password for the user ...
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
-# passwd sysop
-# New UNIX password:
-# Retype new UNIX password:
-passwd: all authentication tokens updated successfully
-</PRE>
-</CODE></BLOCKQUOTE>
-<P>
-<H2><A NAME="ss1.3">1.3 Installing the software</A>
-</H2>
-
-<P>Now to unpack the DX Spider distribution, set symbolic links and group
-permissions. Copy the tarball to /home/sysop and do the following.
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
-# cd ~sysop
-# tar xvfz spider-1.46.tar.gz
-# ln -s ~sysop/spider /spider
-# groupadd -g 251 spider (or another number)
-</PRE>
-</CODE></BLOCKQUOTE>
-<P>If you do not have the command <EM>groupadd</EM> available to you simply
-add a line in /etc/group by hand.
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
-# vi /etc/group (or your favorite editor)
-</PRE>
-</CODE></BLOCKQUOTE>
-<P>You also need to add some others to the group, including your own callsign
-(this will be used as an alias) and root. The finished line in /etc/group
-should look something like this
-<P><CODE>spider:x:251:sysop,g0vgs,root</CODE>
-<P>
-<P>The next step is to set the permissions on the Spider directory tree and files ....
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
-# chown -R sysop.spider spider
-# find . -type d -exec chmod 2775 {} \;
-# find . -type f -exec chmod 775 {} \;
-</PRE>
-</CODE></BLOCKQUOTE>
-<P>
-<P>This last step allows various users of the group <EM>spider</EM> to have
-write access to all the directories. This is not really needed just yet
-but will be useful when web interfaces start to appear.
-<P>
-<P>Finally, you need to fix the permissions on the ax25_call and netrom_call
-programs. Check where they are with the <EM>locate</EM> command and alter
-the permissions with the <EM>chmod</EM> command like this ..
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
-# chown root ax25_call netrom_call
-# chmod 4775 ax25_call netrom_call
-</PRE>
-</CODE></BLOCKQUOTE>
-<P>
-<H2><A NAME="ss1.4">1.4 Setting callsigns etc</A>
-</H2>
-
-<P>Now login to your machine as the user you created earlier. In my case that
-user is called <EM>sysop</EM>. Once logged in, issue the following commands ....
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
-$ cd /spider
-$ mkdir local
-$ mkdir local_cmd
-$ cp perl/DXVars.pm.issue local/DXVars.pm
-$ cd local
-$ vi DXVars.pm (or your favourite editor)
-</PRE>
-</CODE></BLOCKQUOTE>
-<P>
-<P>Using the distributed DXVars.pm as a a template, set your cluster callsign,
-sysop callsign and other user info to suit your own environment. Note that
-this a perl file which will be parsed and executed as part of the cluster. If
-you get it wrong then perl will complain when you start the cluster process.
-It is important only to alter the text of any section. Some of the lines look
-a little odd. Take this line for example ....
-<P><CODE>$myemail = "ianmaude\@btinternet.com";</CODE>
-<P>
-<P>There appears to be an extra slash in there. However this has to be there
-for the file to work so leave it in.
-<P>
-<P><B>PLEASE USE CAPITAL LETTERS FOR CALLSIGNS</B>
-<P>
-<P>DON'T alter any file in /spider/perl, they are overwritten with every
-release. Any files or commands you place in /spider/local or /spider/local_cmd
-will automagically be used in preference to the ones in /spider/perl EVEN
-while the cluster is running!
-<P>
-<P>Save the new file and change directory to ../perl ....
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
-$ cd ../perl
-</PRE>
-</CODE></BLOCKQUOTE>
-<P>
-<P>Now type the following command which creates the basic user file with you as
-the sysop.
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
-$ ./create_sysop.pl
-</PRE>
-</CODE></BLOCKQUOTE>
-<P>
-<H2><A NAME="ss1.5">1.5 Starting up for the first time</A>
-</H2>
-
-<P>We can now bring spider up for the first time and see if all is well or not!
-It should look something like this ...
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
-$ ./cluster.pl
-DXSpider DX Cluster Version 1.46
-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 ...
-</PRE>
-</CODE></BLOCKQUOTE>
-<P>
-<P>If all is well then login on another term or console as <EM>sysop</EM> and
-cd to /spider/src. Now issue the following command ...
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
-$ ./client
-</PRE>
-</CODE></BLOCKQUOTE>
-<P>
-<P>This should log you into the cluster as the sysop under the alias callsign we
-set earlier. In this case the callsign is G0VGS. The cluster callsign is set
-in the DXVars.pm file in /spider/local. In this case we will assume that this
-was set as GB7MBC. You should therefore see this when you login ....
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
-G0VGS de GB7MBC 19-Nov-1999 2150Z >
-</PRE>
-</CODE></BLOCKQUOTE>
-<P>If you do, congratulations! If not, look over the instructions again, you
-have probably missed something out. You can shut spider down again with the
-command ....
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
-shutdown
-</PRE>
-</CODE></BLOCKQUOTE>
-<P>
-<P>and both the cluster and the client should return to Linux prompts.
-<P>
-<H2><A NAME="ss1.6">1.6 The Client program</A>
-</H2>
-
-<P>In earlier versions of Spider, all the processes were Perl scripts. This
-was fine but with a lot of users your computer memory would soon be used up.
-To combat this a new client was written in "C". This client only works for
-<EM>incoming</EM> connects at the moment. Before you can use it though it
-has to be "made". CD to /spider/src and type <EM>make</EM>. You
-should see the output on your screen and hopefully now have a small C program
-called <EM>client</EM>. Leave it in this directory.
-<P>
-<P>
-<HR>
-<A HREF="adminmanual-2.html">Next</A>
-Previous
-<A HREF="adminmanual.html#toc1">Contents</A>
-</BODY>
-</HTML>
+++ /dev/null
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN">
-<HTML>
-<HEAD>
- <META NAME="GENERATOR" CONTENT="SGML-Tools 1.0.9">
- <TITLE>The DXSpider Installation and Administration Manual: Databases</TITLE>
- <LINK HREF="adminmanual-11.html" REL=next>
- <LINK HREF="adminmanual-9.html" REL=previous>
- <LINK HREF="adminmanual.html#toc10" REL=contents>
-<link rel=stylesheet href="style.css" type="text/css" title="default stylesheet">
-</HEAD>
-<BODY>
-<A HREF="adminmanual-11.html">Next</A>
-<A HREF="adminmanual-9.html">Previous</A>
-<A HREF="adminmanual.html#toc10">Contents</A>
-<HR>
-<H2><A NAME="s10">10. Databases</A></H2>
-
-<P>Spider allows the creation of local or remote databases. It supports
-chained databases, allowing several different databases to be scanned
-with one simple command. Importing of databases is limited at present
-to the standard AK1A databases such as OBLAST and the DB0SDX QSL
-database but will expand with time.
-<P>
-<H2><A NAME="ss10.1">10.1 Creating databases</A>
-</H2>
-
-<P>Creating a database could not be more simple. All the commands are
-sent from the cluster prompt as the <EM>sysop</EM> user.
-<P>To create a database you use the command <EM>dbcreate</EM>. It can
-be used in 3 different ways like so ..
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
-dbcreate <name>
-</PRE>
-</CODE></BLOCKQUOTE>
-<P>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.
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
-dbcreate <name> chain <name> [<name>...]
-</PRE>
-</CODE></BLOCKQUOTE>
-<P>This creates a chained database entry. The first database will be
-scanned, then the second, the third etc...
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
-dbcreate <name> remote <name>
-</PRE>
-</CODE></BLOCKQUOTE>
-<P>This creates a remote entry. the first name field is the database
-name at the remote node, then the remote switch, then the actual
-node_call of the remote node, for example...
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
-dbcreate buckmaster remote gb7dxc
-</PRE>
-</CODE></BLOCKQUOTE>
-<P>Remote databases cannot be chained, however, the last database in a
-chain can be a remote database.
-<P>
-<H2><A NAME="ss10.2">10.2 Importing databases</A>
-</H2>
-
-<P>The only databases that Spider can currently import are the standard
-AK1A databases such as OBLAST or the DB0SDX qsl and address database.
-This will be added to with time.
-<P>To import such a database, first put the file somewhere useful like /tmp
-and then issue the following command ...
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
-dbimport oblast /tmp/OBLAST.FUL
-</PRE>
-</CODE></BLOCKQUOTE>
-<P>This will update the existing local oblast database or create it if
-it does not exist.
-<P>
-<H2><A NAME="ss10.3">10.3 Checking available databases</A>
-</H2>
-
-<P>Once a database is created, you will want to check that it has been
-added. To do this use the <EM>dbavail</EM> command. This will
-output the available databases. For example ...
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
-dbavail
-DB Name Location Chain
-qsl Local
-buck GB7ADX
-hftest GB7DXM
-G0VGS de GB7MBC 3-Feb-2001 1925Z >
-</PRE>
-</CODE></BLOCKQUOTE>
-<P>
-<H2><A NAME="ss10.4">10.4 Looking up databases</A>
-</H2>
-
-<P>To look for information in a defined database, simply use the <EM>dbshow</EM>
-command, for example ...
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
-dbshow buckmaster G0YLM
-</PRE>
-</CODE></BLOCKQUOTE>
-<P>will show the information for the callsign G0YLM from the buckmaster
-database if it exists. To make things more standard for the users
-you can add an entry in the Aliases file so that it looks like a standard
-<EM>show</EM> command like this ...
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
-'^sh\w*/buc', 'dbshow buckmaster', 'dbshow',
-</PRE>
-</CODE></BLOCKQUOTE>
-<P>Now you can simply use show/buckmaster or an abreviation.
-<P>
-<H2><A NAME="ss10.5">10.5 Removing databases</A>
-</H2>
-
-<P>To delete an existing database you use the <EM>dbremove</EM> command.
-For example ...
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
-dbremove oblast
-</PRE>
-</CODE></BLOCKQUOTE>
-<P>would remove the oblast database and its associated datafile from the
-system. There are no warnings or recovery possible from this command.
-If you remove a database it ceases to exist and would have to be created
-from scratch if you still required it.
-<P>
-<HR>
-<A HREF="adminmanual-11.html">Next</A>
-<A HREF="adminmanual-9.html">Previous</A>
-<A HREF="adminmanual.html#toc10">Contents</A>
-</BODY>
-</HTML>
+++ /dev/null
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN">
-<HTML>
-<HEAD>
- <META NAME="GENERATOR" CONTENT="SGML-Tools 1.0.9">
- <TITLE>The DXSpider Installation and Administration Manual: Information, files and useful programs</TITLE>
- <LINK HREF="adminmanual-12.html" REL=next>
- <LINK HREF="adminmanual-10.html" REL=previous>
- <LINK HREF="adminmanual.html#toc11" REL=contents>
-<link rel=stylesheet href="style.css" type="text/css" title="default stylesheet">
-</HEAD>
-<BODY>
-<A HREF="adminmanual-12.html">Next</A>
-<A HREF="adminmanual-10.html">Previous</A>
-<A HREF="adminmanual.html#toc11">Contents</A>
-<HR>
-<H2><A NAME="s11">11. Information, files and useful programs</A></H2>
-
-<H2><A NAME="ss11.1">11.1 MOTD</A>
-</H2>
-
-<P>One of the more important things a cluster sysop needs to do is to get
-information to his users. The simplest way to do this is to have a banner
-that is sent to the user on login. This is know as a "message of the day"
-or "motd". To set this up, simply create a file in /spider/data called motd
-and edit it to say whatever you want. It is purely a text file and will be
-sent automatically to anyone logging in to the cluster.
-<P>
-<H2><A NAME="ss11.2">11.2 Downtime message</A>
-</H2>
-
-<P>If for any reason the cluster is down, maybe for upgrade or maintenance but
-the machine is still running, a message can be sent to the user advising them
-of the fact. This message lives in the /spider/data directory and is called
-"offline". Simply create the file and edit it to say whatever you wish.
-This file will be sent to a user attempting to log into the cluster when
-DXSpider is not actually running.
-<P>
-<H2><A NAME="ss11.3">11.3 Other text messages</A>
-</H2>
-
-<P>You can set other text messages to be read by the user if they input the file
-name. This could be for news items or maybe information for new users.
-To set this up, make a directory under /spider called <EM>packclus</EM>.
-Under this directory you can create files called <EM>news</EM> or <EM>newuser</EM>
-for example. In fact you can create files with any names you like. These can
-be listed by the user with the command ....
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
-show/files
-</PRE>
-</CODE></BLOCKQUOTE>
-<P>They can be read by the user by typing the command ....
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
-type news
-</PRE>
-</CODE></BLOCKQUOTE>
-<P>If the file they want to read is called <EM>news</EM>. You could also set
-an alias for this in the Alias file to allow them just to type <EM>news</EM>
-<P>
-<P>You can also store other information in this directory, either directly or
-nested under directories. One use for this would be to store DX bulletins
-such as the OPDX bulletins. These can be listed and read by the user.
-To keep things tidy, make a directory under /spider/packclus called
-<EM>bulletin</EM>. Now copy any OPDX or similar bulletins into it. These
-can be listed by the user in the same way as above using the <EM>show/files</EM>
-command with an extension for the bulletin directory you have just created,
-like this ....
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
-show/files bulletin
-</PRE>
-</CODE></BLOCKQUOTE>
-<P>
-<P>An example would look like this ....
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
-sh/files
-bulletin DIR 20-Dec-1999 1715Z news 1602 14-Dec-1999 1330Z
-</PRE>
-</CODE></BLOCKQUOTE>
-<P>You can see that in the files area (basically the packclus directory) there is a
-file called <EM>news</EM> and a directory called <EM>bulletin</EM>. You can
-also see that dates they were created. In the case of the file <EM>news</EM>,
-you can also see the time it was last modified, a good clue as to whether the
-file has been updated since you last read it. To read the file called
-<EM>news</EM> you would simply issue the command ....
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
-type news
-</PRE>
-</CODE></BLOCKQUOTE>
-<P>To look what is in the bulletin directory you issue the command ....
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
-show/files bulletin
-opdx390 21381 29-Nov-1999 1621Z opdx390.1 1670 29-Nov-1999 1621Z
-opdx390.2 2193 29-Nov-1999 1621Z opdx391 25045 29-Nov-1999 1621Z
-opdx392 35969 29-Nov-1999 1621Z opdx393 15023 29-Nov-1999 1621Z
-opdx394 33429 29-Nov-1999 1621Z opdx394.1 3116 29-Nov-1999 1621Z
-opdx395 24319 29-Nov-1999 1621Z opdx396 32647 29-Nov-1999 1621Z
-opdx396.1 5537 29-Nov-1999 1621Z opdx396.2 6242 29-Nov-1999 1621Z
-opdx397 18433 29-Nov-1999 1621Z opdx398 19961 29-Nov-1999 1621Z
-opdx399 17719 29-Nov-1999 1621Z opdx400 19600 29-Nov-1999 1621Z
-opdx401 27738 29-Nov-1999 1621Z opdx402 18698 29-Nov-1999 1621Z
-opdx403 24994 29-Nov-1999 1621Z opdx404 15685 29-Nov-1999 1621Z
-opdx405 13984 29-Nov-1999 1621Z opdx405.1 4166 29-Nov-1999 1621Z
-opdx406 28934 29-Nov-1999 1621Z opdx407 24153 29-Nov-1999 1621Z
-opdx408 15081 29-Nov-1999 1621Z opdx409 23234 29-Nov-1999 1621Z
-Press Enter to continue, A to abort (16 lines) >
-</PRE>
-</CODE></BLOCKQUOTE>
-<P>You can now read any file in this directory using the type command, like this ....
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
-type bulletin/opdx391
-Ohio/Penn DX Bulletin No. 391
-The Ohio/Penn Dx PacketCluster
-DX Bulletin No. 391
-BID: $OPDX.391
-January 11, 1999
-Editor Tedd Mirgliotta, KB8NW
-Provided by BARF-80 BBS Cleveland, Ohio
-Online at 440-237-8208 28.8k-1200 Baud 8/N/1 (New Area Code!)
-Thanks to the Northern Ohio Amateur Radio Society, Northern Ohio DX
-Association, Ohio/Penn PacketCluster Network, K1XN & Golist, WB2RAJ/WB2YQH
-& The 59(9) DXReport, W3UR & The Daily DX, K3TEJ, KN4UG, W4DC, NC6J, N6HR,
-Press Enter to continue, A to abort (508 lines) >
-</PRE>
-</CODE></BLOCKQUOTE>
-<P>The page length will of course depend on what you have it set to!
-<P>
-<H2><A NAME="ss11.4">11.4 The Aliases file</A>
-</H2>
-
-<P>You will find a file in /spider/cmd/ called Aliases. First, copy this file to
-/spider/local_cmd/Aliases and edit this file. You will see something like this ...
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
-
-#!/usr/bin/perl
-
-# provide some standard aliases for commands for terminally
-# helpless ak1a user (helpless in the sense that they never
-# read nor understand help files)
-
-# This file is automagically reloaded if its modification time is
-# later than the one stored in CmdAlias.pm
-
-# PLEASE make this file consistant with reality! (the patterns MUST
-# match the filenames!)
-
-# Don't alter this file, copy it into the local_cmd tree and modify it.
-# This file will be replaced everytime I issue a new release.
-
-# You only need to put aliases in here for commands that don't work as
-# you desire naturally, e.g sh/dx on its own just works as you expect
-# so you need not add it as an alias.
-
-
-
-package CmdAlias;
-
-%alias = (
- '?' => [
- '^\?', 'apropos', 'apropos',
- ],
- 'a' => [
- '^ann.*/full', 'announce full', 'announce',
- '^ann.*/sysop', 'announce sysop', 'announce',
- '^ann.*/(.*)$', 'announce $1', 'announce',
- ],
- 'b' => [
- ],
- 'c' => [
- ],
- 'd' => [
- '^del', 'kill', 'kill',
- '^del\w*/fu', 'kill full', 'kill',
- '^di\w*/a\w*', 'directory all', 'directory',
- '^di\w*/b\w*', 'directory bulletins', 'directory',
- '^di\w*/n\w*', 'directory new', 'directory',
- '^di\w*/o\w*', 'directory own', 'directory',
- '^di\w*/s\w*', 'directory subject', 'directory',
- '^di\w*/t\w*', 'directory to', 'directory',
- '^di\w*/f\w*', 'directory from', 'directory',
- '^di\w*/(\d+)', 'directory $1', 'directory',
- ],
- 'e' => [
- ],
- 'f' => [
- ],
- 'g' => [
- ],
- 'h' => [
- ],
- 'i' => [
- ],
- 'j' => [
- ],
- 'k' => [
- ],
- 'l' => [
- '^l$', 'directory', 'directory',
- '^ll$', 'directory', 'directory',
- '^ll/(\d+)', 'directory $1', 'directory',
- ],
- 'm' => [
- ],
- 'n' => [
- '^news', 'type news', 'type',
- ],
- 'o' => [
- ],
- 'p' => [
- ],
- 'q' => [
- '^q', 'bye', 'bye',
- ],
- 'r' => [
- '^r$', 'read', 'read',
- '^rcmd/(\S+)', 'rcmd $1', 'rcmd',
- ],
- 's' => [
- '^s/p$', 'send', 'send',
- '^sb$', 'send noprivate', 'send',
- '^set/home$', 'set/homenode', 'set/homenode',
- '^set/nobe', 'unset/beep', 'unset/beep',
- '^set/nohe', 'unset/here', 'unset/here',
- '^set/noan', 'unset/announce', 'unset/announce',
- '^set/nodx', 'unset/dx', 'unset/dx',
- '^set/nota', 'unset/talk', 'unset/talk',
- '^set/noww', 'unset/wwv', 'unset/wwv',
- '^set/nowx', 'unset/wx', 'unset/wx',
- '^sh$', 'show', 'show',
- '^sh\w*/buck', 'dbshow buck', 'dbshow',
- '^sh\w*/bu', 'show/files bulletins', 'show/files',
- '^sh\w*/c/n', 'show/configuration nodes', 'show/configuration',
- '^sh\w*/c$', 'show/configuration', 'show/configuration',
- '^sh\w*/com', 'dbavail', 'dbavail',
- '^sh\w*/dx/(\d+)-(\d+)', 'show/dx $1-$2', 'show/dx',
- '^sh\w*/dx/(\d+)', 'show/dx $1', 'show/dx',
- '^sh\w*/dx/d(\d+)', 'show/dx from $1', 'show/dx',
- '^sh\w*/email', 'dbshow email', 'dbshow',
- '^sh\w*/hftest', 'dbshow hftest', 'dbshow',
- '^sh\w*/vhftest', 'dbshow vhftest', 'dbshow',
- '^sh\w*/qsl', 'dbshow qsl', 'dbshow',
- '^sh\w*/tnc', 'who', 'who',
- '^sh\w*/up', 'show/cluster', 'show/cluster',
- '^sh\w*/w\w*/(\d+)-(\d+)', 'show/wwv $1-$2', 'show/wwv',
- '^sh\w*/w\w*/(\d+)', 'show/wwv $1', 'show/wwv',
- '^sp$', 'send', 'send',
-
- ],
- 't' => [
- '^ta$', 'talk', 'talk',
- '^t$', 'talk', 'talk',
- ],
- 'u' => [
- ],
- 'v' => [
- ],
- 'w' => [
- '^wx/full', 'wx full', 'wx',
- '^wx/sysop', 'wx sysop', 'wx',
- ],
- 'x' => [
- ],
- 'y' => [
- ],
- 'z' => [
- ],
-)
-</PRE>
-</CODE></BLOCKQUOTE>
-<P>You can create aliases for commands at will. Beware though, these may not
-always turn out as you think. Care is needed and you need to test the
-results once you have set an alias.
-<P>
-<H2><A NAME="ss11.5">11.5 Console.pl</A>
-</H2>
-
-<P>In later versions of Spider a simple console program is provided for the sysop.
-This has a type ahead buffer with line editing facilities and colour for spots,
-announces etc. To use this program, simply use console.pl instead of client.
-<P>
-<P>To edit the colours, copy /spider/perl/Console.pl to /spider/local and edit the
-file with your favourite editor.
-<P>
-<H2><A NAME="ss11.6">11.6 Updating kepler data</A>
-</H2>
-
-<P>Spider has a powerful and flexible show/satellite command. In order for
-this to be accurate, the kepler data has to be updated regularly. In
-general, this data is available as an email or via cluster mail.
-Updating it is simple. First you need to export the mail message as a
-file. You do this with the <EM>export</EM> command from the cluster prompt
-as the sysop. For example ...
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
-export 5467 /spider/perl/keps.in
-</PRE>
-</CODE></BLOCKQUOTE>
-<P>would export message number 5467 as a file called keps.in in the
-/spider/perl directory.
-<P>Now login to a VT as sysop and cd /spider/perl. There is a command in
-the perl directory called <EM>convkeps.pl</EM>. All we need to do now is
-convert the file like so ...
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
-./convkeps.pl keps.in
-</PRE>
-</CODE></BLOCKQUOTE>
-<P>Now go back to the cluster and issue the command ...
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
-load/keps
-</PRE>
-</CODE></BLOCKQUOTE>
-<P>That is it! the kepler data has been updated.
-<P>
-<H2><A NAME="ss11.7">11.7 The QRZ callbook</A>
-</H2>
-
-<P>The command <EM>sh/qrz</EM> will only work once you have followed a few
-simple steps. First you need to get a user ID and password from qrz.com.
-Simply go to the site and create one. Secondly you need to copy the file
-/spider/perl/Internet.pm to /spider/local and alter it to match your user
-ID and password. You also at this point need to set $allow=1 to complete
-the setup. Many thanks to Fred Lloyd, the proprieter of
-<A HREF="http://www.qrz.com">qrz.com</A> for allowing this access.
-<P>
-<HR>
-<A HREF="adminmanual-12.html">Next</A>
-<A HREF="adminmanual-10.html">Previous</A>
-<A HREF="adminmanual.html#toc11">Contents</A>
-</BODY>
-</HTML>
+++ /dev/null
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN">
-<HTML>
-<HEAD>
- <META NAME="GENERATOR" CONTENT="SGML-Tools 1.0.9">
- <TITLE>The DXSpider Installation and Administration Manual: CVS</TITLE>
- <LINK HREF="adminmanual-13.html" REL=next>
- <LINK HREF="adminmanual-11.html" REL=previous>
- <LINK HREF="adminmanual.html#toc12" REL=contents>
-<link rel=stylesheet href="style.css" type="text/css" title="default stylesheet">
-</HEAD>
-<BODY>
-<A HREF="adminmanual-13.html">Next</A>
-<A HREF="adminmanual-11.html">Previous</A>
-<A HREF="adminmanual.html#toc12">Contents</A>
-<HR>
-<H2><A NAME="s12">12. CVS</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>
-<P>THIS IS NOT FOR THE FAINT HEARTED!!! ONLY DO THIS IF YOU HAVE A TEST
-INSTALLATION OR ARE WILLING TO HAVE YOUR CLUSTER CRASH ON YOU!!!
-THIS MUST BE CONSIDERED AT LEAST BETA TESTING AND MAYBE EVEN ALPHA!!
-YOU HAVE BEEN WARNED!!!
-<P>
-<P>DID I MENTION..... ONLY DO THIS IF YOU ARE WILLING TO ACCEPT THE
-CONSEQUENCES!!!
-<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 ...
-<P>
-<PRE>
-cvs -d:pserver:anonymous@cvs.DXSpider.sourceforge.net:/cvsroot/dxspider login
-</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.
-<P>
-<PRE>
-cvs -z3 -d:pserver:anonymous@cvs.DXSpider.sourceforge.net:/cvsroot/dxspider co spider
-</PRE>
-<P>This command is all on one line.
-<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>
-<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>If you want to upgrade your current installation then do this ...
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
-tar cvfz /tmp/s.tgz spider
-cd /
-tar xvfzp /tmp/s.tgz
-</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>
-<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>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>
-cd /spider
-cvs -z3 update -d
-</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-13.html">Next</A>
-<A HREF="adminmanual-11.html">Previous</A>
-<A HREF="adminmanual.html#toc12">Contents</A>
-</BODY>
-</HTML>
+++ /dev/null
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN">
-<HTML>
-<HEAD>
- <META NAME="GENERATOR" CONTENT="SGML-Tools 1.0.9">
- <TITLE>The DXSpider Installation and Administration Manual: The DXSpider command set</TITLE>
- <LINK HREF="adminmanual-12.html" REL=previous>
- <LINK HREF="adminmanual.html#toc13" REL=contents>
-<link rel=stylesheet href="style.css" type="text/css" title="default stylesheet">
-</HEAD>
-<BODY>
-Next
-<A HREF="adminmanual-12.html">Previous</A>
-<A HREF="adminmanual.html#toc13">Contents</A>
-<HR>
-<H2><A NAME="s13">13. The DXSpider command set</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>
-<H2><A NAME="ss13.1">13.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="ss13.2">13.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="ss13.3">13.3 accept/spots (0)</A>
-</H2>
-
-<P><CODE><B>accept/announce [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="ss13.4">13.4 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="ss13.5">13.5 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="ss13.6">13.6 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="ss13.7">13.7 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="ss13.8">13.8 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="ss13.9">13.9 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
-<P>
-<H2><A NAME="ss13.10">13.10 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="ss13.11">13.11 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="ss13.12">13.12 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="ss13.13">13.13 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="ss13.14">13.14 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="ss13.15">13.15 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>
-<P>
-<H2><A NAME="ss13.16">13.16 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="ss13.17">13.17 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="ss13.18">13.18 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="ss13.19">13.19 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="ss13.20">13.20 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="ss13.21">13.21 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="ss13.22">13.22 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="ss13.23">13.23 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="ss13.24">13.24 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="ss13.25">13.25 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="ss13.26">13.26 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="ss13.27">13.27 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="ss13.28">13.28 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="ss13.29">13.29 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="ss13.30">13.30 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="ss13.31">13.31 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="ss13.32">13.32 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="ss13.33">13.33 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="ss13.34">13.34 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="ss13.35">13.35 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="ss13.36">13.36 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="ss13.37">13.37 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>
-<P>
-<H2><A NAME="ss13.38">13.38 load/baddx (9)</A>
-</H2>
-
-<P><CODE><B>load/baddx</B> Reload the bad DX table</CODE>
-<P>
-<P>Reload the /spider/data/baddx.pl file if you have changed it manually whilst
-the cluster is running. This table contains the DX Calls that, if spotted,
-will not be passed on. FR0G and TEST are classic examples.
-<P>
-<H2><A NAME="ss13.39">13.39 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="ss13.40">13.40 load/badwords (9)</A>
-</H2>
-
-<P><CODE><B>load/badwords</B> Reload the badwords file</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="ss13.41">13.41 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="ss13.42">13.42 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="ss13.43">13.43 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="ss13.44">13.44 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="ss13.45">13.45 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="ss13.46">13.46 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="ss13.47">13.47 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="ss13.48">13.48 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="ss13.49">13.49 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="ss13.50">13.50 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="ss13.51">13.51 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="ss13.52">13.52 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="ss13.53">13.53 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="ss13.54">13.54 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="ss13.55">13.55 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="ss13.56">13.56 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="ss13.57">13.57 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="ss13.58">13.58 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="ss13.59">13.59 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="ss13.60">13.60 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="ss13.61">13.61 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="ss13.62">13.62 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="ss13.63">13.63 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="ss13.64">13.64 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="ss13.65">13.65 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="ss13.66">13.66 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="ss13.67">13.67 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="ss13.68">13.68 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="ss13.69">13.69 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="ss13.70">13.70 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="ss13.71">13.71 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="ss13.72">13.72 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="ss13.73">13.73 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="ss13.74">13.74 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="ss13.75">13.75 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="ss13.76">13.76 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="ss13.77">13.77 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="ss13.78">13.78 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="ss13.79">13.79 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="ss13.80">13.80 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="ss13.81">13.81 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="ss13.82">13.82 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="ss13.83">13.83 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="ss13.84">13.84 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="ss13.85">13.85 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="ss13.86">13.86 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="ss13.87">13.87 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="ss13.88">13.88 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>
-<P>
-<H2><A NAME="ss13.89">13.89 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 but any spaces are removed (you can type in
-spaces - but they won't appear in the password). You can see the
-result with STAT/USER. The password is the usual 30 character baycom
-type password.
-<P>
-<H2><A NAME="ss13.90">13.90 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="ss13.91">13.91 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="ss13.92">13.92 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="ss13.93">13.93 set/sys_qra (9)</A>
-</H2>
-
-<P><CODE><B>set/sys_qra <locator></B> Set your cluster QRA locator</CODE>
-<P>
-<H2><A NAME="ss13.94">13.94 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="ss13.95">13.95 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>
-<BLOCKQUOTE><CODE>
-<PRE>
- set/qth East Dereham, Norfolk
-</PRE>
-</CODE></BLOCKQUOTE>
-<P>
-<H2><A NAME="ss13.96">13.96 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="ss13.97">13.97 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="ss13.98">13.98 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="ss13.99">13.99 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="ss13.100">13.100 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="ss13.101">13.101 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="ss13.102">13.102 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="ss13.103">13.103 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="ss13.104">13.104 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="ss13.105">13.105 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="ss13.106">13.106 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="ss13.107">13.107 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="ss13.108">13.108 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="ss13.109">13.109 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="ss13.110">13.110 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="ss13.111">13.111 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="ss13.112">13.112 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="ss13.113">13.113 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="ss13.114">13.114 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="ss13.115">13.115 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="ss13.116">13.116 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="ss13.117">13.117 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="ss13.118">13.118 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>inputing:-
-<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="ss13.119">13.119 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="ss13.120">13.120 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="ss13.121">13.121 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="ss13.122">13.122 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>
-<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>
-<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="ss13.123">13.123 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="ss13.124">13.124 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="ss13.125">13.125 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="ss13.126">13.126 show/sun (0)</A>
-</H2>
-
-<P><CODE><B>show/sun [<prefix>|<callsign>]</B> Show
-sun rise and set times</CODE>
-<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>
-<BLOCKQUOTE><CODE>
-<PRE>
- SH/SUN
- SH/SUN G1TLH K9CW ZS
-</PRE>
-</CODE></BLOCKQUOTE>
-<P>
-<H2><A NAME="ss13.127">13.127 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="ss13.128">13.128 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="ss13.129">13.129 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="ss13.130">13.130 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="ss13.131">13.131 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="ss13.132">13.132 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="ss13.133">13.133 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="ss13.134">13.134 stat/msg (5)</A>
-</H2>
-
-<P><CODE><B>stat/msg <msgno></B> Show the status of a message</CODE>
-<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>
-<H2><A NAME="ss13.135">13.135 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="ss13.136">13.136 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
-</PRE>
-</CODE></BLOCKQUOTE>
-<P>you type:-
-<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>
-<H2><A NAME="ss13.137">13.137 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>
-<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>
-<BLOCKQUOTE><CODE>
-<PRE>
- /DX 14001 G1TLH What's a B class licensee doing on 20m CW?
- /HELP talk
-</PRE>
-</CODE></BLOCKQUOTE>
-<P>To leave talk mode type:
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
- /EX
-</PRE>
-</CODE></BLOCKQUOTE>
-<P>
-<H2><A NAME="ss13.138">13.138 type (0)</A>
-</H2>
-
-<P><CODE><B>type <filearea>/<name></B> Look at a file in one of the fileareas</CODE>
-<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>
-<BLOCKQUOTE><CODE>
-<PRE>
- TYPE bulletins/arld051
-</PRE>
-</CODE></BLOCKQUOTE>
-<P>See also SHOW/FILES to see what fileareas are available and a
-list of content.
-<P>
-<H2><A NAME="ss13.139">13.139 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="ss13.140">13.140 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="ss13.141">13.141 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>
-<P>
-<HR>
-Next
-<A HREF="adminmanual-12.html">Previous</A>
-<A HREF="adminmanual.html#toc13">Contents</A>
-</BODY>
-</HTML>
+++ /dev/null
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN">
-<HTML>
-<HEAD>
- <META NAME="GENERATOR" CONTENT="SGML-Tools 1.0.9">
- <TITLE>The DXSpider Installation and Administration Manual: Quick installation guide (Linux version)</TITLE>
- <LINK HREF="adminmanual-3.html" REL=next>
- <LINK HREF="adminmanual-1.html" REL=previous>
- <LINK HREF="adminmanual.html#toc2" REL=contents>
-<link rel=stylesheet href="style.css" type="text/css" title="default stylesheet">
-</HEAD>
-<BODY>
-<A HREF="adminmanual-3.html">Next</A>
-<A HREF="adminmanual-1.html">Previous</A>
-<A HREF="adminmanual.html#toc2">Contents</A>
-<HR>
-<H2><A NAME="s2">2. Quick installation guide (Linux version)</A></H2>
-
-<P>This section is designed for experienced Spider sysops who want to install
-Spider from scratch. It is simply a check list of things that need to be
-done without any explanations. The name in brackets at the end of each line
-is the user that should be doing that process.
-<P>
-<UL>
-<LI>Login as root</LI>
-<LI>Get the additional CPAN modules and install them (root)</LI>
-<LI>Create the "sysop" user and set a password (root)</LI>
-<LI>Put the Spider tarball in sysop and untar it (root)</LI>
-<LI>ln -s sysop/spider /spider (root)</LI>
-<LI>groupadd -g 251 spider (root)</LI>
-<LI>Add any more users you need to the group entry in /etc/group (root)</LI>
-<LI>Set the permissions on the spider tree (root)</LI>
-<LI>Fix permissions on ax25_call and netrom_call (root)</LI>
-<LI>Login as the sysop user</LI>
-<LI>cd to /spider (sysop)</LI>
-<LI>mkdir local (sysop)</LI>
-<LI>mkdir local_cmd (sysop)</LI>
-<LI>cp perl/DXVars.pm.issue local/DXVars.pm (sysop)</LI>
-<LI>cd to /spider/local and edit DXVars to set your details (sysop)</LI>
-<LI>cd ../perl (sysop)</LI>
-<LI>./create_sysop.pl (sysop)</LI>
-<LI>./cluster.pl (sysop)</LI>
-</UL>
-<P>Spider should now be running and you should be able to login using the
-client program.
-<P>
-<UL>
-<LI>Login as root</LI>
-<LI>Enter the correct line in ax25d.conf (root)</LI>
-<LI>Enter the correct line in /etc/services (root)</LI>
-<LI>Enter the correct line in /etc/inetd.conf (root)</LI>
-<LI>killall -HUP inetd (root)</LI>
-</UL>
-<P>Spider should now be able to accept logins via telnet, netrom and ax25.
-<P>
-<UL>
-<LI>Login as sysop</LI>
-<LI>Start the cluster (sysop)</LI>
-<LI>set/node and type for links (sysop)</LI>
-<LI>Write any connect scripts (sysop)</LI>
-<LI>Edit /spider/crontab as required (sysop)</LI>
-<LI>Edit any other files as necessary (sysop)</LI>
-<LI>Set filters, hops and forwarding files (sysop)</LI>
-<LI>Login as root</LI>
-<LI>Enter the correct line in /etc/inittab (root)</LI>
-</UL>
-<P>
-<HR>
-<A HREF="adminmanual-3.html">Next</A>
-<A HREF="adminmanual-1.html">Previous</A>
-<A HREF="adminmanual.html#toc2">Contents</A>
-</BODY>
-</HTML>
+++ /dev/null
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN">
-<HTML>
-<HEAD>
- <META NAME="GENERATOR" CONTENT="SGML-Tools 1.0.9">
- <TITLE>The DXSpider Installation and Administration Manual: Configuration</TITLE>
- <LINK HREF="adminmanual-4.html" REL=next>
- <LINK HREF="adminmanual-2.html" REL=previous>
- <LINK HREF="adminmanual.html#toc3" REL=contents>
-<link rel=stylesheet href="style.css" type="text/css" title="default stylesheet">
-</HEAD>
-<BODY>
-<A HREF="adminmanual-4.html">Next</A>
-<A HREF="adminmanual-2.html">Previous</A>
-<A HREF="adminmanual.html#toc3">Contents</A>
-<HR>
-<H2><A NAME="s3">3. Configuration</A></H2>
-
-<H2><A NAME="ss3.1">3.1 Allowing ax25 connects from users</A>
-</H2>
-
-<P>As stated previously, the aim of this document is not to tell you how to
-configure Linux or the ax25 utilities. However, you do need to add a line
-in your ax25d.conf to allow connections to DXSpider for your users. For
-each interface that you wish to allow connections on, use the following format ...
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
-default * * * * * * - sysop /spider/src/client client %u ax25
-</PRE>
-</CODE></BLOCKQUOTE>
-<P>or, if you wish your users to be able to use SSID's on their callsigns ..
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
-default * * * * * * - sysop /spider/src/client client %s ax25
-</PRE>
-</CODE></BLOCKQUOTE>
-<P>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 first example and
-then add a specific line for that node like this:
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
-GB7DJK-2 * * * * * * - sysop /spider/src/client client gb7djk-2 ax25
-default * * * * * * - sysop /spider/src/client client %u ax25
-</PRE>
-</CODE></BLOCKQUOTE>
-<P>
-<H2><A NAME="ss3.2">3.2 Allowing telnet connects from users </A>
-</H2>
-
-<P>
-From version 1.47 there is a new (more efficient) way of doing this
-(see next section) but, if you prefer, the method of doing it described
-here will continue to work just fine.
-<P>
-<P>Allowing telnet connections is quite simple. Firstly you need to add a line
-in /etc/services to allow connections to a port number, like this ....
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
-spdlogin 8000/tcp # spider anonymous login port
-</PRE>
-</CODE></BLOCKQUOTE>
-<P>Then add a line in /etc/inetd.conf like this ....
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
-spdlogin stream tcp nowait root /usr/sbin/tcpd /spider/src/client login telnet
-</PRE>
-</CODE></BLOCKQUOTE>
-<P>
-<P>Once this is done, you need to restart inetd like this ....
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
-killall -HUP inetd
-</PRE>
-</CODE></BLOCKQUOTE>
-<P>
-<P>
-<P>Now login as <EM>sysop</EM> and cd spider/src. You can test that spider
-is accepting telnet logins by issuing the following command ....
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
-./client login telnet
-</PRE>
-</CODE></BLOCKQUOTE>
-<P>You should get a login prompt and on issuing a callsign, you will be given
-access to the cluster. Note, you will not get a password login. There seems
-no good reason for a password prompt to be given so it is not asked for.
-<P>
-<P>Assuming all is well, then try a telnet from your linux console ....
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
-telnet localhost 8000
-</PRE>
-</CODE></BLOCKQUOTE>
-<P>
-<P>You should now get the login prompt and be able to login as before.
-<P>
-<H2><A NAME="ss3.3">3.3 Setting up telnet connects (from 1.47 onwards)</A>
-</H2>
-
-<P>From version 1.47 you can choose to allow the perl cluster.pl program to
-allow connections directly (i.e. not via the <CODE>/spider/src/client</CODE>
-interface program). If you are using Windows then this is the only method
-available of allowing incoming telnet connections.
-<P>
-<P>To do this you need first to remove any line that you may previously have set
-up in /etc/inetd.conf. Remember to:-
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
-killall -HUP inetd
-</PRE>
-</CODE></BLOCKQUOTE>
-<P>
-<P>to make the change happen...
-<P>
-<P>Having done that, you need to copy the file
-<EM>/spider/perl/Listeners.pm</EM> to <EM>/spider/local</EM> and
-then edit it. You will need to uncomment the line containing "0.0.0.0"
-and select the correct port to listen on. So that it looks like this:-
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
-@listen = (
- ["0.0.0.0", 8000],
-);
-</PRE>
-</CODE></BLOCKQUOTE>
-<P>
-<P>As standard, the listener will listen on all interfaces simultaneously.
-If you require more control than this, you can specify each interface
-individually:-
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
-@listen = (
- ["gb7baa.dxcluster.net", 8000],
- ["44.131.16.2", 6300],
-);
-</PRE>
-</CODE></BLOCKQUOTE>
-<P>
-<P>This will only be successful if the IP addresses on each interface are static.
-If you are using some kind of dynamic IP addressing then the 'default' method
-is the only one that will work.
-<P>
-<P>Restart the cluster.pl program to enable the listener.
-<P>
-<P>One important difference with the internal listener is that no echoing
-is done by the cluster program. Users will need to set 'local-echo' on in
-their telnet clients if it isn't set automatically (as per the standards).
-Needless to say this will probably only apply to Windows users.
-<P>
-<H2><A NAME="ss3.4">3.4 Setting up for AGW Engine (1.47 onwards)</A>
-</H2>
-
-<P>AGW Engine is a Windows based ax25 stack. You can connect to an AGW engine
-from Linux as well as Windows based machines.
-<P>
-<P>In order to enable access to an AGW Engine you need to copy
-<EM>/spider/perl/AGWConnect.pm</EM> to <EM>/spider/local</EM> and edit it.
-Specifically you must:-
-<P>
-<UL>
-<LI> set <CODE>$enable</CODE> to 1.</LI>
-<LI> set <CODE>$login</CODE> and <CODE>$passwd</CODE> to the values set up in your AGW installation.
-If you haven't set any there, then you should not touch these values.</LI>
-<LI> You can connect to a remote AGW engine (ie on some other machine) by changing <CODE>$addr</CODE>
-and <CODE>$port</CODE> appropriately.</LI>
-<LI> Restart the cluster.pl program</LI>
-</UL>
-
-<P>
-<P>
-<H2><A NAME="ss3.5">3.5 Setting up node connects</A>
-</H2>
-
-<P>In order to allow cluster node connections, spider needs to know that the
-connecting callsign is a cluster node. This is the case whether the connect
-is incoming or outgoing. In spider this is a simple task and can be done in
-runtime.
-<P>
-<P>Later versions of Spider can distinguish different software and treat them
-differently. For example, the WCY beacon cannot be handles by AK1A type
-nodes as AK1A does not know what to do with PC73. There are 4 different
-types of node at present and although they may not have any major
-differences at the moment, it allows for compatibility. The 4 types are ...
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
-set/node (AK1A type)
-set/spider
-set/dxnet
-set/clx
-</PRE>
-</CODE></BLOCKQUOTE>
-<P>
-<P>For now, we will assume that the cluster we are going to connect to is an
-AK1A type node.
-<P>
-<P>Start up the cluster as you did before and login as the sysop with client.
-The cluster node I am wanting to make a connection to is GB7BAA but you would
-obviously use whatever callsign you required. At the prompt type ...
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
-set/node gb7baa
-</PRE>
-</CODE></BLOCKQUOTE>
-<P>
-<P>The case does not matter as long as you have a version of DXSpider later than
-1.33. Earlier versions required the callsign to be in upper case.
-<P>
-<P>That is now set, it is as simple as that. To prove it, login on yet another
-console as sysop, cd to spider/src and issue the command ...
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
-./client gb7baa (using the callsign you set as a node)
-</PRE>
-</CODE></BLOCKQUOTE>
-<P>
-<P>You should get an initialisation string from DXSpider like this ...
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
-./client gb7baa
-PC38^GB7MBC^~
-</PRE>
-</CODE></BLOCKQUOTE>
-<P>If the callsign you just set up as a cluster node is for an incoming connect,
-this is all that needs to be done. If the connection is to be outgoing then
-a connection script needs to be written.
-<P>
-<P>Sometimes you make a mistake... Honest, it does happen. If you want to make a node
-back to being a normal user, regardless
-of what type it is, do:
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
-unset/node gb7baa
-</PRE>
-</CODE></BLOCKQUOTE>
-<P>
-<H2><A NAME="ss3.6">3.6 Connection scripts</A>
-</H2>
-
-<P>Because DXSpider operates under Linux, connections can be made using just about
-any protocol; AX25, NETRom, tcp/ip, ROSE etc are all possible examples.
-Connect scripts live in the /spider/connect directory and are simple ascii files.
-Writing a script for connections is therefore relatively simple.
-<P>
-<P>The connect scripts consist of lines which start with the following keywords
-or symbols:-
-<P>
-<DL>
-<P>
-<DT><B>#</B><DD><P>All lines starting with a <CODE>#</CODE> are ignored, as are completely
-blank lines.
-<P>
-<DT><B>timeout</B><DD><P><CODE>timeout</CODE> followed by a number is the number of seconds to wait for a
-command to complete. If there is no timeout specified in the script
-then the default is 60 seconds.
-<P>
-<DT><B>abort</B><DD><P><CODE>abort</CODE> is a regular expression containing one or more strings to look
-for to abort a connection. This is a perl regular expression and is
-executed ignoring case.
-<P>
-<DT><B>connect</B><DD><P><CODE>connect</CODE> followed by ax25, agw (for Windows users) or telnet and some type dependent
-information. In the case of a telnet connection, there can be up to
-two parameters.
-The first is the ip address or hostname of the computer you wish to
-connect to and the second is the port number you want to use (this
-can be left out if it is a normal telnet session).
-In the case of an ax25 session then this would normally be a call to
-ax25_call or netrom_call as in the example above. It is your
-responsibility to get your node and other ax25 parameters to work
-before going down this route!
-<P>
-<DT><B>'</B><DD><P><CODE>'</CODE> is the delimiting character for a word or phrase of an expect/send
-line in a chat type script. The words/phrases normally come in pairs,
-either can be empty. Each line reads input from the connection until
-it sees the string (or perl regular expression) contained in the
-left hand string. If the left hand string is empty then it doesn't
-read or wait for anything. The comparison is done ignoring case.
-When the left hand string has found what it is looking for (if it is)
-then the right hand string is sent to the connection.
-This process is repeated for every line of chat script.
-<P>
-<DT><B>client</B><DD><P><CODE>client</CODE> starts the connection, put the arguments you would want here
-if you were starting the client program manually. You only need this
-if the script has a different name to the callsign you are trying to
-connect to (i.e. you have a script called other which actually
-connects to GB7DJK-1 [instead of a script called gb7djk-1]).
-</DL>
-<P>
-<P>There are many possible ways to configure the script but here are three examples,
-one for a NETRom/AX25 connect, one for AGW engines and one for tcp/ip.
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
-timeout 60
-abort (Busy|Sorry|Fail)
-# don't forget to chmod 4775 netrom_call!
-connect ax25 /usr/sbin/netrom_call bbs gb7djk g1tlh
-'Connect' ''
-'Connect' 'c np7'
-'Connect' 'c gb7dxm'
-# you can leave this out if you call the script 'gb7dxm'
-client gb7dxm ax25
-</PRE>
-</CODE></BLOCKQUOTE>
-<P>
-<P>
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
-timeout 60
-abort (Busy|Sorry|Fail)
-# this does exactly the same as the previous example
-# the '1' is the AGW port number to connect thru for g1tlh
-connect agw 1 g1tlh
-'Connect' ''
-'Connect' 'c np7'
-'Connect' 'c gb7dxm'
-# you can leave this out if you call the script 'gb7dxm'
-client gb7dxm ax25
-</PRE>
-</CODE></BLOCKQUOTE>
-<P>
-<P>
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
-timeout 15
-connect telnet dirkl.tobit.co.uk
-'login' 'gb7djk'
-'word' 'gb7djk'
-# tell GB7DJK-1 that it is connected to GB7DJK
-# you can leave this out if you call this script 'gb7djk'
-client gb7djk telnet
-</PRE>
-</CODE></BLOCKQUOTE>
-<P>
-<P>Both these examples assume that everything is set up properly at the other end.
-You will find other examples in the /spider/examples directory.
-<P>
-<H2><A NAME="ss3.7">3.7 Starting the connection</A>
-</H2>
-
-<P>You start the connection, from within a sysop enabled cluster login, by typing
-in the word <EM>connect</EM> followed by a script name like this ....
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
-G0VGS de GB7MBC 13-Dec-1998 2041Z >connect gb7djk-1
-connection to GB7DJK-1 started
-G0VGS de GB7MBC 13-Dec-1998 2043Z >
-</PRE>
-</CODE></BLOCKQUOTE>
-<P>This will start a connection using the script called <EM>gb7djk-1</EM>. You can
-follow the connection by watching the term or console from where you started
-<EM>cluster.pl</EM>. From version 1.47 onwards, you will need to <CODE>set/debug connect</CODE> first.
-You should see something like this ...
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
-<- D G1TLH connect gb7djk-1
--> D G1TLH connection to GB7DJK-1 started
--> D G1TLH G1TLH de GB7DJK 13-Dec-1998 2046Z >
-timeout set to 15
-CONNECT sort: telnet command: dirkl.tobit.co.uk
-CHAT "login" -> "gb7djk"
-received "
-Red Hat Linux release 5.1 (Manhattan)
-Kernel 2.0.35 on an i586
-"
-received "login: "
-sent "gb7djk"
-CHAT "word" -> "gb7djk"
-received "gb7djk"
-received "Password: "
-sent "gb7djk"
-Connected to GB7DJK-1, starting normal protocol
-<- O GB7DJK-1 telnet
--> B GB7DJK-1 0
-GB7DJK-1 channel func state 0 -> init
-<- D GB7DJK-1
-<- D GB7DJK-1 Last login: Sun Dec 13 17:59:56 from dirk1
-<- D GB7DJK-1 PC38^GB7DJK-1^~
-<- D GB7DJK-1 PC18^ 1 nodes, 0 local / 1 total users Max users 0 Uptime
-0 00:00^5447^~
- etc
-</PRE>
-</CODE></BLOCKQUOTE>
-<P>
-<P>With later versions of Spider there is a set/login command for users. This
-tells them when a user or node logs in or out. If you do not add a line to
-your scripts after the final line (or before the client line which should always
-be last if needed) then the login/logout information will be sent to users
-<I>before</I> the login actually completes. This means if a node is
-unreachable, it will continue sending logins and logouts to users even though it
-is not actually connecting. To avoid this use the following line ...
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
-'connect' ''
-</PRE>
-</CODE></BLOCKQUOTE>
-<P>
-<P>In a script, this might look like ...
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
-timeout 35
-abort (Busy|Sorry|Fail)
-connect telnet mary 3000
-'ogin:' 'gb7mbc'
-'>' 'telnet 44.131.93.96 7305'
-'connect' ''
-</PRE>
-</CODE></BLOCKQUOTE>
-<P>
-<H2><A NAME="ss3.8">3.8 Telnet echo</A>
-</H2>
-
-<P>Cluster links in particular suffer greatly from the presence of telnet echo.
-This is caused by the telnet negotiation itself and can create at worst severe
-loops. At best it creates unnecessary bandwidth and large logfiles! There are
-things that can be done to limit this problem but will not always work dependent
-on the route taken to connect.
-<P>
-<P>Telnet echo itself should only be a problem if the connection is being made to
-the telnet port (23). This port uses special rules that include echo negotiation.
-If the connection is to a different port, such as 7300, this negotiation does
-not happen and therefore no echo should be present.
-<P>
-<P>Sometimes it is not possible to make a direct connection to another node and this
-can cause problems. There is a way of trying to suppress the telnet echo but
-this will not always work, unfortunately it is difficult to be more specific.
-Here is an example of what I mean ...
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
-timeout 35
-abort (Busy|Sorry|Fail)
-connect telnet mary.lancs.ac.uk
-'ogin:' 'gb7mbc'
-'word:' 'mypasswd'
-'\$' 'stty -echo raw'
-'\$' 'telnet 44.131.93.96'
-'connect' ''
-</PRE>
-</CODE></BLOCKQUOTE>
-<P>So, the first connection is made by Spider. This is fine as Spider uses the
-Net_Telnet script from within perl. This actually uses TCP rather than TELNET
-so no negotiation will be done on the first connection. Once connected to
-mary.lancs.ac.uk, the command is sent to suppress echo. Now a telnet is made
-to a cluster node that is accepting connections on port 23. The problem with
-this link is that the negotiation is made by the remote machine, therefore you
-have no control over it. The chances are that this link will create echo and
-there will be no way you can stop it.
-<P>
-<P>
-<HR>
-<A HREF="adminmanual-4.html">Next</A>
-<A HREF="adminmanual-2.html">Previous</A>
-<A HREF="adminmanual.html#toc3">Contents</A>
-</BODY>
-</HTML>
+++ /dev/null
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN">
-<HTML>
-<HEAD>
- <META NAME="GENERATOR" CONTENT="SGML-Tools 1.0.9">
- <TITLE>The DXSpider Installation and Administration Manual: Automating things</TITLE>
- <LINK HREF="adminmanual-5.html" REL=next>
- <LINK HREF="adminmanual-3.html" REL=previous>
- <LINK HREF="adminmanual.html#toc4" REL=contents>
-<link rel=stylesheet href="style.css" type="text/css" title="default stylesheet">
-</HEAD>
-<BODY>
-<A HREF="adminmanual-5.html">Next</A>
-<A HREF="adminmanual-3.html">Previous</A>
-<A HREF="adminmanual.html#toc4">Contents</A>
-<HR>
-<H2><A NAME="s4">4. Automating things</A></H2>
-
-<P>Ok, you should now have DXSpider running nicely and allowing connects by cluster
-nodes or users. However, it has to be shutdown and restarted manually and if
-connection scripts fail they have to be started again manually too, not much use
-if you are not at the console! So, in this section we will automate both.
-Firstly starting the cluster.
-<P>
-<H2><A NAME="ss4.1">4.1 Autostarting the cluster</A>
-</H2>
-
-<P>This is not only a way to start the cluster automatically, it also works as a
-watchdog, checking the sanity of DXSpider and respawning it should it crash for
-any reason. Before doing the following, shutdown the cluster as you did earlier.
-<P>
-<P>Login as root and bring up the /etc/inittab file in your favourite editor. Add
-the following lines to the file near the end ...
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
-##Start DXSpider on bootup and respawn it should it crash
-DX:3:respawn:/bin/su -c "/usr/bin/perl -w /spider/perl/cluster.pl" sysop >/dev/tty7
-</PRE>
-</CODE></BLOCKQUOTE>
-<P>
-<P>This line works fine for RedHat distributions. It is also fine for SuSE up to
-7.0. From Suse 7.1 you need to add runlevels 2 and 5 like this ...
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
-DX:235:respawn:/bin/su -c "/usr/bin/perl -w /spider/perl/cluster.pl" sysop >/dev/tty7
-</PRE>
-</CODE></BLOCKQUOTE>
-<P>
-<P>The line required for Slackware distributions is slightly different. My thanks to
-Aurelio, PA3EZL for this information.
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
-DX:23:respawn:/bin/su - sysop -c "/usr/bin/perl -w /spider/perl/cluster.pl" >/dev/tty7
-</PRE>
-</CODE></BLOCKQUOTE>
-<P>
-<P>This will automatically start DXSpider on tty7 (ALT-F7) on bootup and restart
-it should it crash for any reason.
-<P>
-<P>As root type the command <EM>telinit q</EM>. DXSpider should start up
-immediately. You will see the output on tty7 and if you login as <EM>sysop</EM>
-you should find everything running nicely.
-<P>
-<P>So far so good, now to automate script connections...
-<P>
-<H2><A NAME="ss4.2">4.2 The crontab file</A>
-</H2>
-
-<P>Login as <EM>sysop</EM> and create a file in /spider/local_cmd called crontab.
-Edit it with your favourite editor and add a line like this (I have included
-a comment)
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
-# check every 10 minutes to see if gb7xxx is connected and if not
-# start a connect job going
-
-0,10,20,30,40,50 * * * * start_connect('gb7xxx') if unless connected('gb7xxx')
-</PRE>
-</CODE></BLOCKQUOTE>
-<P>
-<P>The callsign involved will be the callsign of the cluster node you are
-going to connect to. This will now check every 10 minutes to see if
-gb7xxx is connected, if it is then nothing will be done. If it is not,
-then a connect attempt will be started.
-<P>
-<P>There are probably lots of other things you could use this crontab file for.
-If you want to know more about it, look at the
-<A HREF="http://www.dxcluster.org/cron.html">DXSpider</A> website
-at the cron page where it is explained more fully.
-<P>
-<HR>
-<A HREF="adminmanual-5.html">Next</A>
-<A HREF="adminmanual-3.html">Previous</A>
-<A HREF="adminmanual.html#toc4">Contents</A>
-</BODY>
-</HTML>
+++ /dev/null
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN">
-<HTML>
-<HEAD>
- <META NAME="GENERATOR" CONTENT="SGML-Tools 1.0.9">
- <TITLE>The DXSpider Installation and Administration Manual: Hop control</TITLE>
- <LINK HREF="adminmanual-6.html" REL=next>
- <LINK HREF="adminmanual-4.html" REL=previous>
- <LINK HREF="adminmanual.html#toc5" REL=contents>
-<link rel=stylesheet href="style.css" type="text/css" title="default stylesheet">
-</HEAD>
-<BODY>
-<A HREF="adminmanual-6.html">Next</A>
-<A HREF="adminmanual-4.html">Previous</A>
-<A HREF="adminmanual.html#toc5">Contents</A>
-<HR>
-<H2><A NAME="s5">5. Hop control</A></H2>
-
-<P>Starting with version 1.13 there is simple hop control available on a per
-node basis. Also it is possible to isolate a network completely so that you
-get all the benefits of being on that network, but can't pass on information
-from it to any other networks you may be connected to (or vice versa).
-<P>
-<H2><A NAME="ss5.1">5.1 Basic hop control</A>
-</H2>
-
-<P>In /spider/data you will find a file called hop_table.pl. This is the file
-that controls your hop count settings. It has a set of default hops on the
-various PC frames and also a set for each node you want to alter the hops for.
-You may be happy with the default settings of course, but this powerful tool
-can help to protect and improve the network. The file will look something
-like this ...
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
-#
-# hop table construction
-#
-
-package DXProt;
-
-# default hopcount to use
-$def_hopcount = 5;
-
-# some variable hop counts based on message type
-%hopcount =
-(
- 11 => 10,
- 16 => 10,
- 17 => 10,
- 19 => 10,
- 21 => 10,
-);
-
-
-# the per node hop control thingy
-
-
-%nodehops =
-
- GB7ADX => { 11 => 8,
- 12 => 8,
- 16 => 8,
- 17 => 8,
- 19 => 8,
- 21 => 8,
- },
-
- GB7UDX => { 11 => 8,
- 12 => 8,
- 16 => 8,
- 17 => 8,
- 19 => 8,
- 21 => 8,
- },
- GB7BAA => {
- 11 => 5,
- 12 => 8,
- 16 => 8,
- 17 => 8,
- 19 => 8,
- 21 => 8,
- },
-};
-</PRE>
-</CODE></BLOCKQUOTE>
-<P>
-<P>Each set of hops is contained within a pair of curly braces and contains a
-series of PC frame types. PC11 for example is a DX spot. The figures here
-are not exhaustive but should give you a good idea of how the file works.
-<P>
-<P>You can alter this file at any time, including whilst the cluster is running.
-If you alter the file during runtime, the command <EM>load/hops</EM> will
-bring your changes into effect.
-<P>
-<H2><A NAME="ss5.2">5.2 Isolating networks</A>
-</H2>
-
-<P>It is possible to isolate networks from each other on a "gateway" node using the
-<EM>set/isolate <node_call></EM> command.
-<P>
-<P>The effect of this is to partition an isolated network completely from another
-nodes connected to your node. Your node will appear on and otherwise behave
-normally on every network to which you are connected, but data from an isolated
-network will not cross onto any other network or vice versa. However all the
-spot, announce and WWV traffic and personal messages will still be handled
-locally (because you are a real node on all connected networks), that is locally
-connected users will appear on all networks and will be able to access and
-receive information from all networks transparently. All routed messages will
-be sent as normal, so if a user on one network knows that you are a gateway for
-another network, he can still still send a talk/announce etc message via your
-node and it will be routed across.
-<P>
-<P>The only limitation currently is that non-private messages cannot be passed down
-isolated links regardless of whether they are generated locally. This will change
-when the bulletin routing facility is added.
-<P>
-<P>If you use isolate on a node connection you will continue to receive all
-information from the isolated partner, however you will not pass any information
-back to the isolated node. There are times when you would like to forward only
-spots across a link (maybe during a contest for example). To do this, isolate
-the node in the normal way and put in a filter in the /spider/filter/spots
-directory to override the isolate. This filter can be very simple and consists
-of just one line ....
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
-$in = [
- [ 1, 0, 'd', 0, 3] # The last figure (3) is the hop count
-];
-</PRE>
-</CODE></BLOCKQUOTE>
-<P>
-<P>There is a lot more on filtering in the next section.
-<P>
-<HR>
-<A HREF="adminmanual-6.html">Next</A>
-<A HREF="adminmanual-4.html">Previous</A>
-<A HREF="adminmanual.html#toc5">Contents</A>
-</BODY>
-</HTML>
+++ /dev/null
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN">
-<HTML>
-<HEAD>
- <META NAME="GENERATOR" CONTENT="SGML-Tools 1.0.9">
- <TITLE>The DXSpider Installation and Administration Manual: Filtering (Old Style upto v1.44)</TITLE>
- <LINK HREF="adminmanual-7.html" REL=next>
- <LINK HREF="adminmanual-5.html" REL=previous>
- <LINK HREF="adminmanual.html#toc6" REL=contents>
-<link rel=stylesheet href="style.css" type="text/css" title="default stylesheet">
-</HEAD>
-<BODY>
-<A HREF="adminmanual-7.html">Next</A>
-<A HREF="adminmanual-5.html">Previous</A>
-<A HREF="adminmanual.html#toc6">Contents</A>
-<HR>
-<H2><A NAME="s6">6. Filtering (Old Style upto v1.44)</A></H2>
-
-<P>Filters can be set for spots, announcements and WWV. You will find the
-directories for these under /spider/filter. You will find some examples in
-the directories with the suffix <EM>.issue</EM>. There are two types of
-filter, one for incoming information and one for outgoing information.
-Outgoing filters are in the form <EM>CALLSIGN.pl</EM> and incoming filters
-are in the form <EM>in_CALLSIGN.pl</EM>. Filters can be set for both nodes
-and users.
-<P>
-<P>All filters work in basically the same way. There are several elements
-delimited by commas. There can be many lines in the filter and they are
-read from the top by the program. When writing a filter you need to think
-carefully about just what you want to achieve. You are either going to write
-a filter to <EM>accept</EM> or to <EM>reject</EM>. Think of a filter as
-having 2 main elements. For a reject filter, you would have a line or multiple
-lines rejecting the things you do not wish to receive and then a default line
-accepting everything else that is not included in the filter. Likewise, for an
-accept filter, you would have a line or multiple lines accepting the things you
-wish to receive and a default line rejecting everthing else.
-<P>
-<P>In the example below, a user requires a filter that would only return SSB spots
-posted in Europe on the HF bands. This is achieved by first rejecting the CW
-section of each HF band and rejecting all of VHF, UHF etc based on frequency.
-Secondly, a filter rule is set based on CQ zones to only accept spots posted in
-Europe. Lastly, a default filter rule is set to reject anything outside the filter.
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
-$in = [
- [ 0, 0, 'r', # reject all CW spots
- [
- 1800.0, 1850.0,
- 3500.0, 3600.0,
- 7000.0, 7040.0,
- 14000.0, 14100.0,
- 18068.0, 18110.0,
- 21000.0, 21150.0,
- 24890.0, 24930.0,
- 28000.0, 28180.0,
- 30000.0, 49000000000.0,
- ] ,1 ],
- [ 1, 11, 'n', [ 14, 15, 16, 20, 33, ], 15 ], #accept EU
- [ 0, 0, 'd', 0, 1 ], # 1 = want, 'd' = everything else
-];
-</PRE>
-</CODE></BLOCKQUOTE>
-<P>
-<P>The actual elements of each filter are described more fully in the following
-sections.
-<P>
-<H2><A NAME="ss6.1">6.1 Spots</A>
-</H2>
-
-<P>The elements of the Spot filter are ....
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
-[action, field_no, sort, possible_values, hops]
-</PRE>
-</CODE></BLOCKQUOTE>
-<P>
-<P>There are 3 elements here to look at. Firstly, the action element. This is
-very simple and only 2 possible states exist, accept (1) or drop (0).
-<P>
-<P>The second element is the field_no. There are 13 possiblities to choose from
-here ....
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
- 0 = frequency
- 1 = call
- 2 = date in unix format
- 3 = comment
- 4 = spotter
- 5 = spotted dxcc country
- 6 = spotter's dxcc country
- 7 = origin
- 8 = spotted itu
- 9 = spotted cq
- 10 = spotter's itu
- 11 = spotter's cq
- 12 = callsign of the channel on which the spot has appeared
-</PRE>
-</CODE></BLOCKQUOTE>
-<P>
-<P>The third element tells us what to expect in the fourth element. There are
-4 possibilities ....
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
- n - numeric list of numbers e.g. [ 1,2,3 ]
- r - ranges of pairs of numbers e.g. between 2 and 4 or 10 to 17 - [ 2,4, 10,17 ]
- a - an alphanumeric regex
- d - the default rule
-</PRE>
-</CODE></BLOCKQUOTE>
-<P>
-<P>The fifth element is simply the hops to set in this filter. This would only
-be used if the filter was for a node of course and overrides the hop count in
-hop_table.pl.
-<P>
-<P>So, let's look at an example spot filter. It does not matter in the example
-who the filter is to be used for. So, what do we need in the filter? We need
-to filter the spots the user/node requires and also set a default rule for
-anything else outside the filter. Below is a simple filter that stops spots
-arriving from outside Europe.
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
-$in = [
- [ 0, 4, 'a', '^(K|N|A|W|VE|VA|J)'], # 0 = drop, 'a' = alphanumeric
- [ 1, 0, 'd', 0, 1 ], # 1 = want, 'd' = everything else
- ];
-</PRE>
-</CODE></BLOCKQUOTE>
-<P>
-<P>So the filter is wrapped in between a pair of square brackets. This tells
-Spider to look in between these limits. Then each line is contained within
-its own square brackets and ends with a comma. Lets look carefully at the first
-line. The first element is 0 (drop). Therefore anything we put on this line
-will not be accepted. The next element is 4. This means we are filtering by
-the spotter. The third element is the letter "a" which tells the program to
-expect an alphanumeric expression in the fourth element. The fourth element
-is a list of letters separated by the pipe symbol.
-<P>
-<P>What this line does is tell the program to drop any spots posted by anyone in
-the USA, Canada or Japan.
-<P>
-<P>The second line is the default rule for anything else. The "d" tells us this
-and the line simply reads... accept anything else.
-<P>
-<P>You can add as many lines as you need to complete the filter but if there are
-several lines of the same type it is neater to enclose them all as one line.
-An example of this is where specific bands are set. We could write this like
-this ....
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
-[ 0,0,'r',[1800.0, 2000.0], 1],
-[ 0,0,'r',[10100.0, 10150.0], 1],
-[ 0,0,'r',[14000.0, 14350.0], 1],
-[ 0,0,'r',[18000.0, 18200.0], 1],
-</PRE>
-</CODE></BLOCKQUOTE>
-<P>
-<P>But the line below achieves the same thing and is more efficient ....
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
- [ 0, 0, 'r',
- [
- 1800.0, 2000.0, # top band
- 10100.0, 10150.0, # WARC
- 14000.0, 14350.0, # 20m
- 18000.0, 18200.0, # WARC
- [ ,1 ],
-</PRE>
-</CODE></BLOCKQUOTE>
-<P>
-<P>
-<H2><A NAME="ss6.2">6.2 Announcements</A>
-</H2>
-
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
-
-# This is an example announce or filter allowing only West EU announces
-#
-# The element list is:-
-# 0 - callsign of announcer
-# 1 - destination * = all, <callsign> = routed to the node
-# 2 - text
-# 3 - * - sysop, <some text> - special list eg 6MUK, ' ', normal announce
-# 4 - origin
-# 5 - 0 - announce, 1 - wx
-# 6 - channel callsign (the interface from which this spot came)
-
-$in = [
- [ 1, 0, 'a', '^(P[ABCDE]|DK0WCY|G|M|2|EI|F|ON)' ],
- [ 0, 0, 'd', 0 ]
-];
-</PRE>
-</CODE></BLOCKQUOTE>
-<P>In this example, only the prefixes listed will be allowed. It is possible to
-be quite specific. The Dutch prefix "P" is followed by several secondary
-identifiers which are allowed. So, in the example, "PA" or "PE" would be ok
-but not "PG". It is even possible to allow information from a single callsign.
-In the example this is DK0WCY, to allow the posting of his Aurora Beacon.
-<P>
-<H2><A NAME="ss6.3">6.3 WWV</A>
-</H2>
-
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
-
-# This is an example WWV filter
-#
-# The element list is:-
-# 0 - nominal unix date of spot (ie the day + hour:13)
-# 1 - the hour
-# 2 - SFI
-# 3 - K
-# 4 - I
-# 5 - text
-# 6 - spotter
-# 7 - origin
-# 8 - incoming interface callsign
-
-# this one doesn't filter, it just sets the hop count to 6 and is
-# used mainly just to override any isolation from WWV coming from
-# the internet.
-
-$in = [
- [ 1, 0, 'd', 0, 6 ]
-];
-</PRE>
-</CODE></BLOCKQUOTE>
-<P>
-<P>It should be noted that the filter will start to be used only once a user/node
-has logged out and back in again.
-<P>I am not going to spend any more time on these filters now as they will become
-more "comprehensive" in the near future.
-<P>
-<HR>
-<A HREF="adminmanual-7.html">Next</A>
-<A HREF="adminmanual-5.html">Previous</A>
-<A HREF="adminmanual.html#toc6">Contents</A>
-</BODY>
-</HTML>
+++ /dev/null
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN">
-<HTML>
-<HEAD>
- <META NAME="GENERATOR" CONTENT="SGML-Tools 1.0.9">
- <TITLE>The DXSpider Installation and Administration Manual: Filtering (New Style v1.45 and later)</TITLE>
- <LINK HREF="adminmanual-8.html" REL=next>
- <LINK HREF="adminmanual-6.html" REL=previous>
- <LINK HREF="adminmanual.html#toc7" REL=contents>
-<link rel=stylesheet href="style.css" type="text/css" title="default stylesheet">
-</HEAD>
-<BODY>
-<A HREF="adminmanual-8.html">Next</A>
-<A HREF="adminmanual-6.html">Previous</A>
-<A HREF="adminmanual.html#toc7">Contents</A>
-<HR>
-<H2><A NAME="s7">7. Filtering (New Style v1.45 and later)</A></H2>
-
-<H2><A NAME="ss7.1">7.1 General filter rules</A>
-</H2>
-
-<P>Upto v1.44 it was not possible for the user to set their own filters. From
-v1.45 though that has all changed. It is now possible to set filters for just
-about anything you wish. If you have just updated from an older version of
-DXSpider you will need to update your new filters. You do not need to do
-anything with your old filters, they will be renamed as you update.
-<P>
-<P>There are 3 basic commands involved in setting and manipulating filters. These
-are <EM>accept</EM>, <EM>reject</EM> and <EM>clear</EM>. First we will look
-generally at filtering. There are a number of things you can filter in the
-DXSpider system. They all use the same general mechanism.
-<P>
-<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>
-<BLOCKQUOTE><CODE>
-<PRE>
-
-accept/spots .....
-reject/spots .....
-</PRE>
-</CODE></BLOCKQUOTE>
-<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. They are ...
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
-clear/spots 1
-clear/spots all
-</PRE>
-</CODE></BLOCKQUOTE>
-<P>There is clear/xxxx command for each type of filter.
-<P>
-<P>and you can check that your filters have worked by the command ...
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
-
-show/filter
-</PRE>
-</CODE></BLOCKQUOTE>
-<P>
-<P>For now we are going to use spots for the examples, but you can apply the same
-principles to all types of filter.
-<P>
-<H2><A NAME="ss7.2">7.2 Types of filter</A>
-</H2>
-
-<P>There are two main types of filter, <EM>accept</EM> or <EM>reject</EM>. You
-can use either to achieve the result you want dependent on your own preference
-and which is more simple to do. It is pointless writing 8 lines of reject
-filters when 1 accept filter would do the same thing! 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 take it)
-<P>
-<P>If you specify reject filters, then any lines that arrive that match the filter
-will be dumped but all else will be accepted. If you use an accept filter,
-then ONLY the lines in the filter will be accepted and all else will be dumped.
-For example if you have a single line <EM>accept</EM> filter ...
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
-accept/spots on vhf and (by_zone 14,15,16 or call_zone 14,15,16)
-</PRE>
-</CODE></BLOCKQUOTE>
-<P>then you will <EM>ONLY</EM> get VHF spots <EM>from</EM> or <EM>to</EM> CQ zones
-14, 15 and 16.
-<P>
-<P>If you set a reject filter like this ...
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
-reject/spots on hf/cw
-</PRE>
-</CODE></BLOCKQUOTE>
-<P>Then you will get everything <EM>EXCEPT</EM> HF CW spots. You could make this
-single filter even more flexible. For example, if you are interested in IOTA
-and will work it even on CW even though normally you are not interested in
-CW, then you could say ...
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
-reject/spots on hf/cw and not info iota
-</PRE>
-</CODE></BLOCKQUOTE>
-<P>But in that case you might only be interested in iota and say:-
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
-accept/spots not on hf/cw or info iota
-</PRE>
-</CODE></BLOCKQUOTE>
-<P>which achieves exactly the same thing. You should choose one or the other
-until you are comfortable with the way it works. You can mix them if you
-wish (actually you can have an accept AND a reject on the same line) but
-don't attempt this until you are sure you know what you are doing!
-<P>
-<P>You can arrange your filter lines into logical units, either for your own
-understanding or simply convenience. Here is an example ...
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
-reject/spots 1 on hf/cw
-reject/spots 2 on 50000/1400000 not (by_zone 14,15,16 or call_zone 14,15,16)
-</PRE>
-</CODE></BLOCKQUOTE>
-<P>What this does is to ignore all HF CW spots and also rejects any spots on VHF
-which don't either originate or spot someone in Europe.
-<P>
-<P>This is an example where you would use a line number (1 and 2 in this case), if
-you leave the digit out, the system assumes '1'. Digits '0'-'9' are available.
-This make it easier to see just what filters you have set. It also makes it
-more simple to remove individual filters, during a contest for example.
-<P>
-<P>You will notice in the above example that the second line has brackets. Look
-at the line logically. You can see there are 2 separate sections to it. We
-are saying reject spots that are VHF or above <EM>APART</EM> from those in
-zones 14, 15 and 16 (either spotted there or originated there). If you did
-not have the brackets to separate the 2 sections, then Spider would read it
-logically from the front and see a different expression entirely ...
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
-(on 50000/1400000 and by_zone 14,15,16) or call_zone 14,15,16
-</PRE>
-</CODE></BLOCKQUOTE>
-<P>The simple way to remember this is, if you use OR - use brackets. Whilst we are
-here CASE is not important. 'And BY_Zone' is just the same as 'and by_zone'.
-<P>As mentioned earlier, setting several filters can be more flexible than
-simply setting one complex one. Doing it in this way means that if you want
-to alter your filter you can just redefine or remove one or more lines of it or
-one line. For example ...
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
-reject/spots 1 on hf/ssb
-</PRE>
-</CODE></BLOCKQUOTE>
-<P>would redefine our earlier example, or
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
-clear/spots 1
-</PRE>
-</CODE></BLOCKQUOTE>
-<P>To remove all the filter lines in the spot filter ...
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
-clear/spots all
-</PRE>
-</CODE></BLOCKQUOTE>
-<P>
-<H2><A NAME="ss7.3">7.3 Filter options</A>
-</H2>
-
-<P>You can filter in several different ways. The options are listed in the
-various helpfiles for accept, reject and filter.
-<P>
-<H2><A NAME="ss7.4">7.4 Default filters</A>
-</H2>
-
-<P>Sometimes all that is needed is a general rule for node connects. This can
-be done with a node_default filter. This rule will always be followed, even
-if the link is isolated, unless another filter is set specifically. Default
-rules can be set for nodes and users. They can be set for spots, announces,
-WWV and WCY. They can also be used for hops. An example might look like
-this ...
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
-accept/spot node_default by_zone 14,15,16,20,33
-set/hops node_default spot 50
-</PRE>
-</CODE></BLOCKQUOTE>
-<P>This filter is for spots only, you could set others for announce, WWV and WCY.
-This filter would work for ALL nodes unless a specific filter is written to
-override it for a particular node. You can also set a user_default should
-you require. It is important to note that default filters should be
-considered to be "connected". By this I mean that should you override the
-default filter for spots, you need to add a rule for the hops for spots also.
-<P>
-<H2><A NAME="ss7.5">7.5 Advanced filtering</A>
-</H2>
-
-<P>Once you are happy with the results you get, you may like to experiment.
-<P>
-<P>The previous example that filters hf/cw spots and accepts vhf/uhf spots from EU
-can be written with a mixed filter, for example ...
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
-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)
-</PRE>
-</CODE></BLOCKQUOTE>
-<P>Note that the first filter has not been specified with a number. This will
-automatically be assumed to be number 1. In this case, we have said <EM>reject all
-HF spots in the CW section of the bands but accept all others at HF. Also
-accept anything in VHF and above spotted in or by operators in the zones
-14, 15 and 16</EM>. Each filter slot actually has a 'reject' slot and
-an 'accept' slot. The reject slot is executed BEFORE the accept slot.
-<P>
-<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 through everything else on HF. The next filter line
-lets through just VHF/UHF spots from EU.
-<P>
-<P>
-<HR>
-<A HREF="adminmanual-8.html">Next</A>
-<A HREF="adminmanual-6.html">Previous</A>
-<A HREF="adminmanual.html#toc7">Contents</A>
-</BODY>
-</HTML>
+++ /dev/null
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN">
-<HTML>
-<HEAD>
- <META NAME="GENERATOR" CONTENT="SGML-Tools 1.0.9">
- <TITLE>The DXSpider Installation and Administration Manual: Other filters</TITLE>
- <LINK HREF="adminmanual-9.html" REL=next>
- <LINK HREF="adminmanual-7.html" REL=previous>
- <LINK HREF="adminmanual.html#toc8" REL=contents>
-<link rel=stylesheet href="style.css" type="text/css" title="default stylesheet">
-</HEAD>
-<BODY>
-<A HREF="adminmanual-9.html">Next</A>
-<A HREF="adminmanual-7.html">Previous</A>
-<A HREF="adminmanual.html#toc8">Contents</A>
-<HR>
-<H2><A NAME="s8">8. Other filters</A></H2>
-
-<H2><A NAME="ss8.1">8.1 Filtering Mail</A>
-</H2>
-
-<P>In the /spider/msg directory you will find a file called badmsg.pl.issue. Rename
-this to badmsg.pl and edit the file. The original looks something like this ....
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
-
-# the list of regexes for messages that we won't store having
-# received them (bear in mind that we must receive them fully before
-# we can bin them)
-
-
-# The format of each line is as follows
-
-# type source pattern
-# P/B/F T/F/O/S regex
-
-# type: P - private, B - bulletin (msg), F - file (ak1a bull)
-# source: T - to field, F - from field, O - origin, S - subject
-# pattern: a perl regex on the field requested
-
-# Currently only type B and P msgs are affected by this code.
-#
-# The list is read from the top down, the first pattern that matches
-# causes the action to be taken.
-
-# The pattern can be undef or 0 in which case it will always be selected
-# for the action specified
-
-
-
-package DXMsg;
-
-@badmsg = (
-'B', 'T', 'SALE',
-'B', 'T', 'WANTED',
-'B', 'S', 'WANTED',
-'B', 'S', 'SALE',
-'B', 'S', 'WTB',
-'B', 'S', 'WTS',
-'B', 'T', 'FS',
-);
-</PRE>
-</CODE></BLOCKQUOTE>
-<P>
-<P>I think this is fairly self explanatory. It is simply a list of subject
-headers that we do not want to pass on to either the users of the cluster or
-the other cluster nodes that we are linked to. This is usually because of
-rules and regulations pertaining to items for sale etc in a particular country.
-<P>
-<H2><A NAME="ss8.2">8.2 Filtering DX callouts (Depricated)</A>
-</H2>
-
-<P><B><I>From version 1.47, this method is replaced by the command set/baddx</I></B>
-<P>
-<P>In the same way as mail, there are some types of spot we do not wish to pass on
-to users or linked cluster nodes. In the /spider/data directory you will find
-a file called baddx.pl.issue. Rename this to baddx.pl and edit the file. The
-original looks like this ....
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
-
-# the list of dx spot addresses that we don't store and don't pass on
-
-
-package DXProt;
-
-@baddx = qw
-
- FROG
- SALE
- FORSALE
- WANTED
- P1RATE
- PIRATE
- TEST
- DXTEST
- NIL
- NOCALL
-);
-</PRE>
-</CODE></BLOCKQUOTE>
-<P>
-<P>Again, this is simply a list of names we do not want to see in the spotted
-field of a DX callout.
-<P>
-<P>
-<H2><A NAME="ss8.3">8.3 Filtering words from text fields in Announce, Talk and DX spots</A>
-</H2>
-
-<P>Create a file in /spider/data called <EM>badwords</EM>. The format is quite
-simple. Lines beginning with # are ignored so comments can be added. An
-example file is below ...
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
-# Below is a list of words we do not wish to see on the cluster
-grunge grunged grunging
-splodge splodger splodging
-grince
-fluffle
-</PRE>
-</CODE></BLOCKQUOTE>
-<P>Multiple words can be used on the same line as shown. Obviously these
-are just examples :-)
-<P>
-<P>You can reload the file from the cluster prompt as sysop with load/badwords.
-<P>
-<HR>
-<A HREF="adminmanual-9.html">Next</A>
-<A HREF="adminmanual-7.html">Previous</A>
-<A HREF="adminmanual.html#toc8">Contents</A>
-</BODY>
-</HTML>
+++ /dev/null
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN">
-<HTML>
-<HEAD>
- <META NAME="GENERATOR" CONTENT="SGML-Tools 1.0.9">
- <TITLE>The DXSpider Installation and Administration Manual: Mail</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>
-<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. Mail</A></H2>
-
-<P>DXSpider deals seamlessly with standard AK1A type mail. It supports both
-personal and bulletin mail and the sysop has additional commands to ensure
-that mail gets to where it is meant. DXSpider will send mail almost
-immediately, assuming that the target is on line. However, only one
-mail message is dealt with at any one time. If a mail message is already
-being sent or recieved, then the new message will be queued until it has
-finished.
-<P>The cluster mail is automatically deleted after 30 days unless the sysop
-sets the "keep" flag using the <EM>msg</EM> command.
-<P>
-<H2><A NAME="ss9.1">9.1 Personal mail</A>
-</H2>
-
-<P>Personal mail is sent using the <EM>sp</EM> command. This is actually the
-default method of sending mail and so a simple <EM>s</EM> for send will do.
-A full list of the send commands and options is in the <EM>command set</EM>
-section, so I will not duplicate them here.
-<P>
-<H2><A NAME="ss9.2">9.2 Bulletin mail</A>
-</H2>
-
-<P>Bulletin mail is sent by using the <EM>sb</EM> command. This is one of the
-most common mistakes users make when sending mail. They send a bulletin
-mail with <EM>s</EM> or <EM>sp</EM> instead of <EM>sb</EM> and of course
-the message never leaves the cluster. This can be rectified by the sysop
-by using the <EM>msg</EM> command.
-<P>
-<P>Bulletin addresses can be set using the Forward.pl file.
-<P>
-<H2><A NAME="ss9.3">9.3 Forward.pl</A>
-</H2>
-
-<P>DXSpider receives all and any mail sent to it without any alterations needed
-in files. Because personal and bulletin mail are treated differently, there
-is no need for a list of accepted bulletin addresses. It is necessary, however,
-to tell the program which links accept which bulletins. For example, it is
-pointless sending bulletins addresses to "UK" to any links other than UK
-ones. The file that does this is called forward.pl and lives in /spider/msg.
-At default, like other spider files it is named forward.pl.issue. Rename it
-to forward.pl and edit the file to match your requirements.
-The format is below ...
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
-#
-# this is an example message forwarding file for the system
-#
-# The format of each line is as follows
-#
-# type to/from/at pattern action destinations
-# P/B/F T/F/A regex I/F [ call [, call ...] ]
-#
-# type: P - private, B - bulletin (msg), F - file (ak1a bull)
-# to/from/at: T - to field, F - from field, A - home bbs, O - origin
-# pattern: a perl regex on the field requested
-# action: I - ignore, F - forward
-# destinations: a reference to an array containing node callsigns
-#
-# if it is non-private and isn't in here then it won't get forwarded
-#
-# Currently only type B msgs are affected by this code.
-#
-# The list is read from the top down, the first pattern that matches
-# causes the action to be taken.
-#
-# The pattern can be undef or 0 in which case it will always be selected
-# for the action specified
-#
-# If the BBS list is undef or 0 and the action is 'F' (and it matches the
-# pattern) then it will always be forwarded to every node that doesn't have
-# it (I strongly recommend you don't use this unless you REALLY mean it, if
-# you allow a new link with this on EVERY bull will be forwarded immediately
-# on first connection)
-#
-
-package DXMsg;
-
-@forward = (
-'B', 'T', 'LOCAL', 'F', [ qw(GB7MBC) ],
-'B', 'T', 'ALL', 'F', [ qw(GB7BAA GB7ADX PA4AB-14) ],
-'B', 'T', 'UK', 'F', [ qw(GB7BAA GB7ADX) ],
-'B', 'T', 'QSL', 'F', [ qw(GB7BAA GB7ADX PA4AB-14) ],
-'B', 'T', 'QSLINF', 'F', [ qw(GB7BAA GB7ADX PA4AB-14) ],
-'B', 'T', 'DX', 'F', [ qw(GB7BAA GB7ADX PA4AB-14) ],
-'B', 'T', 'DXINFO', 'F', [ qw(GB7BAA GB7ADX PA4AB-14) ],
-'B', 'T', 'DXNEWS', 'F', [ qw(GB7BAA GB7ADX PA4AB-14) ],
-'B', 'T', 'DXQSL', 'F', [ qw(GB7BAA GB7ADX PA4AB-14) ],
-'B', 'T', 'SYSOP', 'F', [ qw(GB7BAA GB7ADX) ],
-'B', 'T', '50MHZ', 'F', [ qw(GB7BAA GB7ADX PA4AB-14) ],
-);
-</PRE>
-</CODE></BLOCKQUOTE>
-<P>Simply insert a bulletin address and state in the brackets where you wish
-that mail to go. For example, you can see here that mail sent to "UK" will
-only be sent to the UK links and not to PA4AB-14.
-<P>
-<P>To force the cluster to reread the file use load/forward
-<P>
-<P>
-<H2><A NAME="ss9.4">9.4 The msg command</A>
-</H2>
-
-<P>The <EM>msg</EM> command is a very powerful and flexible tool for the
-sysop. It allows the sysop to alter to and from fields and make other
-changes to manage the cluster mail.
-<P>Here is a full list of the various options ...
-<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 waiting 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>These commands are simply typed from within the cluster as the sysop user.
-<P>
-<H2><A NAME="ss9.5">9.5 Message status</A>
-</H2>
-
-<P>You can check on a message from within the cluster by using the command
-<EM>stat/msg</EM>. This will give you additional information on the
-message number including which nodes have received it, which node it
-was received from and when etc. Here is an example of the output of
-the command ...
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
-G0VGS de GB7MBC 28-Jan-2001 1308Z >
-stat/msg 6869
- From: GB7DJK
- Msg Time: 26-Jan-2001 1302Z
- Msgno: 6869
- Origin: GB7DJK
- Size: 8012
- Subject: AMSAT 2line KEPS 01025.AMSAT
- To: UK
-Got it Nodes: GB7BAA, GB7ADX
- Private: 0
-Read Confirm: 0
- Times read: 0
-G0VGS de GB7MBC 28-Jan-2001 1308Z >
-</PRE>
-</CODE></BLOCKQUOTE>
-<P>
-<H2><A NAME="ss9.6">9.6 Filtering mail</A>
-</H2>
-
-<P>This is described in the section on <EM>Other filters</EM> so I will not
-duplicate it here.
-<P>
-<H2><A NAME="ss9.7">9.7 Distribution lists</A>
-</H2>
-
-<P>Distribution lists are simply a list of users to send certain types of
-mail to. An example of this is mail you only wish to send to other
-sysops. In /spider/msg there is a directory called <EM>distro</EM>. You
-put any distibution lists in here. For example, here is a file called
-SYSOP.pl that caters for the UK sysops.
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
-qw(GB7TLH GB7DJK GB7DXM GB7CDX GB7BPQ GB7DXN GB7MBC GB7MBC-6 GB7MDX
- GB7NDX GB7SDX GB7TDX GB7UDX GB7YDX GB7ADX GB7BAA GB7DXA GB7DXH
- GB7DXK GB7DXI GB7DXS)
-</PRE>
-</CODE></BLOCKQUOTE>
-<P>Any mail sent to "sysop" would only be sent to the callsigns in this list.
-<P>
-<H2><A NAME="ss9.8">9.8 BBS interface</A>
-</H2>
-
-<P>Spider provides a simple BBS interface. No input is required from the sysop
-of the cluster at all. The BBS simply sets the cluster as a BBS and pushes
-any required mail to the cluster. No mail can flow from Spider to the BBS,
-the interface is one-way.
-<P>
-<P>Please be careful not to flood the cluster network with unnecessary mail.
-Make sure you only send mail to the clusters that want it by using the
-Forward.pl file very carefully.
-<P>
-<HR>
-<A HREF="adminmanual-10.html">Next</A>
-<A HREF="adminmanual-8.html">Previous</A>
-<A HREF="adminmanual.html#toc9">Contents</A>
-</BODY>
-</HTML>
+++ /dev/null
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN">
-<HTML>
-<HEAD>
- <META NAME="GENERATOR" CONTENT="SGML-Tools 1.0.9">
- <TITLE>The DXSpider Installation and Administration Manual</TITLE>
- <LINK HREF="adminmanual-1.html" REL=next>
-
-
-<link rel=stylesheet href="style.css" type="text/css" title="default stylesheet">
-</HEAD>
-<BODY>
-<A HREF="adminmanual-1.html">Next</A>
-Previous
-Contents
-<HR>
-<H1>The DXSpider Installation and Administration Manual</H1>
-
-<H2>Ian Maude, G0VGS, (ianmaude@btinternet.com)</H2>Version 1.47 (Revision 1.30), April 2001
-<P><HR>
-<EM>A reference for SysOps of the DXSpider DXCluster program.</EM>
-<HR>
-<P>
-<H2><A NAME="toc1">1.</A> <A HREF="adminmanual-1.html">Installation (Original version by Iain Philipps, G0RDI)</A></H2>
-
-<UL>
-<LI><A HREF="adminmanual-1.html#ss1.1">1.1 Introduction</A>
-<LI><A HREF="adminmanual-1.html#ss1.2">1.2 Preparation</A>
-<LI><A HREF="adminmanual-1.html#ss1.3">1.3 Installing the software</A>
-<LI><A HREF="adminmanual-1.html#ss1.4">1.4 Setting callsigns etc</A>
-<LI><A HREF="adminmanual-1.html#ss1.5">1.5 Starting up for the first time</A>
-<LI><A HREF="adminmanual-1.html#ss1.6">1.6 The Client program</A>
-</UL>
-<P>
-<H2><A NAME="toc2">2.</A> <A HREF="adminmanual-2.html">Quick installation guide (Linux version)</A></H2>
-
-<P>
-<H2><A NAME="toc3">3.</A> <A HREF="adminmanual-3.html">Configuration</A></H2>
-
-<UL>
-<LI><A HREF="adminmanual-3.html#ss3.1">3.1 Allowing ax25 connects from users</A>
-<LI><A HREF="adminmanual-3.html#ss3.2">3.2 Allowing telnet connects from users </A>
-<LI><A HREF="adminmanual-3.html#ss3.3">3.3 Setting up telnet connects (from 1.47 onwards)</A>
-<LI><A HREF="adminmanual-3.html#ss3.4">3.4 Setting up for AGW Engine (1.47 onwards)</A>
-<LI><A HREF="adminmanual-3.html#ss3.5">3.5 Setting up node connects</A>
-<LI><A HREF="adminmanual-3.html#ss3.6">3.6 Connection scripts</A>
-<LI><A HREF="adminmanual-3.html#ss3.7">3.7 Starting the connection</A>
-<LI><A HREF="adminmanual-3.html#ss3.8">3.8 Telnet echo</A>
-</UL>
-<P>
-<H2><A NAME="toc4">4.</A> <A HREF="adminmanual-4.html">Automating things</A></H2>
-
-<UL>
-<LI><A HREF="adminmanual-4.html#ss4.1">4.1 Autostarting the cluster</A>
-<LI><A HREF="adminmanual-4.html#ss4.2">4.2 The crontab file</A>
-</UL>
-<P>
-<H2><A NAME="toc5">5.</A> <A HREF="adminmanual-5.html">Hop control</A></H2>
-
-<UL>
-<LI><A HREF="adminmanual-5.html#ss5.1">5.1 Basic hop control</A>
-<LI><A HREF="adminmanual-5.html#ss5.2">5.2 Isolating networks</A>
-</UL>
-<P>
-<H2><A NAME="toc6">6.</A> <A HREF="adminmanual-6.html">Filtering (Old Style upto v1.44)</A></H2>
-
-<UL>
-<LI><A HREF="adminmanual-6.html#ss6.1">6.1 Spots</A>
-<LI><A HREF="adminmanual-6.html#ss6.2">6.2 Announcements</A>
-<LI><A HREF="adminmanual-6.html#ss6.3">6.3 WWV</A>
-</UL>
-<P>
-<H2><A NAME="toc7">7.</A> <A HREF="adminmanual-7.html">Filtering (New Style v1.45 and later)</A></H2>
-
-<UL>
-<LI><A HREF="adminmanual-7.html#ss7.1">7.1 General filter rules</A>
-<LI><A HREF="adminmanual-7.html#ss7.2">7.2 Types of filter</A>
-<LI><A HREF="adminmanual-7.html#ss7.3">7.3 Filter options</A>
-<LI><A HREF="adminmanual-7.html#ss7.4">7.4 Default filters</A>
-<LI><A HREF="adminmanual-7.html#ss7.5">7.5 Advanced filtering</A>
-</UL>
-<P>
-<H2><A NAME="toc8">8.</A> <A HREF="adminmanual-8.html">Other filters</A></H2>
-
-<UL>
-<LI><A HREF="adminmanual-8.html#ss8.1">8.1 Filtering Mail</A>
-<LI><A HREF="adminmanual-8.html#ss8.2">8.2 Filtering DX callouts (Depricated)</A>
-<LI><A HREF="adminmanual-8.html#ss8.3">8.3 Filtering words from text fields in Announce, Talk and DX spots</A>
-</UL>
-<P>
-<H2><A NAME="toc9">9.</A> <A HREF="adminmanual-9.html">Mail</A></H2>
-
-<UL>
-<LI><A HREF="adminmanual-9.html#ss9.1">9.1 Personal mail</A>
-<LI><A HREF="adminmanual-9.html#ss9.2">9.2 Bulletin mail</A>
-<LI><A HREF="adminmanual-9.html#ss9.3">9.3 Forward.pl</A>
-<LI><A HREF="adminmanual-9.html#ss9.4">9.4 The msg command</A>
-<LI><A HREF="adminmanual-9.html#ss9.5">9.5 Message status</A>
-<LI><A HREF="adminmanual-9.html#ss9.6">9.6 Filtering mail</A>
-<LI><A HREF="adminmanual-9.html#ss9.7">9.7 Distribution lists</A>
-<LI><A HREF="adminmanual-9.html#ss9.8">9.8 BBS interface</A>
-</UL>
-<P>
-<H2><A NAME="toc10">10.</A> <A HREF="adminmanual-10.html">Databases</A></H2>
-
-<UL>
-<LI><A HREF="adminmanual-10.html#ss10.1">10.1 Creating databases</A>
-<LI><A HREF="adminmanual-10.html#ss10.2">10.2 Importing databases</A>
-<LI><A HREF="adminmanual-10.html#ss10.3">10.3 Checking available databases</A>
-<LI><A HREF="adminmanual-10.html#ss10.4">10.4 Looking up databases</A>
-<LI><A HREF="adminmanual-10.html#ss10.5">10.5 Removing databases</A>
-</UL>
-<P>
-<H2><A NAME="toc11">11.</A> <A HREF="adminmanual-11.html">Information, files and useful programs</A></H2>
-
-<UL>
-<LI><A HREF="adminmanual-11.html#ss11.1">11.1 MOTD</A>
-<LI><A HREF="adminmanual-11.html#ss11.2">11.2 Downtime message</A>
-<LI><A HREF="adminmanual-11.html#ss11.3">11.3 Other text messages</A>
-<LI><A HREF="adminmanual-11.html#ss11.4">11.4 The Aliases file</A>
-<LI><A HREF="adminmanual-11.html#ss11.5">11.5 Console.pl</A>
-<LI><A HREF="adminmanual-11.html#ss11.6">11.6 Updating kepler data</A>
-<LI><A HREF="adminmanual-11.html#ss11.7">11.7 The QRZ callbook</A>
-</UL>
-<P>
-<H2><A NAME="toc12">12.</A> <A HREF="adminmanual-12.html">CVS</A></H2>
-
-<P>
-<H2><A NAME="toc13">13.</A> <A HREF="adminmanual-13.html">The DXSpider command set</A></H2>
-
-<UL>
-<LI><A HREF="adminmanual-13.html#ss13.1">13.1 accept/announce (0)</A>
-<LI><A HREF="adminmanual-13.html#ss13.2">13.2 accept/announce (extended for sysops) (8)</A>
-<LI><A HREF="adminmanual-13.html#ss13.3">13.3 accept/spots (0)</A>
-<LI><A HREF="adminmanual-13.html#ss13.4">13.4 accept/spots (extended for sysops) (8)</A>
-<LI><A HREF="adminmanual-13.html#ss13.5">13.5 accept/wcy (0)</A>
-<LI><A HREF="adminmanual-13.html#ss13.6">13.6 accept/wcy (extended for sysops) (8)</A>
-<LI><A HREF="adminmanual-13.html#ss13.7">13.7 accept/wwv (0)</A>
-<LI><A HREF="adminmanual-13.html#ss13.8">13.8 accept/wwv (extended for sysops) (8)</A>
-<LI><A HREF="adminmanual-13.html#ss13.9">13.9 announce (0)</A>
-<LI><A HREF="adminmanual-13.html#ss13.10">13.10 announce full (0)</A>
-<LI><A HREF="adminmanual-13.html#ss13.11">13.11 announce sysop (5)</A>
-<LI><A HREF="adminmanual-13.html#ss13.12">13.12 apropos (0)</A>
-<LI><A HREF="adminmanual-13.html#ss13.13">13.13 bye (0)</A>
-<LI><A HREF="adminmanual-13.html#ss13.14">13.14 catchup (5)</A>
-<LI><A HREF="adminmanual-13.html#ss13.15">13.15 clear/spots (0)</A>
-<LI><A HREF="adminmanual-13.html#ss13.16">13.16 connect (5) </A>
-<LI><A HREF="adminmanual-13.html#ss13.17">13.17 dbavail (0)</A>
-<LI><A HREF="adminmanual-13.html#ss13.18">13.18 dbcreate (9)</A>
-<LI><A HREF="adminmanual-13.html#ss13.19">13.19 dbimport (9)</A>
-<LI><A HREF="adminmanual-13.html#ss13.20">13.20 dbremove (9)</A>
-<LI><A HREF="adminmanual-13.html#ss13.21">13.21 dbshow (0)</A>
-<LI><A HREF="adminmanual-13.html#ss13.22">13.22 debug (9)</A>
-<LI><A HREF="adminmanual-13.html#ss13.23">13.23 directory (0)</A>
-<LI><A HREF="adminmanual-13.html#ss13.24">13.24 directory (extended for sysops) (5)</A>
-<LI><A HREF="adminmanual-13.html#ss13.25">13.25 disconnect (8)</A>
-<LI><A HREF="adminmanual-13.html#ss13.26">13.26 dx (0)</A>
-<LI><A HREF="adminmanual-13.html#ss13.27">13.27 export (9)</A>
-<LI><A HREF="adminmanual-13.html#ss13.28">13.28 export_users (9)</A>
-<LI><A HREF="adminmanual-13.html#ss13.29">13.29 forward/latlong (8)</A>
-<LI><A HREF="adminmanual-13.html#ss13.30">13.30 forward/opername (1)</A>
-<LI><A HREF="adminmanual-13.html#ss13.31">13.31 help (0)</A>
-<LI><A HREF="adminmanual-13.html#ss13.32">13.32 init (5)</A>
-<LI><A HREF="adminmanual-13.html#ss13.33">13.33 kill (0)</A>
-<LI><A HREF="adminmanual-13.html#ss13.34">13.34 kill (5)</A>
-<LI><A HREF="adminmanual-13.html#ss13.35">13.35 kill full (5)</A>
-<LI><A HREF="adminmanual-13.html#ss13.36">13.36 links (0)</A>
-<LI><A HREF="adminmanual-13.html#ss13.37">13.37 load/aliases (9)</A>
-<LI><A HREF="adminmanual-13.html#ss13.38">13.38 load/baddx (9)</A>
-<LI><A HREF="adminmanual-13.html#ss13.39">13.39 load/badmsg (9)</A>
-<LI><A HREF="adminmanual-13.html#ss13.40">13.40 load/badwords (9)</A>
-<LI><A HREF="adminmanual-13.html#ss13.41">13.41 load/bands (9)</A>
-<LI><A HREF="adminmanual-13.html#ss13.42">13.42 load/cmd_cache (9)</A>
-<LI><A HREF="adminmanual-13.html#ss13.43">13.43 load/forward (9)</A>
-<LI><A HREF="adminmanual-13.html#ss13.44">13.44 load/messages (9)</A>
-<LI><A HREF="adminmanual-13.html#ss13.45">13.45 load/prefixes (9)</A>
-<LI><A HREF="adminmanual-13.html#ss13.46">13.46 merge (5)</A>
-<LI><A HREF="adminmanual-13.html#ss13.47">13.47 msg (9)</A>
-<LI><A HREF="adminmanual-13.html#ss13.48">13.48 pc (8)</A>
-<LI><A HREF="adminmanual-13.html#ss13.49">13.49 ping (1)</A>
-<LI><A HREF="adminmanual-13.html#ss13.50">13.50 rcmd (1)</A>
-<LI><A HREF="adminmanual-13.html#ss13.51">13.51 read (0)</A>
-<LI><A HREF="adminmanual-13.html#ss13.52">13.52 read (extended for sysops) (5) </A>
-<LI><A HREF="adminmanual-13.html#ss13.53">13.53 reject/announce</A>
-<LI><A HREF="adminmanual-13.html#ss13.54">13.54 reject/announce (extended for sysops) (8)</A>
-<LI><A HREF="adminmanual-13.html#ss13.55">13.55 reject/spots (0)</A>
-<LI><A HREF="adminmanual-13.html#ss13.56">13.56 reject/spots (extended for sysops) (8)</A>
-<LI><A HREF="adminmanual-13.html#ss13.57">13.57 reject/wcy (0)</A>
-<LI><A HREF="adminmanual-13.html#ss13.58">13.58 reject/wcy (extended for sysops) (8)</A>
-<LI><A HREF="adminmanual-13.html#ss13.59">13.59 reject/wwv (0)</A>
-<LI><A HREF="adminmanual-13.html#ss13.60">13.60 reject/wwv (extended for sysops) (8)</A>
-<LI><A HREF="adminmanual-13.html#ss13.61">13.61 reply (0)</A>
-<LI><A HREF="adminmanual-13.html#ss13.62">13.62 send (0)</A>
-<LI><A HREF="adminmanual-13.html#ss13.63">13.63 set/address (0)</A>
-<LI><A HREF="adminmanual-13.html#ss13.64">13.64 set/announce (0)</A>
-<LI><A HREF="adminmanual-13.html#ss13.65">13.65 set/arcluster (5)</A>
-<LI><A HREF="adminmanual-13.html#ss13.66">13.66 set/baddx (8)</A>
-<LI><A HREF="adminmanual-13.html#ss13.67">13.67 set/badnode (6)</A>
-<LI><A HREF="adminmanual-13.html#ss13.68">13.68 set/badspotter (8)</A>
-<LI><A HREF="adminmanual-13.html#ss13.69">13.69 set/beep (0)</A>
-<LI><A HREF="adminmanual-13.html#ss13.70">13.70 set/clx (5)</A>
-<LI><A HREF="adminmanual-13.html#ss13.71">13.71 set/debug (9)</A>
-<LI><A HREF="adminmanual-13.html#ss13.72">13.72 set/dx (0)</A>
-<LI><A HREF="adminmanual-13.html#ss13.73">13.73 set/dxgrid (0)</A>
-<LI><A HREF="adminmanual-13.html#ss13.74">13.74 set/dxnet (5)</A>
-<LI><A HREF="adminmanual-13.html#ss13.75">13.75 set/echo (0)</A>
-<LI><A HREF="adminmanual-13.html#ss13.76">13.76 set/here (0)</A>
-<LI><A HREF="adminmanual-13.html#ss13.77">13.77 set/homenode (0)</A>
-<LI><A HREF="adminmanual-13.html#ss13.78">13.78 set/hops (8)</A>
-<LI><A HREF="adminmanual-13.html#ss13.79">13.79 set/isolate (9)</A>
-<LI><A HREF="adminmanual-13.html#ss13.80">13.80 set/language (0)</A>
-<LI><A HREF="adminmanual-13.html#ss13.81">13.81 set/location (0)</A>
-<LI><A HREF="adminmanual-13.html#ss13.82">13.82 set/sys_location (9)</A>
-<LI><A HREF="adminmanual-13.html#ss13.83">13.83 set/logininfo (0)</A>
-<LI><A HREF="adminmanual-13.html#ss13.84">13.84 set/lockout (9)</A>
-<LI><A HREF="adminmanual-13.html#ss13.85">13.85 set/name (0)</A>
-<LI><A HREF="adminmanual-13.html#ss13.86">13.86 set/node (9)</A>
-<LI><A HREF="adminmanual-13.html#ss13.87">13.87 set/obscount (9)</A>
-<LI><A HREF="adminmanual-13.html#ss13.88">13.88 set/page (0)</A>
-<LI><A HREF="adminmanual-13.html#ss13.89">13.89 set/password (9)</A>
-<LI><A HREF="adminmanual-13.html#ss13.90">13.90 set/pinginterval (9)</A>
-<LI><A HREF="adminmanual-13.html#ss13.91">13.91 set/privilege (9)</A>
-<LI><A HREF="adminmanual-13.html#ss13.92">13.92 set/spider (5)</A>
-<LI><A HREF="adminmanual-13.html#ss13.93">13.93 set/sys_qra (9)</A>
-<LI><A HREF="adminmanual-13.html#ss13.94">13.94 set/qra (0)</A>
-<LI><A HREF="adminmanual-13.html#ss13.95">13.95 set/qth (0)</A>
-<LI><A HREF="adminmanual-13.html#ss13.96">13.96 set/talk (0)</A>
-<LI><A HREF="adminmanual-13.html#ss13.97">13.97 set/wcy (0)</A>
-<LI><A HREF="adminmanual-13.html#ss13.98">13.98 set/wwv (0)</A>
-<LI><A HREF="adminmanual-13.html#ss13.99">13.99 set/wx (0)</A>
-<LI><A HREF="adminmanual-13.html#ss13.100">13.100 show/baddx (1)</A>
-<LI><A HREF="adminmanual-13.html#ss13.101">13.101 show/badnode (6)</A>
-<LI><A HREF="adminmanual-13.html#ss13.102">13.102 show/badspotter (1)</A>
-<LI><A HREF="adminmanual-13.html#ss13.103">13.103 show/configuration (0)</A>
-<LI><A HREF="adminmanual-13.html#ss13.104">13.104 show/configuration/node (0)</A>
-<LI><A HREF="adminmanual-13.html#ss13.105">13.105 show/connect (1)</A>
-<LI><A HREF="adminmanual-13.html#ss13.106">13.106 show/date (0)</A>
-<LI><A HREF="adminmanual-13.html#ss13.107">13.107 show/debug (9)</A>
-<LI><A HREF="adminmanual-13.html#ss13.108">13.108 show/dx (0)</A>
-<LI><A HREF="adminmanual-13.html#ss13.109">13.109 show/dxcc (0)</A>
-<LI><A HREF="adminmanual-13.html#ss13.110">13.110 show/files (0)</A>
-<LI><A HREF="adminmanual-13.html#ss13.111">13.111 show/filter (0)</A>
-<LI><A HREF="adminmanual-13.html#ss13.112">13.112 show/filter (extended for sysops) (5)</A>
-<LI><A HREF="adminmanual-13.html#ss13.113">13.113 show/hops (8)</A>
-<LI><A HREF="adminmanual-13.html#ss13.114">13.114 show/isolate (1)</A>
-<LI><A HREF="adminmanual-13.html#ss13.115">13.115 show/lockout (9)</A>
-<LI><A HREF="adminmanual-13.html#ss13.116">13.116 show/log (8)</A>
-<LI><A HREF="adminmanual-13.html#ss13.117">13.117 show/moon (0)</A>
-<LI><A HREF="adminmanual-13.html#ss13.118">13.118 show/muf (0)</A>
-<LI><A HREF="adminmanual-13.html#ss13.119">13.119 show/node (1)</A>
-<LI><A HREF="adminmanual-13.html#ss13.120">13.120 show/prefix (0)</A>
-<LI><A HREF="adminmanual-13.html#ss13.121">13.121 show/program (5)</A>
-<LI><A HREF="adminmanual-13.html#ss13.122">13.122 show/qra (0)</A>
-<LI><A HREF="adminmanual-13.html#ss13.123">13.123 show/qrz (0)</A>
-<LI><A HREF="adminmanual-13.html#ss13.124">13.124 show/route (0)</A>
-<LI><A HREF="adminmanual-13.html#ss13.125">13.125 show/satellite (0)</A>
-<LI><A HREF="adminmanual-13.html#ss13.126">13.126 show/sun (0)</A>
-<LI><A HREF="adminmanual-13.html#ss13.127">13.127 show/time (0)</A>
-<LI><A HREF="adminmanual-13.html#ss13.128">13.128 show/wcy (0)</A>
-<LI><A HREF="adminmanual-13.html#ss13.129">13.129 show/wwv (0)</A>
-<LI><A HREF="adminmanual-13.html#ss13.130">13.130 shutdown (5)</A>
-<LI><A HREF="adminmanual-13.html#ss13.131">13.131 spoof (9)</A>
-<LI><A HREF="adminmanual-13.html#ss13.132">13.132 stat/db (5)</A>
-<LI><A HREF="adminmanual-13.html#ss13.133">13.133 stat/channel (5)</A>
-<LI><A HREF="adminmanual-13.html#ss13.134">13.134 stat/msg (5)</A>
-<LI><A HREF="adminmanual-13.html#ss13.135">13.135 stat/user (5)</A>
-<LI><A HREF="adminmanual-13.html#ss13.136">13.136 sysop (0)</A>
-<LI><A HREF="adminmanual-13.html#ss13.137">13.137 talk (0)</A>
-<LI><A HREF="adminmanual-13.html#ss13.138">13.138 type (0)</A>
-<LI><A HREF="adminmanual-13.html#ss13.139">13.139 who (0)</A>
-<LI><A HREF="adminmanual-13.html#ss13.140">13.140 wx (0)</A>
-<LI><A HREF="adminmanual-13.html#ss13.141">13.141 wx (enhanced for sysops) (5)</A>
-</UL>
-<HR>
-<A HREF="adminmanual-1.html">Next</A>
-Previous
-Contents
-</BODY>
-</HTML>
+++ /dev/null
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN">
-<HTML>
-<HEAD>
- <META NAME="GENERATOR" CONTENT="SGML-Tools 1.0.9">
- <TITLE>The Installation Guide for DXSpider under Microsoft Windows: Introduction</TITLE>
- <LINK HREF="wininstallation-2.html" REL=next>
-
- <LINK HREF="wininstallation.html#toc1" REL=contents>
-<link rel=stylesheet href="style.css" type="text/css" title="default stylesheet">
-</HEAD>
-<BODY>
-<A HREF="wininstallation-2.html">Next</A>
-Previous
-<A HREF="wininstallation.html#toc1">Contents</A>
-<HR>
-<H2><A NAME="s1">1. Introduction</A></H2>
-
-<P><B>IMPORTANT:</B>
-<P>What you'll be left with once you've followed these instructions
-is (hopefully) a working DX Spider v1.47 system that is capable
-of accepting or originating "internet" connections, plus inbound
-AX.25 and TCP/IP radio connections. If the absence of outbound
-radio connections is a serious limitation for you, it would be
-better for you to wait a couple more weeks until this support has
-been added.
-<P>On the other hand, you may have an enquiring mind, or better yet,
-may be looking for a useful way of connecting your current
-(perhaps) AK1A cluster "to the internet" via some networking
-mechanism (BPQEther, etc) or other. I won't be producing
-instructions for the latter case, because I don't have an AK1A to
-play with. But someone might ...
-<P>Whatever, this document is intended to get you started with DX
-Spider in a Microsoft Windows ™ environment. It's not
-intended to teach you anything other than how to perform a
-minimum configuration of a DX Spider installation and have it
-able to connect across "the internet" to other DX Clusters, while
-accepting inbound TELNET and radio connections.
-<P>
-<H2><A NAME="ss1.1">1.1 The requirements</A>
-</H2>
-
-<P>The very first things you're going to need are (in order of
-importance):-
-<P>
-<UL>
-<LI>A cup of good, strong tea</LI>
-<LI>A supported Windows platform with an internet connection so you can
-download the necessary software bits and bobs directly to it. There are other ways, but this is preferable.</LI>
-<LI>Another cup of good, strong tea</LI>
-<LI>If all goes according to plan, about an hour to spare</LI>
-<LI>Plenty of good, strong tea</LI>
-</UL>
-<P>
-<H2><A NAME="ss1.2">1.2 The system</A>
-</H2>
-
-<P>The platform I used to generate these instructions was a
-"vanilla" Microsoft Windows Me 4.90.3000 system, with a 700MHz
-AMD Athlon processor and 96 Mb memory. I've also personally
-verified that it runs on my laptop (Pentium 266MHz, 32 Mb memory,
-Windows 98 SE v4.10.2222 A) and a computer that I assembled from
-a random pile of junk (AMD K6-2 333MHz, 64 Mb memory, Windows 98
-v4.10.1998). As a result, I have reason to believe that what I'm
-about to describe will perform equally on any 32-bit MS Windows
-environment with 32 Mb of memory.
-<P>Because of the changes that have recently been made to the core
-"cluster.pl" module and the introduction of a very lightweight
-"winclient.pl", I have a sneaking suspicion that this will now
-run on any platform that has reasonably complete support for
-Perl. Is there someone out there with both an enquiring mind and
-(say) a Macintosh, for instance?
-<P>Please bear in mind, though, that my instructions relate solely
-to how to get this going under a Microsoft Windows environment,
-and I have zero intention of trying to make them say otherwise.
-<P>
-<H2><A NAME="ss1.3">1.3 Perl</A>
-</H2>
-
-<P>Install your chosen Perl environment. Unless you have a very good
-reason for not doing so, I strongly suggest that you use
-ActivePerl v5.6. For my testing & development, I used build 623.
-You can get this from:-
-<A HREF="http://www.activestate.com/Products/ActivePerl/Download.html">http://www.activestate.com/Products/ActivePerl/Download.html</A><P>You will need to choose either the MSI or the AS package. My
-recommendation is that you choose the MSI package and deal with
-the consequences if your system isn't equipped with support for
-the latest MS Installer; you'll be better off in the long run.
-The build 623 download is 7,460 KB, so now is a really good time
-to have some tea if you're on a slow dial-up connection.
-<P>During installation, please ensure that you do choose the options
-to "Add Perl to the PATH environment variable" and "Create Perl
-file extension association"; it will make your life so much
-easier. Once the installation is finished, be sure to reboot your
-PC. You probably won't be told anywhere else that this needs to
-be done now, but it does. Really.
-<P>Once you've rebooted, open a "DOS box" (Start > Run > command
-might do it, if you can't find it elsewhere) and from wherever it
-lands, type PERL -v <ENTER> (it's better if that's a lower-case
-'v', because an upper-case 'V' means something else. You should
-be rewarded with some interesting information about your Perl
-installation. If you're not, you must go back to the beginning
-and discover what went wrong and fix it. It's pointless to
-proceed unless this simple check is passed. Assuming it did work,
-you may now move on.
-<P>
-<H2><A NAME="ss1.4">1.4 Additional packages</A>
-</H2>
-
-<P>Some extensions ("packages") need to be added to the base Perl
-distribution, and we'll do this next. If you're using the Perl I
-recommended, and don't know any better for yourself, then just
-blindly following these instructions will work just fine. If that
-didn't describe you, then you're on your own.
-<P>Visit the following URL:
-<P>
-<A HREF="http://www.activestate.com/PPMPackages/zips/6xx-builds-only/">http://www.activestate.com/PPMPackages/zips/6xx-builds-only/</A><P>and download the following files:-
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
-Data-Dumper.zip
-Net-Telnet.zip
-TimeDate.zip
-Time-HiRes.zip
-DB_File.zip
-</PRE>
-</CODE></BLOCKQUOTE>
-<P>Make yourself a convenient directory to unpack all of these zip
-files into (I put mine in "D:\ppm>") and do the following (the
-bits you type in are blue ). Note that where these files land
-will be directly related to where you chose to install your
-ActivePerl (mine, as you can probably guess from what follows,
-went into "D:\Perl"):-
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
-D:\ppm>ppm install Data-Dumper.ppd
-Installing package 'Data-Dumper.ppd'
-Installing D:\Perl\site\lib\auto\Data\Dumper\Dumper.bs
-Installing D:\Perl\site\lib\auto\Data\Dumper\Dumper.dll
-Installing D:\Perl\site\lib\auto\Data\Dumper\Dumper.exp
-Installing D:\Perl\site\lib\auto\Data\Dumper\Dumper.lib
-Installing D:\Perl\html\site\lib\auto\Data\Dumper\Dumper.html
-Installing D:\Perl\site\lib\Data\Dumper\Dumper.pm
-Writing D:\Perl\site\lib\auto\Data\Dumper\Dumper.packlist
-D:\ppm>
-</PRE>
-</CODE></BLOCKQUOTE>
-<P>I'm not going to bother you with exhaustive details of the rest
-of them, but suffice it to say you need to:
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
-ppm install DB_File.ppd
-ppm install Net-Telnet.ppd
-ppm install TimeDate.ppd
-ppm install Time-HiRes.ppd
-</PRE>
-</CODE></BLOCKQUOTE>
-<P>If all that seemed to work OK, time to move along. Before anyone
-who is familiar with PPM tells me that we didn't need to download
-and keep those files locally, I knew that. I also knew that PPM
-is sometimes awkward to configure via firewalls, and that
-sometimes the repositories don't always work the way we'd hope. I
-do it that way because it suits me.
-<P>
-<H2><A NAME="ss1.5">1.5 Getting Spider</A>
-</H2>
-
-<P>Get the current version of the DX Spider distribution. This needs
-to be v1.47 or later. You've got two ways (currently) of getting
-this; either get a CVS update from sourceforge (if you don't know
-what this is, then it isn't for you) or get my package from:-
-<P>
-<A HREF="http://www.dcc.rsgb.org/WinSpider.zip">http://www.dcc.rsgb.org/WinSpider.zip</A><P>or if you want the lastest CVS version (which is produced every night)
-<P>
-<A HREF="http://www.dxcluster.org/download/CVSlatest.tgz">http://www.dxcluster.org/download/CVSlatest.tgz</A><P>If you went down the CVS route, then everything will be nicely
-set out on your local disk. If you got the ZIP file, unpack it to
-somewhere convenient. The following examples assume that you put
-it on drive "C:\", for convenience.
-<P><B>NOTE:</B> This distribution method will go away as soon as the first
-v1.47 tarball is released. You can use WinZip to unpack that, and
-my life will be made easier by not needing to keep this .ZIP file
-updated.
-<P>
-<HR>
-<A HREF="wininstallation-2.html">Next</A>
-Previous
-<A HREF="wininstallation.html#toc1">Contents</A>
-</BODY>
-</HTML>
+++ /dev/null
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN">
-<HTML>
-<HEAD>
- <META NAME="GENERATOR" CONTENT="SGML-Tools 1.0.9">
- <TITLE>The Installation Guide for DXSpider under Microsoft Windows: Installing the software</TITLE>
- <LINK HREF="wininstallation-1.html" REL=previous>
- <LINK HREF="wininstallation.html#toc2" REL=contents>
-<link rel=stylesheet href="style.css" type="text/css" title="default stylesheet">
-</HEAD>
-<BODY>
-Next
-<A HREF="wininstallation-1.html">Previous</A>
-<A HREF="wininstallation.html#toc2">Contents</A>
-<HR>
-<H2><A NAME="s2">2. Installing the software</A></H2>
-
-<P>Ensure that your CVS session or your unZIPped file have left you
-with a directory "C:\spider\local"; if not, go to "C:\spider\"
-and create one. If "C:\spider" is missing, go back and figure out
-why, because it shouldn't be.
-<P>Now create your own local copy of the DXVars.pm file by:-
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
-copy c:\spider\perl\DXVars.pm.issue
-c:\spider\local\DXVars.pm
-</PRE>
-</CODE></BLOCKQUOTE>
-<P>Now you'll need to edit this file using a text editor. If nothing
-else, you can simply
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
-cd \spider\local
-</PRE>
-</CODE></BLOCKQUOTE>
-<P>and then
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
-notepad DXVars.pm
-</PRE>
-</CODE></BLOCKQUOTE>
-<P>to bring up an editor window containing the file. As an absolute
-minimum you must adjust the following items in DXVars.pm:-
-<P>
-<UL>
-<LI> $mycall - Should hold the callsign of your DX Cluster</LI>
-<LI> $myname - The SysOp's first name</LI>
-<LI> $myalias - the SysOp's callsign. Cannot be the same as $mycall!</LI>
-</UL>
-<P>You really also ought to update the $mylatitude, $mylongitude,
-$myqth and $myemail variables. And unless you are absolutely
-certain you know what you're doing, you should change nothing
-else in this file.
-<P>
-<H2><A NAME="ss2.1">2.1 The AGW packet engine</A>
-</H2>
-
-<P>On the assumption that you'll be using the SV2AGW Packet Engine
-to interface your radios to the cluster, you should now create
-your own local copy of AGWConnect.pm by:-
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
-copy c:\spider\perl\AGWConnect.pm
-c:\spider\local\AGWConnect.pm
-</PRE>
-</CODE></BLOCKQUOTE>
-<P>and then
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
-notepad AGWConnect.pm
-</PRE>
-</CODE></BLOCKQUOTE>
-<P>to bring up an editor window containing the file. You must
-consider adjusting the following items in AGWConnect.pm:-
-<P>
-<UL>
-<LI>$enable - set to '1' to enable AGWPE interface </LI>
-<LI>$login - the login ID you chose when you set up the SV2AGW security :-)</LI>
-<LI>$passwd - password that matches $login</LI>
-</UL>
-<P>
-<H2><A NAME="ss2.2">2.2 Setting up the initial user files</A>
-</H2>
-
-<P>Next you need to create the initial user files, etc. A tool is
-supplied which will do this for you. To run the tool:-
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
-cd \spider\perl
-perl create_sysop.pl
-</PRE>
-</CODE></BLOCKQUOTE>
-<P>If all goes according to plan, you will see no output from this
-program, and after a brief wait, your DOS prompt will be
-returned.
-<P>Depending on how brave you are, you might now care to try the
-following:-
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
-perl cluster.pl
-</PRE>
-</CODE></BLOCKQUOTE>
-<P>If you did everything you were told, your DOS window will now
-hold a display which looks something like:-
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
-DXSpider DX Cluster Version 1.47
-Copyright (c) 1998-2001 Dirk Koopman G1TLH
-loading prefixes ...
-loading band data ...
-loading user file system ...
-starting listeners ...
-Internal port: localhost 27754
-load badwords: Ok
-reading in duplicate spot and WWV info ...
-reading existing message headers ...
-load badmsg: Ok
-load forward: Ok
-load swop: Ok
-@msg = 0 before delete
-@msg = 0 after delete
-reading cron jobs ...v cron: reading /spider/cmd/crontab
-cron: adding 1 0 * * 0
-DXUser::export("$main::data/user_asc")
-reading database descriptors ...
-doing local initialisation ...
-orft we jolly well go ...
-queue msg (0)
-</PRE>
-</CODE></BLOCKQUOTE>
-<P>Now, if that's what you've got, you are very nearly home and dry
-(in as far as these particular experiments are concerned, anyhow)
-<P>To access your new cluster (from the local machine) find yourself another
-"DOS box" and do the following:-
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
-cd \spider\perl
-perl winclient.pl
-</PRE>
-</CODE></BLOCKQUOTE>
-<P>If you are rewarded with a display which looks something like:-
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
-Hello Iain, this is GB7SJP in Amersham, Bucks running DXSpider V1.47
-Cluster: 1 nodes, 1 local / 1 total users Max users 2 Uptime 0 00:00
-M0ADI de GB7SJP 4-Mar-2001 1511Z >
-</PRE>
-</CODE></BLOCKQUOTE>
-<P>You've arrived. Try some commands, and see how they feel. (In
-case you were wondering, "Iain", "M0ADI" and "GB7SJP" all came
-from the version of DXVars.pm that was on the machine when I
-started the winclient.pl)
-<P>
-<H2><A NAME="ss2.3">2.3 Incoming telnets</A>
-</H2>
-
-<P>If you want to enable inbound "TELNET" connections, you've got a
-little more work to do. From a handy "DOS box" that's not doing
-anything else, do the following:-
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
-copy \spider\perl\listeners.pm \spider\local
-cd \spider\local
-notepad listeners.pm
-</PRE>
-</CODE></BLOCKQUOTE>
-<P>The following lines need attention:-
-<P>
-<BLOCKQUOTE><CODE>
-<PRE>
-["0.0.0.0", 7300],
-</PRE>
-</CODE></BLOCKQUOTE>
-<P>On my machine, I've simply uncommented the "0.0.0.0" entry by
-removing the '#' from the front of the line.
-<P>If you don't have a static hostname for your machine, and you
-intend to allow folk to connect to your machine across the
-internet, then I'd suggest you pay a visit to www.dyndns.org and
-create one for yourself. While it's free, it will take a modest
-an amount of effort on your part to read, understand and
-implement what needs to be done to set this up.
-<P>
-<H2><A NAME="ss2.4">2.4 Connecting to other clusters</A>
-</H2>
-
-<P>If you want to connect this to another cluster, then you'll want
-to negotiate a link with someone. For experimental purposes, I'm
-happy to allow folk to connect to GB7DXA (spud.ath.cx), on the
-understanding that the system may or may not be there and may or
-may not be connected to anything particularly useful at any given
-moment. Contact me by Email if you want me to set up a connection
-for you.
-<P><I>Last updated: 15-Apr-01</I>
-<P>
-<HR>
-Next
-<A HREF="wininstallation-1.html">Previous</A>
-<A HREF="wininstallation.html#toc2">Contents</A>
-</BODY>
-</HTML>
+++ /dev/null
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN">
-<HTML>
-<HEAD>
- <META NAME="GENERATOR" CONTENT="SGML-Tools 1.0.9">
- <TITLE>The Installation Guide for DXSpider under Microsoft Windows</TITLE>
- <LINK HREF="wininstallation-1.html" REL=next>
-
-
-<link rel=stylesheet href="style.css" type="text/css" title="default stylesheet">
-</HEAD>
-<BODY>
-<A HREF="wininstallation-1.html">Next</A>
-Previous
-Contents
-<HR>
-<H1>The Installation Guide for DXSpider under Microsoft Windows</H1>
-
-<H2>Iain Philipps, G0RDI (g0rdi@77hz.com)</H2>$Date$ $Revision$
-<P><HR>
-<EM>DX Spider under Microsoft Windows ™</EM>
-<HR>
-<P>
-<H2><A NAME="toc1">1.</A> <A HREF="wininstallation-1.html">Introduction</A></H2>
-
-<UL>
-<LI><A HREF="wininstallation-1.html#ss1.1">1.1 The requirements</A>
-<LI><A HREF="wininstallation-1.html#ss1.2">1.2 The system</A>
-<LI><A HREF="wininstallation-1.html#ss1.3">1.3 Perl</A>
-<LI><A HREF="wininstallation-1.html#ss1.4">1.4 Additional packages</A>
-<LI><A HREF="wininstallation-1.html#ss1.5">1.5 Getting Spider</A>
-</UL>
-<P>
-<H2><A NAME="toc2">2.</A> <A HREF="wininstallation-2.html">Installing the software</A></H2>
-
-<UL>
-<LI><A HREF="wininstallation-2.html#ss2.1">2.1 The AGW packet engine</A>
-<LI><A HREF="wininstallation-2.html#ss2.2">2.2 Setting up the initial user files</A>
-<LI><A HREF="wininstallation-2.html#ss2.3">2.3 Incoming telnets</A>
-<LI><A HREF="wininstallation-2.html#ss2.4">2.4 Connecting to other clusters</A>
-</UL>
-<HR>
-<A HREF="wininstallation-1.html">Next</A>
-Previous
-Contents
-</BODY>
-</HTML>
+++ /dev/null
-<!doctype linuxdoc system>
-
-<article>
-
-<!-- Title information -->
-
-<title>The Installation Guide for DXSpider under Microsoft Windows</title>
-<author>Iain Philipps, G0RDI (g0rdi@77hz.com)</author>
-<date>$Date$ $Revision$</date>
-<abstract>
-DX Spider under Microsoft Windows ™
-</abstract>
-
-<!-- Table of contents -->
-<toc>
-
-<!-- Begin the document -->
-
-<sect>Introduction
-
-<P>
-<bf>IMPORTANT:</bf>
-
-What you'll be left with once you've followed these instructions
-is (hopefully) a working DX Spider v1.47 system that is capable
-of accepting or originating "internet" connections, plus inbound
-AX.25 and TCP/IP radio connections. If the absence of outbound
-radio connections is a serious limitation for you, it would be
-better for you to wait a couple more weeks until this support has
-been added.
-
-On the other hand, you may have an enquiring mind, or better yet,
-may be looking for a useful way of connecting your current
-(perhaps) AK1A cluster "to the internet" via some networking
-mechanism (BPQEther, etc) or other. I won't be producing
-instructions for the latter case, because I don't have an AK1A to
-play with. But someone might ...
-
-Whatever, this document is intended to get you started with DX
-Spider in a Microsoft Windows ™ environment. It's not
-intended to teach you anything other than how to perform a
-minimum configuration of a DX Spider installation and have it
-able to connect across "the internet" to other DX Clusters, while
-accepting inbound TELNET and radio connections.
-
-<sect1>The requirements
-
-<P>
-The very first things you're going to need are (in order of
-importance):-
-
-<itemize>
-<item>A cup of good, strong tea
-<item>A supported Windows platform with an internet connection so you can
-download the necessary software bits and bobs directly to it. There are other ways, but this is preferable.
-<item>Another cup of good, strong tea
-<item>If all goes according to plan, about an hour to spare
-<item>Plenty of good, strong tea
-</itemize>
-
-<sect1>The system
-
-<P>
-The platform I used to generate these instructions was a
-"vanilla" Microsoft Windows Me 4.90.3000 system, with a 700MHz
-AMD Athlon processor and 96 Mb memory. I've also personally
-verified that it runs on my laptop (Pentium 266MHz, 32 Mb memory,
-Windows 98 SE v4.10.2222 A) and a computer that I assembled from
-a random pile of junk (AMD K6-2 333MHz, 64 Mb memory, Windows 98
-v4.10.1998). As a result, I have reason to believe that what I'm
-about to describe will perform equally on any 32-bit MS Windows
-environment with 32 Mb of memory.
-
-Because of the changes that have recently been made to the core
-"cluster.pl" module and the introduction of a very lightweight
-"winclient.pl", I have a sneaking suspicion that this will now
-run on any platform that has reasonably complete support for
-Perl. Is there someone out there with both an enquiring mind and
-(say) a Macintosh, for instance?
-
-Please bear in mind, though, that my instructions relate solely
-to how to get this going under a Microsoft Windows environment,
-and I have zero intention of trying to make them say otherwise.
-
-<sect1>Perl
-
-<P>
-Install your chosen Perl environment. Unless you have a very good
-reason for not doing so, I strongly suggest that you use
-ActivePerl v5.6. For my testing & development, I used build 623.
-You can get this from:- <htmlurl
-url="http://www.activestate.com/Products/ActivePerl/Download.html"
-name="http://www.activestate.com/Products/ActivePerl/Download.html">
-
-You will need to choose either the MSI or the AS package. My
-recommendation is that you choose the MSI package and deal with
-the consequences if your system isn't equipped with support for
-the latest MS Installer; you'll be better off in the long run.
-The build 623 download is 7,460 KB, so now is a really good time
-to have some tea if you're on a slow dial-up connection.
-
-During installation, please ensure that you do choose the options
-to "Add Perl to the PATH environment variable" and "Create Perl
-file extension association"; it will make your life so much
-easier. Once the installation is finished, be sure to reboot your
-PC. You probably won't be told anywhere else that this needs to
-be done now, but it does. Really.
-
-Once you've rebooted, open a "DOS box" (Start > Run > command
-might do it, if you can't find it elsewhere) and from wherever it
-lands, type PERL -v <ENTER> (it's better if that's a lower-case
-'v', because an upper-case 'V' means something else. You should
-be rewarded with some interesting information about your Perl
-installation. If you're not, you must go back to the beginning
-and discover what went wrong and fix it. It's pointless to
-proceed unless this simple check is passed. Assuming it did work,
-you may now move on.
-
-<sect1>Additional packages
-
-<P>
-Some extensions ("packages") need to be added to the base Perl
-distribution, and we'll do this next. If you're using the Perl I
-recommended, and don't know any better for yourself, then just
-blindly following these instructions will work just fine. If that
-didn't describe you, then you're on your own.
-
-Visit the following URL:
-
-<htmlurl url="http://www.activestate.com/PPMPackages/zips/6xx-builds-only/"
-name="http://www.activestate.com/PPMPackages/zips/6xx-builds-only/">
-
-and download the following files:-
-
-<tscreen><verb>
-Data-Dumper.zip
-Net-Telnet.zip
-TimeDate.zip
-Time-HiRes.zip
-DB_File.zip
-</verb></tscreen>
-
-Make yourself a convenient directory to unpack all of these zip
-files into (I put mine in "D:\ppm>") and do the following (the
-bits you type in are blue ). Note that where these files land
-will be directly related to where you chose to install your
-ActivePerl (mine, as you can probably guess from what follows,
-went into "D:\Perl"):-
-
-<tscreen><verb>
-D:\ppm>ppm install Data-Dumper.ppd
-Installing package 'Data-Dumper.ppd'
-Installing D:\Perl\site\lib\auto\Data\Dumper\Dumper.bs
-Installing D:\Perl\site\lib\auto\Data\Dumper\Dumper.dll
-Installing D:\Perl\site\lib\auto\Data\Dumper\Dumper.exp
-Installing D:\Perl\site\lib\auto\Data\Dumper\Dumper.lib
-Installing D:\Perl\html\site\lib\auto\Data\Dumper\Dumper.html
-Installing D:\Perl\site\lib\Data\Dumper\Dumper.pm
-Writing D:\Perl\site\lib\auto\Data\Dumper\Dumper.packlist
-D:\ppm>
-</verb></tscreen>
-
-I'm not going to bother you with exhaustive details of the rest
-of them, but suffice it to say you need to:
-
-<tscreen><verb>
-ppm install DB_File.ppd
-ppm install Net-Telnet.ppd
-ppm install TimeDate.ppd
-ppm install Time-HiRes.ppd
-</verb></tscreen>
-
-If all that seemed to work OK, time to move along. Before anyone
-who is familiar with PPM tells me that we didn't need to download
-and keep those files locally, I knew that. I also knew that PPM
-is sometimes awkward to configure via firewalls, and that
-sometimes the repositories don't always work the way we'd hope. I
-do it that way because it suits me.
-
-<sect1>Getting Spider
-
-<P>
-Get the current version of the DX Spider distribution. This needs
-to be v1.47 or later. You've got two ways (currently) of getting
-this; either get a CVS update from sourceforge (if you don't know
-what this is, then it isn't for you) or get my package from:-
-
-<htmlurl url="http://www.dcc.rsgb.org/WinSpider.zip" name="http://www.dcc.rsgb.org/WinSpider.zip">
-
-or if you want the lastest CVS version (which is produced every night)
-
-<htmlurl url="http://www.dxcluster.org/download/CVSlatest.tgz" name="http://www.dxcluster.org/download/CVSlatest.tgz">
-
-If you went down the CVS route, then everything will be nicely
-set out on your local disk. If you got the ZIP file, unpack it to
-somewhere convenient. The following examples assume that you put
-it on drive "C:\", for convenience.
-
-<bf>NOTE:</bf> This distribution method will go away as soon as the first
-v1.47 tarball is released. You can use WinZip to unpack that, and
-my life will be made easier by not needing to keep this .ZIP file
-updated.
-
-<sect>Installing the software
-
-<P>
-Ensure that your CVS session or your unZIPped file have left you
-with a directory "C:\spider\local"; if not, go to "C:\spider\"
-and create one. If "C:\spider" is missing, go back and figure out
-why, because it shouldn't be.
-
-Now create your own local copy of the DXVars.pm file by:-
-
-<tscreen><verb>
-copy c:\spider\perl\DXVars.pm.issue
-c:\spider\local\DXVars.pm
-</verb></tscreen>
-
-Now you'll need to edit this file using a text editor. If nothing
-else, you can simply
-
-<tscreen><verb>
-cd \spider\local
-</verb></tscreen>
-
-and then
-
-<tscreen><verb>
-notepad DXVars.pm
-</verb></tscreen>
-
-to bring up an editor window containing the file. As an absolute
-minimum you must adjust the following items in DXVars.pm:-
-
-<itemize>
-<item> $mycall - Should hold the callsign of your DX Cluster
-<item> $myname - The SysOp's first name
-<item> $myalias - the SysOp's callsign. Cannot be the same as $mycall!
-</itemize>
-
-You really also ought to update the $mylatitude, $mylongitude,
-$myqth and $myemail variables. And unless you are absolutely
-certain you know what you're doing, you should change nothing
-else in this file.
-
-<sect1>The AGW packet engine
-
-<P>
-On the assumption that you'll be using the SV2AGW Packet Engine
-to interface your radios to the cluster, you should now create
-your own local copy of AGWConnect.pm by:-
-
-<tscreen><verb>
-copy c:\spider\perl\AGWConnect.pm
-c:\spider\local\AGWConnect.pm
-</verb></tscreen>
-
-and then
-
-<tscreen><verb>
-notepad AGWConnect.pm
-</verb></tscreen>
-
-to bring up an editor window containing the file. You must
-consider adjusting the following items in AGWConnect.pm:-
-
-<itemize>
-<item>$enable - set to '1' to enable AGWPE interface
-<item>$login - the login ID you chose when you set up the SV2AGW security :-)
-<item>$passwd - password that matches $login
-</itemize>
-
-<sect1>Setting up the initial user files
-
-<P>
-Next you need to create the initial user files, etc. A tool is
-supplied which will do this for you. To run the tool:-
-
-<tscreen><verb>
-cd \spider\perl
-perl create_sysop.pl
-</verb></tscreen>
-
-If all goes according to plan, you will see no output from this
-program, and after a brief wait, your DOS prompt will be
-returned.
-
-Depending on how brave you are, you might now care to try the
-following:-
-
-<tscreen><verb>
-perl cluster.pl
-</verb></tscreen>
-
-If you did everything you were told, your DOS window will now
-hold a display which looks something like:-
-
-<tscreen><verb>
-DXSpider DX Cluster Version 1.47
-Copyright (c) 1998-2001 Dirk Koopman G1TLH
-loading prefixes ...
-loading band data ...
-loading user file system ...
-starting listeners ...
-Internal port: localhost 27754
-load badwords: Ok
-reading in duplicate spot and WWV info ...
-reading existing message headers ...
-load badmsg: Ok
-load forward: Ok
-load swop: Ok
-@msg = 0 before delete
-@msg = 0 after delete
-reading cron jobs ...v cron: reading /spider/cmd/crontab
-cron: adding 1 0 * * 0
-DXUser::export("$main::data/user_asc")
-reading database descriptors ...
-doing local initialisation ...
-orft we jolly well go ...
-queue msg (0)
-</verb></tscreen>
-
-Now, if that's what you've got, you are very nearly home and dry
-(in as far as these particular experiments are concerned, anyhow)
-
-To access your new cluster (from the local machine) find yourself another
-"DOS box" and do the following:-
-
-<tscreen><verb>
-cd \spider\perl
-perl winclient.pl
-</verb></tscreen>
-
-If you are rewarded with a display which looks something like:-
-
-<tscreen><verb>
-Hello Iain, this is GB7SJP in Amersham, Bucks running DXSpider V1.47
-Cluster: 1 nodes, 1 local / 1 total users Max users 2 Uptime 0 00:00
-M0ADI de GB7SJP 4-Mar-2001 1511Z >
-</verb></tscreen>
-
-You've arrived. Try some commands, and see how they feel. (In
-case you were wondering, "Iain", "M0ADI" and "GB7SJP" all came
-from the version of DXVars.pm that was on the machine when I
-started the winclient.pl)
-
-<sect1>Incoming telnets
-
-<P>
-If you want to enable inbound "TELNET" connections, you've got a
-little more work to do. From a handy "DOS box" that's not doing
-anything else, do the following:-
-
-<tscreen><verb>
-copy \spider\perl\listeners.pm \spider\local
-cd \spider\local
-notepad listeners.pm
-</verb></tscreen>
-
-The following lines need attention:-
-
-<tscreen><verb>
-["0.0.0.0", 7300],
-</verb></tscreen>
-
-On my machine, I've simply uncommented the "0.0.0.0" entry by
-removing the '#' from the front of the line.
-
-If you don't have a static hostname for your machine, and you
-intend to allow folk to connect to your machine across the
-internet, then I'd suggest you pay a visit to www.dyndns.org and
-create one for yourself. While it's free, it will take a modest
-an amount of effort on your part to read, understand and
-implement what needs to be done to set this up.
-
-<sect1>Connecting to other clusters
-
-<P>
-If you want to connect this to another cluster, then you'll want
-to negotiate a link with someone. For experimental purposes, I'm
-happy to allow folk to connect to GB7DXA (spud.ath.cx), on the
-understanding that the system may or may not be there and may or
-may not be connected to anything particularly useful at any given
-moment. Contact me by Email if you want me to set up a connection
-for you.
-
-<it>Last updated: 15-Apr-01</it>
-
-</article>
projects / spider.git / commitdiff