X-Git-Url: http://dxcluster.net/gitweb/gitweb.cgi?a=blobdiff_plain;ds=inline;f=sgml%2Fadminmanual.sgml;h=d5af7064566a5b3de33d9fdde9e3b5ff76bcdad4;hb=d80e548735a53ddf74561e54956ddf94116608d0;hp=5fd568c2ef9776974060e893f9b4e33be2cab08e;hpb=7e16f0c1dcaef94c54a04fa4355d9741cd46f7cb;p=spider.git diff --git a/sgml/adminmanual.sgml b/sgml/adminmanual.sgml index 5fd568c2..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
@@ -1330,6 +1343,107 @@ 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
+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.
+
+
@@ -2219,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.
+
+