X-Git-Url: http://dxcluster.org/gitweb/gitweb.cgi?a=blobdiff_plain;f=sgml%2Fadminmanual.sgml;h=8af052bada49b951ff2a516d6465fc7211556456;hb=204a594bd86adeba2cbb1ddefd3ddd6c288b702a;hp=6dbf74220e21b2c9002c3c8ed7815af56ff5cd41;hpb=741dc93536de6dd7d612807081f7e7dcafe44be1;p=spider.git diff --git a/sgml/adminmanual.sgml b/sgml/adminmanual.sgml index 6dbf7422..8af052ba 100644 --- a/sgml/adminmanual.sgml +++ b/sgml/adminmanual.sgml @@ -6,7 +6,7 @@
-Last modified: 13 January 2001 by Ian Maude, G0VGS
-
@@ -604,6 +601,15 @@ the following lines to the file near the end ...
DX:3:respawn:/bin/su -c "/usr/bin/perl -w /spider/perl/cluster.pl" sysop >/dev/tty7
+
+This line works fine for RedHat and SuSE distributions. The line required for
+Slackware distributions is slightly different. My thanks to Aurelio, PA3EZL for
+this information.
+
+
This will automatically start DXSpider on tty7 (ALT-F7) on bootup and restart
it should it crash for any reason.
@@ -1312,6 +1318,316 @@ are just examples :-)
You can reload the file from the cluster prompt as sysop with load/badwords.
+
+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.
+
+The cluster mail is automatically deleted after 30 days unless the sysop
+sets the "keep" flag using the msg command.
+
+
+Personal mail is sent using the sp command. This is actually the
+default method of sending mail and so a simple s for send will do.
+A full list of the send commands and options is in the command set
+section, so I will not duplicate them here.
+
+
+Bulletin mail is sent by using the sb command. This is one of the
+most common mistakes users make when sending mail. They send a bulletin
+mail with s or sp instead of sb and of course
+the message never leaves the cluster. This can be rectified by the sysop
+by using the msg command.
+
+ Bulletin addresses can be set using the Forward.pl file.
+
+
+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 ...
+
+
+To force the cluster to reread the file use load/forward
+
+
+
+The msg 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.
+
+Here is a full list of the various options ...
+
+
+You can check on a message from within the cluster by using the command
+stat/msg. 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 ...
+
+
+This is described in the section on Other filters so I will not
+duplicate it here.
+
+
+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 distro. You
+put any distibution lists in here. For example, here is a file called
+SYSOP.pl that caters for the UK sysops.
+
+
+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.
+
+
+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.
+
+
+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.
+
+
+Creating a database could not be more simple. All the commands are
+sent from the cluster prompt as the sysop user.
+
+To create a database you use the command dbcreate. It can
+be used in 3 different ways like so ..
+
+
+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 ...
+
+
+Once a database is created, you will want to check that it has been
+added. To do this use the dbavail command. This will
+output the available databases. For example ...
+
+
+To look for information in a defined database, simply use the dbshow
+command, for example ...
+
+
+To delete an existing database you use the dbremove command.
+For example ...
+
+
-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 ...
+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.
-
+To edit the colours, copy /spider/perl/Console.pl to /spider/local and edit the
+file with your favourite editor.
-package DXMsg;
+
+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 export command from the cluster prompt
+as the sysop. For example ...
+
+
-To force the cluster to reread the file use load/forward
+Now login to a VT as sysop and cd /spider/perl. There is a command in
+the perl directory called convkeps.pl. All we need to do now is
+convert the file like so ...
-
-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 distro. You
-put any distibution lists in here. For example, here is a file called
-SYSOP.pl that caters for the UK sysops.
+Now go back to the cluster and issue the command ...
-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.
+
-To edit the colours, copy /spider/perl/Console.pl to /spider/local and edit the
-file with your favourite editor.
+The command sh/qrz 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
+
The next step will create a brand new 'spider' directory in your current
@@ -1763,7 +2038,7 @@ correct. YOU WERE LOGGED IN AS THE USER SYSOP WEREN'T YOU?????
Remember to recompile the C client (cd /spider/src; make)
-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!
@@ -3259,7 +3534,18 @@ Set the node_call as a CLX type node
-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 show/debug
+command.
+
+You can remove a debug level with unset/debug <name>
-
@@ -3731,6 +4017,16 @@ 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.
+
+
+
+The levels can be set with set/debug
+
@@ -3893,6 +4189,18 @@ Show which nodes are currently set to be isolated.
Show a list of callsigns that have been excluded (locked out) of the
cluster locally with the set/lockout command
+
+
+
+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.
+