X-Git-Url: http://dxcluster.org/gitweb/gitweb.cgi?a=blobdiff_plain;ds=sidebyside;f=sgml%2Fadminmanual.sgml;h=d61944f320dc1dc136080c413aba5d298fedfd7b;hb=b2478484ac66d4c499a2348b8163a7e0966f4250;hp=2bffd437b8ebe8e8f285beb2d2112495a12d0b2b;hpb=3f9573f9a338248cd6129ad864ab0ffa2e132cad;p=spider.git diff --git a/sgml/adminmanual.sgml b/sgml/adminmanual.sgml index 2bffd437..d61944f3 100644 --- a/sgml/adminmanual.sgml +++ b/sgml/adminmanual.sgml @@ -6,7 +6,7 @@
-Last modified: 13 January 2001 by Ian Maude, G0VGS
-
@@ -1312,6 +1309,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.
+That is it! the kepler data has been updated.
-
-To edit the colours, copy /spider/perl/Console.pl to /spider/local and edit the
-file with your favourite editor.
+
+
+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.
+