X-Git-Url: http://dxcluster.org/gitweb/gitweb.cgi?a=blobdiff_plain;f=sgml%2Fadminmanual.sgml;h=d5af7064566a5b3de33d9fdde9e3b5ff76bcdad4;hb=5b621c40fa6165a9f0eaf592d24a63a174e4b902;hp=4a25de0cbb479a821f38c2a773f59283d57fc6fd;hpb=f522780bffd435c31b544944063da62a86f9c363;p=spider.git diff --git a/sgml/adminmanual.sgml b/sgml/adminmanual.sgml index 4a25de0c..d5af7064 100644 --- a/sgml/adminmanual.sgml +++ b/sgml/adminmanual.sgml @@ -4,9 +4,9 @@ -
-You can set what hops have been set using the show/hops command.
+You can show what hops have been set using the show/hops command.
To force the cluster to reread the file use load/forward
+
+NB: If a user tries to send mail to a bulletin address that does not exist
+in this file, they will get an error.
-As usual, any text behind a # is treated as a comment and not read.
+As usual, any text behind a # is treated as a comment and not read. To use
+this file, simply rename it from startup.issue to startup. In our example
+above there are three options. The first option is the amount of spots that
+a user can request with the sh/dx command. Normally the default is
+to give 10 spots unless the user specifies more. Without this line enabled,
+the maximum a user can request is 100 spots. Depending on your link quality
+you may wish to enable more or less by specifying the number.
+
+
+The other 2 options are dealt with more fully in the security section.
+
Secondly, it is used to store the login scripts for users and nodes. Currently
this can only be done by the sysop but it is envisaged that eventually users will
be able to set their own. An example is included in the distibution but here is
@@ -1200,149 +1213,76 @@ The page length will of course depend on what you have it set to!
-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 ...
-
-
+You should not alter the original file in /spider/cmd/ but create a new file
+with the same name in /spider/local_cmd. This means that any new Aliases files
+that is downloaded will not overwrite your self created Aliases and also that
+you do not override any new Aliases with your copy in /spider/local_cmd/. You
+must remember that any files you store in /spider/local/ or /spider/local_cmd
+override the originals if the same lines are used in both files.
-# 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.
+
+The best way of dealing with all this then is to only put your own locally
+created Aliases in the copy in /spider/local_cmd. The example below is
+currently in use at GB7MBC.
+
+Each alphabetical section should be preceded by the initial letter and the section
+should be wrapped in square brackets as you can see. The syntax is straightforward.
+The first section on each line is the new command that will be allowed once the
+alias is included. The second section is the command it is replacing and the last
+section is the actual command that is being used.
+
+
+The eagle-eyed amongst you will have noticed that in the first section, the new
+alias command has a '^' at the start and a '$' at the end. Basically these force
+a perfect match on the alias. The '^' says match the beginning exactly and the
+'$' says match the end exactly. This prevents unwanted and unintentional matches
+with similar commands.
+
+
+I have 3 different types of alias in this file. At the top is an alias for 'news'.
+This is a file I have created in the /spider/packclus/ directory where I can inform
+users of new developments or points of interest. In it's initial form a user would
+have to use the command type news. The alias allows them to simply type
+news to get the info. Second is an alias for the show/qrz
+command so that those users used to the original show/buck command in
+AK1A will not get an error, and the rest of the lines are for locally created
+databases so that a user can type show/hftest instead of having to use
+the command dbshow hftest which is not as intuitive.
+
+
+This file is just an example and you should edit it to your own requirements.
+Once created, simply issue the command load/alias at the cluster
+prompt as the sysop user and the aliases should be available.
+
would export message number 5467 as a file called keps.in in the
/spider/perl directory.
+
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 ...
@@ -1380,12 +1322,14 @@ convert the file like so ...
./convkeps.pl keps.in
+
Now go back to the cluster and issue the command ...
That is it! the kepler data has been updated.
+There appear to be very few logging programs out there that support telnet
+especially the popular ones like LogEQF, Turbolog etc. This can make it
+difficult to connect to your own cluster!
+The way to do it is to make the logging program think it has a TNC attached
+to a com port on the logging PC and 'push' a linux login out to it.
+This is achieved very simply by the use of agetty.
+
+
+All that is required is to add a line in /etc/inittab to have the client
+ready for a connection on the com port of your choice. Remember that in
+Linux, the com ports start at ttyS0 for com1, ttyS1 for com2 etc.
+
+
+Add this after the standard runlevel lines in /etc/inittab. The above
+line works on ttyS1 (com2). Now as root, issue the command telinit q
+and it should be ready for connection. All that is required is a 3 wire
+serial lead (tx, rx and signal ground). Tell you logging program to use
+8n1 at 9600 baud and you should see a Linux login prompt. Login as normal
+and then telnet from there to the cluster.
+
+
+In the spider tree will be a directory spider-web. This is a
+neat little java web applet that can be run from a website. The applet
+must run on the same machine as the cluster. The included README file is
+shown below.
+
+
+I should comment here that the applet is precompiled, that is, ready to go.
+It was compiled using JDK1.3.1. If your version is earlier than this then it
+may not work. Should that be the case you need to recompile or update your
+JDK. To recompile do the following ...
+
+
+I have used /usr/bin/javac as an example, your path to javac may be different.
+
+
@@ -2288,6 +2333,27 @@ There is NO SECOND CHANCE.
It goes without saying that you should use this command CAREFULLY!
+
+
+
+This command is provided so that sysops can demonstrate commands to
+other users. It runs a command as though that user had typed it in and
+then sends the output to that user, together with the command that
+caused it.
+
+