X-Git-Url: http://dxcluster.org/gitweb/gitweb.cgi?a=blobdiff_plain;f=sgml%2Fadminmanual.sgml;h=6f807633730f90a06f42da62daa854351afde06c;hb=cfde73187c90e1c260c2339332b7773ecfbb8309;hp=034111d3a5cfdad8a6a9ca789ef89e9040ec4fe6;hpb=b21ba4d796c6e285685a18be32f538facb2408c5;p=spider.git diff --git a/sgml/adminmanual.sgml b/sgml/adminmanual.sgml index 034111d3..6f807633 100644 --- a/sgml/adminmanual.sgml +++ b/sgml/adminmanual.sgml @@ -4,9 +4,9 @@ -
+This section is designed for experienced Spider sysops who want to install
+Spider from scratch. It is simply a check list of things that need to be
+done without any explanations. The name in brackets at the end of each line
+is the user that should be doing that process.
+
+
+From version 1.47 there is a new (more efficient) way of doing this (see next section) but,
+if you prefer, the method of doing it described here will continue to work just fine.
+
Allowing telnet connections is quite simple. Firstly you need to add a line
in /etc/services to allow connections to a port number, like this ....
-This needs to be added above the standard services such as ftp, telnet etc.
Once this is done, you need to restart inetd like this ....
Now login as sysop and cd spider/perl. You can test that spider
+ Now login as sysop and cd spider/src. You can test that spider
is accepting telnet logins by issuing the following command ....
You should now get the login prompt and be able to login as before.
+
+From version 1.47 you can chose to allow the perl cluster.pl program to
+allow connections direct (i.e. not via the /spider/src/client
+interface program). If you are using Windows then this is the only method
+available of allowing incoming telnet connections.
+
+
+To do this you need first to remove any line that you may previously have set
+up in /etc/inetd.conf. Remember to:-
+
+
+to make the change happen...
+
+
+Having done that then you need to copy the file
+/spider/perl/Listeners.pm to /spider/local and
+then edit it. You will need to uncomment the line containing &dquot;0.0.0.0&dquot;
+and select the correct port to listen on. So that it looks like this:-
+
+ As standard, the listener will listen on all interfaces simultaniously. If you require more
+control than this, you can specify each interface individually:-
+
+ This will only be successful if the IP addresses on each interface are static.
+If you are using some kind of dynamic IP addressing then the 'default' method is the
+only one which will work.
+
+
+Restart the cluster.pl program to enable the listener.
+
+
+One important difference with the internal listener is that no echoing is done by the
+cluster program. Users will need to set 'local-echo' on in their telnet clients if
+it isn't set automatically (as per the standards). Needless to say this will probably
+only apply to Windows users.
+
+ AGW Engine is a Windows based ax25 stack. You can connect to an AGW engine from Linux
+as well as Windows based machines.
+
+ In order to enable access to an AGW Engine you need to copy /spider/perl/AGWConnect.pm
+to /spider/local and edit it. Specifically you must:-
+
+
@@ -347,7 +486,7 @@ For now, we will assume that the cluster we are going to connect to is an
AK1A type node.
-Start up the cluster as you did before and login as the sysop with client.pl.
+Start up the cluster as you did before and login as the sysop with client.
The cluster node I am wanting to make a connection to is GB7BAA but you would
obviously use whatever callsign you required. At the prompt type ...
@@ -361,17 +500,17 @@ The case does not matter as long as you have a version of DXSpider later than
That is now set, it is as simple as that. To prove it, login on yet another
-console as sysop, cd to spider/perl and issue the command ...
+console as sysop, cd to spider/src and issue the command ...
You should get an initialisation string from DXSpider like this ...
+Sometimes you make a mistake... Honest, it does happen. If you want to make a node
+back to being a normal user, regardless
+of what type it is, do:
+
+
@@ -391,20 +539,20 @@ Writing a script for connections is therefore relatively simple.
The connect scripts consist of lines which start with the following keywords
or symbols:-
-
+
+
Telnet echo itself should only be a problem if the connection is being made to
the telnet port (23). This port uses special rules that include echo negotiation.
-If the connection is to a different port, such as 8000, this negotiation does
+If the connection is to a different port, such as 7300, this negotiation does
not happen and therefore no echo should be present.
@@ -641,7 +805,7 @@ a comment)
# check every 10 minutes to see if gb7xxx is connected and if not
# start a connect job going
-0,10,20,30,40,50 * * * * start_connect('gb7xxx') if !connected('gb7xxx')
+0,10,20,30,40,50 * * * * start_connect('gb7xxx') if unless connected('gb7xxx')
@@ -1686,13 +1850,13 @@ You can also store other information in this directory, either directly or
nested under directories. One use for this would be to store DX bulletins
such as the OPDX bulletins. These can be listed and read by the user.
To keep things tidy, make a directory under /spider/packclus called
-bulletins. Now copy any OPDX or similar bulletins into it. These
+bulletin. Now copy any OPDX or similar bulletins into it. These
can be listed by the user in the same way as above using the show/files
-command with an extension for the bulletins directory you have just created,
+command with an extension for the bulletin directory you have just created,
like this ....
@@ -1700,11 +1864,11 @@ An example would look like this ....
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.
+announces etc. To use this program, simply use console.pl instead of client.
To edit the colours, copy /spider/perl/Console.pl to /spider/local and edit the