<!-- Title information -->
-<title>The DXSpider Installation and Administration Manual
-<author>Ian Maude, G0VGS, (ianmaude@btinternet.com)
-<date>Version 1.31 January 2001
+<title>The DXSpider Installation and Administration Manual</title>
+<author>Ian Maude, G0VGS, (ianmaude@btinternet.com)</author>
+<date>Version 1.47 (Revision 1.30), April 2001</date>
+
<abstract>
A reference for SysOps of the DXSpider DXCluster program.
</abstract>
<!-- Begin the document -->
-<sect>Installation (Original version by Iain Phillips, G0RDI)
+<sect>Installation (Original version by Iain Philipps, G0RDI)
<sect1>Introduction
<P>
-This section describes the installation of DX Spider v1.35 on a
-<htmlurl url="http://www.redhat.com" name="RedHat"> Linux Distribution.
+This section describes the installation of DX Spider v1.46 on a
+<htmlurl url="http://www.redhat.com" name="RedHat"> Linux Distribution.
+Wherever possible I will try to include differences for other distributions.
I do not intend to try and cover the installation of Linux or the setup
of the AX25 utilities. If you need help on this then read Iains original
-HOWTO on the <htmlurl url="http://www.dxcluster.org" name="DXSpider">
-website.
+installation guide that comes with the Spider distribution.
<P>
I am assuming a general knowledge of Linux and its commands. You should
<P>
The crucial ingredient for all of this is
-<htmlurl url="http://www.perl.org" name="Perl 5.004">. Now I know Perl 5.005
-is out and this will almost certainly work with it, but
-<htmlurl url="http://www.redhat.com" name="RedHat 5.1"> comes with 5.004.
-<em>Be Warned</em>, earlier versions of
-<htmlurl url="http://www.redhat.com" name="RedHat"> <bf>do not</bf> come
-with 5.004 as standard, you need to
-<htmlurl url="ftp://upgrade.redhat.com" name="upgrade">
+<htmlurl url="http://www.perl.org" name="Perl">. Earlier versions of
+Spider required perl 5.004, however it is now <it>STRONGLY</it> recommended
+that you use at least version 5.005_03 as this is the version being used
+in the development of Spider.
<P>In addition to the standard Red Hat distribution you will require the
-following <htmlurl url="http://www.cpan.org/CPAN.html" name="CPAN"> modules: -
+following modules from <htmlurl url="http://www.cpan.org/CPAN.html" name="http://www.cpan.org/CPAN.html"> ...
<P>
<itemize>
-<item> MD5-1.7.tar.gz
-<item> Data-Dumper-2.10.tar.gz
-<item> FreezeThaw-0.3.tar.gz
-<item> MLDBM-2.00.tar.gz
-<item> TimeDate-1.08.tar.gz
-<item> IO-1.20.tar.gz
+<item> Data-Dumper-2.101.tar.gz
+<item> TimeDate-1.10.tar.gz
+<item> IO-1.20.tar.gz (for perl 5.00403 and lower)
<item> Net-Telnet-3.02.tar.gz
<item> Curses-1.05.tar.gz
<item> Time-HiRes-01.20.tar.gz
<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.35 for this section but of course you would use the latest version.
+1.46 for this section but of course you would use the latest version.
<P>
Login as root and create a user to run the cluster under. <bf><it>UNDER
<tscreen><verb>
# cd ~sysop
-# tar xvfz spider-1.35.tar.gz
+# tar xvfz spider-1.46.tar.gz
# ln -s ~sysop/spider /spider
# groupadd -g 251 spider (or another number)
</verb></tscreen>
<P><bf>PLEASE USE CAPITAL LETTERS FOR CALLSIGNS</bf>
<P>
-DON'T alter the DXVars.pm (or any other 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!
+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>
Save the new file and change directory to ../perl ....
the sysop.
<tscreen><verb>
-$ create_sysop.pl
+$ ./create_sysop.pl
</verb></tscreen>
<sect1>Starting up for the first time
It should look something like this ...
<tscreen><verb>
-$ cluster.pl
-DXSpider DX Cluster Version 1.35
+$ ./cluster.pl
+DXSpider DX Cluster Version 1.46
Copyright (c) 1998 Dirk Koopman G1TLH
loading prefixes ...
loading band data ...
<P>
If all is well then login on another term or console as <em>sysop</em> and
-cd to /spider/perl. Now issue the following command ...
+cd to /spider/src. Now issue the following command ...
<tscreen><verb>
-$ client.pl
+$ ./client
</verb></tscreen>
<P>
<P>
and both the cluster and the client should return to Linux prompts.
-<sect>The Client program
+<sect1>The Client program
<P>
In earlier versions of Spider, all the processes were Perl scripts. This
should see the output on your screen and hopefully now have a small C program
called <em>client</em>. Leave it in this directory.
+
+<sect>Quick installation guide (Linux version)
+
+<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.
+
+<itemize>
+<item>Login as root
+<item>Get the additional CPAN modules and install them (root)
+<item>Create the "sysop" user and set a password (root)
+<item>Put the Spider tarball in ~sysop and untar it (root)
+<item>ln -s ~sysop/spider /spider (root)
+<item>groupadd -g 251 spider (root)
+<item>Add any more users you need to the group entry in /etc/group (root)
+<item>Set the permissions on the spider tree (root)
+<item>Fix permissions on ax25_call and netrom_call (root)
+<item>Login as the sysop user
+<item>cd to /spider (sysop)
+<item>mkdir local (sysop)
+<item>mkdir local_cmd (sysop)
+<item>cp perl/DXVars.pm.issue local/DXVars.pm (sysop)
+<item>cd to /spider/local and edit DXVars to set your details (sysop)
+<item>cd ../perl (sysop)
+<item>./create_sysop.pl (sysop)
+<item>./cluster.pl (sysop)
+</itemize>
+
+Spider should now be running and you should be able to login using the
+client program.
+
+<itemize>
+<item>Login as root
+<item>Enter the correct line in ax25d.conf (root)
+<item>Enter the correct line in /etc/services (root)
+<item>Enter the correct line in /etc/inetd.conf (root)
+<item>killall -HUP inetd (root)
+</itemize>
+
+Spider should now be able to accept logins via telnet, netrom and ax25.
+
+<itemize>
+<item>Login as sysop
+<item>Start the cluster (sysop)
+<item>set/node and type for links (sysop)
+<item>Write any connect scripts (sysop)
+<item>Edit /spider/crontab as required (sysop)
+<item>Edit any other files as necessary (sysop)
+<item>Set filters, hops and forwarding files (sysop)
+<item>Login as root
+<item>Enter the correct line in /etc/inittab (root)
+</itemize>
+
<sect>Configuration
<sect1>Allowing ax25 connects from users
default * * * * * * - sysop /spider/src/client client %u ax25
</verb></tscreen>
-<sect1>Allowing telnet connects from users
+or, if you wish your users to be able to use SSID's on their callsigns ..
+
+<tscreen><verb>
+default * * * * * * - sysop /spider/src/client client %s ax25
+</verb></tscreen>
+
+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:
+
+<tscreen><verb>
+GB7DJK-2 * * * * * * - sysop /spider/src/client client gb7djk-2 ax25
+default * * * * * * - sysop /spider/src/client client %u ax25
+</verb></tscreen>
+
+<sect1>Allowing telnet connects from users
+<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>
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 ....
</verb></tscreen>
<P>
-This needs to be added above the standard services such as ftp, telnet etc.
Once this is done, you need to restart inetd like this ....
<tscreen><verb>
</verb></tscreen>
-<P>Now login as <em>sysop</em> and cd spider/perl. You can test that spider
+<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 ....
<tscreen><verb>
-client.pl login telnet
+./client login telnet
</verb></tscreen>
You should get a login prompt and on issuing a callsign, you will be given
<P>
You should now get the login prompt and be able to login as before.
+<sect1>Setting up telnet connects (from 1.47 onwards)
+
+<P>
+From version 1.47 you can choose to allow the perl cluster.pl program to
+allow connections directly (i.e. not via the <tt>/spider/src/client</tt>
+interface program). If you are using Windows then this is the only method
+available of allowing incoming telnet connections.
+
+<P>
+To do this you need first to remove any line that you may previously have set
+up in /etc/inetd.conf. Remember to:-
+
+<tscreen><verb>
+killall -HUP inetd
+</verb></tscreen>
+
+<P>
+to make the change happen...
+
+<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 &dquot;0.0.0.0&dquot;
+and select the correct port to listen on. So that it looks like this:-
+
+<tscreen><verb>
+@listen = (
+ ["0.0.0.0", 8000],
+);
+</verb></tscreen>
+
+<P>
+As standard, the listener will listen on all interfaces simultaneously.
+If you require more control than this, you can specify each interface
+individually:-
+
+<tscreen><verb>
+@listen = (
+ ["gb7baa.dxcluster.net", 8000],
+ ["44.131.16.2", 6300],
+);
+</verb></tscreen>
+
+<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>
+Restart the cluster.pl program to enable the listener.
+
+<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.
+
+<sect1>Setting up for AGW Engine (1.47 onwards)
+
+<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>
+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:-
+
+<itemize>
+<item> set <tt>$enable</tt> to 1.
+<item> set <tt>$login</tt> and <tt>$passwd</tt> to the values set up in your AGW installation.
+If you haven't set any there, then you should not touch these values.
+<item> You can connect to a remote AGW engine (ie on some other machine) by changing <tt>$addr</tt>
+and <tt>$port</tt> appropriately.
+<item> Restart the cluster.pl program
+</itemize>
+
+
<sect1>Setting up node connects
<P>
AK1A type node.
<P>
-Start up the cluster as you did before and login as the sysop with client.pl.
+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>
That is now set, it is as simple as that. To prove it, login on yet another
-console as sysop and issue the command ...
+console as sysop, cd to spider/src and issue the command ...
<tscreen><verb>
-client.pl gb7baa (using the callsign you set as a node)
+./client gb7baa (using the callsign you set as a node)
</verb></tscreen>
<P>
You should get an initialisation string from DXSpider like this ...
<tscreen><verb>
-client.pl gb7baa
+./client gb7baa
PC38^GB7MBC^~
</verb></tscreen>
this is all that needs to be done. If the connection is to be outgoing then
a connection script needs to be written.
+<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:
+
+<tscreen><verb>
+unset/node gb7baa
+</verb></tscreen>
+
<sect1>Connection scripts
<P>
The connect scripts consist of lines which start with the following keywords
or symbols:-
-<verb>
+<descrip>
-# All lines starting with a # are ignored, as are completely
+<tag/#/All lines starting with a <tt>#</tt> are ignored, as are completely
blank lines.
-timeout timeout followed by a number is the number of seconds to wait for a
+<tag/timeout/<tt>timeout</tt> 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.
-abort abort is a regular expression containing one or more strings to look
+<tag/abort/ <tt>abort</tt> 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.
-connect connect followed by ax25 or telnet and some type dependent
+<tag/connect/<tt>connect</tt> 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
responsibility to get your node and other ax25 parameters to work
before going down this route!
-' ' is the delimiting character for a word or phrase of an expect/send
+<tag/'/<tt>'</tt> 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
then the right hand string is sent to the connection.
This process is repeated for every line of chat script.
-client client starts the connection, put the arguments you would want here
+<tag/client/<tt>client</tt> 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]).
-</verb>
+</descrip>
-There are many possible ways to configure the script but here are two examples,
-one for a NETRom/AX25 connect and one for tcp/ip.
+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.
<tscreen><verb>
timeout 60
<P>
+<tscreen><verb>
+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
+</verb></tscreen>
+
+<P>
+
<tscreen><verb>
timeout 15
connect telnet dirkl.tobit.co.uk
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>. You should see something like this ...
+<em>cluster.pl</em>. From version 1.47 onwards, you will need to <tt>set/debug connect</tt> first.
+You should see something like this ...
<tscreen><verb>
<- D G1TLH connect gb7djk-1
<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 8000, this negotiation does
+If the connection is to a different port, such as 7300, this negotiation does
not happen and therefore no echo should be present.
<P>
DX:3:respawn:/bin/su -c "/usr/bin/perl -w /spider/perl/cluster.pl" sysop >/dev/tty7
</verb></tscreen>
+<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 ...
+
+<tscreen><verb>
+DX:235:respawn:/bin/su -c "/usr/bin/perl -w /spider/perl/cluster.pl" sysop >/dev/tty7
+</verb></tscreen>
+
+
+The line required for Slackware distributions is slightly different. My thanks to
+Aurelio, PA3EZL for this information.
+
+<tscreen><verb>
+DX:23:respawn:/bin/su - sysop -c "/usr/bin/perl -w /spider/perl/cluster.pl" >/dev/tty7
+</verb></tscreen>
+
<P>
This will automatically start DXSpider on tty7 (ALT-F7) on bootup and restart
it should it crash for any reason.
# 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 !connected('gb7xxx')
+0,10,20,30,40,50 * * * * start_connect('gb7xxx') if unless connected('gb7xxx')
</verb></tscreen>
<P>
Make sure you only send mail to the clusters that want it by using the
Forward.pl file very carefully.
+<sect>Databases
+
+<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.
+
+<sect1>Creating databases
+
+<P>
+Creating a database could not be more simple. All the commands are
+sent from the cluster prompt as the <em>sysop</em> user.
+
+To create a database you use the command <em>dbcreate</em>. It can
+be used in 3 different ways like so ..
+
+<tscreen><verb>
+dbcreate <name>
+</verb></tscreen>
+
+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.
+
+<tscreen><verb>
+dbcreate <name> chain <name> [<name>...]
+</verb></tscreen>
+
+This creates a chained database entry. The first database will be
+scanned, then the second, the third etc...
+
+<tscreen><verb>
+dbcreate <name> remote <name>
+</verb></tscreen>
+
+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...
+
+<tscreen><verb>
+dbcreate buckmaster remote gb7dxc
+</verb></tscreen>
+
+Remote databases cannot be chained, however, the last database in a
+chain can be a remote database.
+
+<sect1>Importing databases
+
+<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.
+
+To import such a database, first put the file somewhere useful like /tmp
+and then issue the following command ...
+
+<tscreen><verb>
+dbimport oblast /tmp/OBLAST.FUL
+</verb></tscreen>
+
+This will update the existing local oblast database or create it if
+it does not exist.
+
+<sect1>Checking available databases
+
+<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 ...
+
+<tscreen><verb>
+dbavail
+DB Name Location Chain
+qsl Local
+buck GB7ADX
+hftest GB7DXM
+G0VGS de GB7MBC 3-Feb-2001 1925Z >
+</verb></tscreen>
+
+<sect1>Looking up databases
+
+<P>
+To look for information in a defined database, simply use the <em>dbshow</em>
+command, for example ...
+
+<tscreen><verb>
+dbshow buckmaster G0YLM
+</verb></tscreen>
+
+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 ...
+
+<tscreen><verb>
+'^sh\w*/buc', 'dbshow buckmaster', 'dbshow',
+</verb></tscreen>
+
+Now you can simply use show/buckmaster or an abreviation.
+
+<sect1>Removing databases
+
+<P>
+To delete an existing database you use the <em>dbremove</em> command.
+For example ...
+
+<tscreen><verb>
+dbremove oblast
+</verb></tscreen>
+
+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.
+
<sect>Information, files and useful programs
<sect1>MOTD
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>bulletins</em>. Now copy any OPDX or similar bulletins into it. These
+<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 bulletins directory you have just created,
+command with an extension for the bulletin directory you have just created,
like this ....
<tscreen><verb>
-show/files bulletins
+show/files bulletin
</verb></tscreen>
<P>
<tscreen><verb>
sh/files
-bulletins DIR 20-Dec-1999 1715Z news 1602 14-Dec-1999 1330Z
+bulletin DIR 20-Dec-1999 1715Z news 1602 14-Dec-1999 1330Z
</verb></tscreen>
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>bulletins</em>. You can
+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
type news
</verb></tscreen>
-To look what is in the bulletins directory you issue the command ....
+To look what is in the bulletin directory you issue the command ....
<tscreen><verb>
-show/files bulletins
+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
You can now read any file in this directory using the type command, like this ....
<tscreen><verb>
-type bulletins/opdx391
+type bulletin/opdx391
Ohio/Penn DX Bulletin No. 391
The Ohio/Penn Dx PacketCluster
DX Bulletin No. 391
<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.pl.
+announces etc. To use this program, simply use console.pl instead of client.
<P>
To edit the colours, copy /spider/perl/Console.pl to /spider/local and edit the
That is it! the kepler data has been updated.
+<sect1>The QRZ callbook
+
+<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
+<htmlurl url="http://www.qrz.com" name="qrz.com"> for allowing this access.
<sect>CVS
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.
-Either way you will want to change directory to a new place, if you want to
-update an existing installation then I suggest /tmp, otherwise choose a
-suitable place according to the normal installation instructions.
+
+If you are installing Spider from CVS then change directory to /home/sysop
+
+If you are wanting to update Spider then cd to /tmp
<P>
The next step will create a brand new 'spider' directory in your current
Remember to recompile the C client (cd /spider/src; make)
<P>
-At this point the files have been upgraded. You can (usually) restrt the cluster
+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!
</tt>
<P>
-You can remove this level with unset/debug <name>
+You can choose to log several different levels. The levels are
+
+chan
+state
+msg
+cron
+connect
+
+You can show what levels you are logging with the <em>show/debug</em>
+command.
+
+You can remove a debug level with unset/debug <name>
<sect1>set/dx (0)
<P>
<tt>
-<bf>show/badspotter</bf>Show all the bad spotters in the system
+<bf>show/badspotter</bf> Show all the bad spotters in the system
</tt>
<P>
Display all the bad spotter's callsigns in the system, see SET/BADSPOTTER
for more information.
+<sect1>show/configuration (0)
+
+<P>
+<tt>
+<bf>show/configuration [<node>]</bf> Show all visible nodes and their users
+</tt>
+
+<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.
+
+This command is normally abbreviated to: sh/c
+
+BE WARNED: the list that is returned can be VERY long
+
+<sect1>show/configuration/node (0)
+
+<P>
+<tt>
+<bf>show/configuration/node</bf> Show all the nodes connected
+</tt>
+
+<P>
+Show all the nodes connected locally and the nodes they have connected.
+
+<sect1>show/connect (1)
+
+<P>
+<tt>
+<bf>show/connect</bf> Show all the active connections
+</tt>
+
+<P>
+This command shows information on all the active connections known to
+the node. This command gives slightly more information than WHO.
+
<sect1>show/date (0)
<P>
then it will show UTC and UTC + the local offset (not including DST) at
the prefixes or callsigns that you specify.
+<sect1>show/debug (9)
+
+<P>
+<tt>
+<bf>show/debug</bf> Show what levels of debug you are logging
+</tt>
+
+<P>
+The levels can be set with <em>set/debug</em>
+
<sect1>show/dx (0)
<P>
Show a list of callsigns that have been excluded (locked out) of the
cluster locally with the <em>set/lockout</em> command
+<sect1>show/log (8)
+
+<P>
+<tt>
+<bf>show/log [<callsign>]</bf> Show excerpts from the system log
+</tt>
+
+<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.
+
<sect1>show/moon (0)
<P>
projects / spider.git / blobdiff