X-Git-Url: http://scm.dxcluster.org/gitweb/gitweb.cgi?a=blobdiff_plain;f=sgml%2Fadminmanual.sgml;h=39ec64313b937908ad8d4ef2e42b24baf9191516;hb=ab0ea211ea17085944f4ce2b0100932fa6af02c8;hp=6f807633730f90a06f42da62daa854351afde06c;hpb=6374fb31da62987e676244c38eb6cf73c81bf891;p=spider.git diff --git a/sgml/adminmanual.sgml b/sgml/adminmanual.sgml index 6f807633..39ec6431 100644 --- a/sgml/adminmanual.sgml +++ b/sgml/adminmanual.sgml @@ -6,7 +6,8 @@
This section is designed for experienced Spider sysops who want to install
@@ -328,10 +329,10 @@ or, if you wish your users to be able to use SSID's on their callsigns ..
default * * * * * * - sysop /spider/src/client client %s ax25
-For most purposes this is not desirable. The only time you probably will need this is
-when you need to allow other cluster nodes that are using SSID's in. In this case it
-owuld probably be better to use the first example and then add a specific line for that
-node like this:
+For most purposes this is not desirable. The only time you probably will
+need this is when you need to allow other cluster nodes that are using SSID's
+in. In this case it would probably be better to use the first example and
+then add a specific line for that node like this:
-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.
+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 ....
@@ -390,8 +392,8 @@ 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
+From version 1.47 you can choose to allow the perl cluster.pl program to
+allow connections directly (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.
@@ -403,51 +405,57 @@ up in /etc/inetd.conf. Remember to:-
killall -HUP inetd
+
to make the change happen... -
-Having done that then you need to copy the file -/spider/perl/Listeners.pm to /spider/local and +
+Having done that, 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:- +
+As standard, the listener will listen on all interfaces simultaneously.
+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. +
+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 that 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.
+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.
+
+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:-
+
+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:-
+
+
+This command allows you to see all the users that can be seen
+and the nodes to which they are connected. With the optional node,
+you can specify a particular node to look at.
+
+This command is normally abbreviated to: sh/c
+
+BE WARNED: the list that is returned can be VERY long
+
+
+
+
+Show all the nodes connected locally and the nodes they have connected.
+
+
+
+
+This command shows information on all the active connections known to
+the node. This command gives slightly more information than WHO.
+