-From version 1.47 there is a new (more efficient) way of doing 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.
@@ -79,7 +79,7 @@ telnet localhost 8000
From version 1.47 you can choose to allow the perl cluster.pl program to +
>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.
@@ -467,7 +467,7 @@ DX:3:respawn:/bin/su -c "/usr/bin/perl -w /spider/perl/cluster.pl" sysop >/dev/t
This line works fine for RedHat distributions. It is also fine for SuSE up to -7.0. From Suse 7.1 you need to add runlevels 2 and 5 like this ... +7.0. From SuSE 7.1 you need to add runlevels 2 and 5 like this ...
@@ -487,6 +487,9 @@ DX:23:respawn:/bin/su - sysop -c "/usr/bin/perl -w /spider/perl/cluster.pl" >/de
This will automatically start DXSpider on tty7 (ALT-F7) on bootup and restart
it should it crash for any reason.
+
NB: It should be noted that /dev/tty7 is only an example. Some SuSE systems will
+only accept upto tty6. It really does not matter which tty you run it on.
+
As root type the command telinit q. DXSpider should start up
immediately. You will see the output on tty7 and if you login as sysop
you should find everything running nicely.