X-Git-Url: http://dxcluster.org/gitweb/gitweb.cgi?a=blobdiff_plain;ds=inline;f=sgml%2Fadminmanual.sgml;h=d5af7064566a5b3de33d9fdde9e3b5ff76bcdad4;hb=cb5f21f8f960a003b80e7415f945d718f4b7d43e;hp=2dc01d83de453229d416df47f355d7a3549471f6;hpb=9cfd05889c539c625a4fb3ee9fdbc0fea847452c;p=spider.git diff --git a/sgml/adminmanual.sgml b/sgml/adminmanual.sgml index 2dc01d83..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.
The other 2 options are dealt with more fully in the security section.
@@ -1341,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.
+
+
@@ -2230,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.
+
+