@@ -48,15 +48,31 @@ perl distribution.
+On most modern distributions most (if not all) the modules you will need are either included or
+can be loaded automatically. Please consult your distro's instructions for loading new programs
+and look for modules that usually start with the string "perl-". For instance:-
+
+
+Some distros are now packaging perl-DB_File separately as well, so you may have to add that to the list +above. +
Copy the CPAN modules listed above to a convenient place on your computer. One good
place would be /usr/local/packages, and the instructions which follow will assume that
@@ -66,54 +82,61 @@ that's where you have put them.
Log in as 'root', and make sure you're at '/root' before you continue. Here are exactly the commands you must issue next: -
+Only if you need to do these because your perl is old:-
+
+
@@ -234,8 +257,9 @@ $mycall = "GB7DJK";
-This is the call sign of your cluster. If you use an SSID then include it here
-also.
+This is the call sign of your cluster. Here in the UK we have
+separate callsigns for our cluster nodes. If you can't use a different callsign I suggest
+you use an SSID of '-2' for the node callsign '$mycall'.
This is dealt with in the previous section
-
+>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.
+
+
+to make the change happen...
+
+
+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.
+
+It comes out of the box looking something like:-
+
+
+Later versions have more comments in the Listeners.pm file that
+are designed to help you remove the correct '#' character.
+
+
+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 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.
+
+
>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
+(see previous section) but, if you prefer, the method of doing it described
here will continue to work just fine.
@@ -937,62 +1024,6 @@ telnet localhost 8000
You should now get the login prompt and be able to login as before.
-
->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.
-
-
-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, 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 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 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.
There are probably lots of other things you could use this crontab file for.
If you want to know more about it, look at the
-