X-Git-Url: http://gb7djk.dxcluster.net/gitweb/gitweb.cgi?a=blobdiff_plain;f=html%2Fadminmanual-3.html;h=83fe1c0c699ea315d627fdb4ca6370c1a2939599;hb=ecd9c3904c5859a2db92fd2668ea756186eda699;hp=e9c3d67ba970b2363c369cc27570aeaab51b45a0;hpb=439f25ba04e8c4ddbd6806f31da58c0939e2c868;p=spider.git diff --git a/html/adminmanual-3.html b/html/adminmanual-3.html index e9c3d67b..83fe1c0c 100644 --- a/html/adminmanual-3.html +++ b/html/adminmanual-3.html @@ -6,6 +6,7 @@ + Next @@ -27,6 +28,13 @@ each interface that you wish to allow connections on, use the following format . default * * * * * * - sysop /spider/src/client client %u ax25 +

or, if you wish your users to be able to use SSID's on their callsigns .. +

+

+
+default  * * * * * *  - sysop /spider/src/client client %s ax25
+
+

3.2 Allowing telnet connects from users

@@ -57,12 +65,12 @@ killall -HUP inetd

-

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 .... 

-client.pl login telnet
+./client login telnet

You should get a login prompt and on issuing a callsign, you will be given @@ -105,7 +113,7 @@ set/clx

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 ...

@@ -119,11 +127,11 @@ set/node gb7baa 1.33. Earlier versions required the callsign to be in upper case.

That is now set, it is as simple as that. To prove it, login on yet another -console as sysop and issue the command ... +console as sysop, cd to spider/src and issue the command ... 

-client.pl gb7baa (using the callsign you set as a node)
+./client gb7baa (using the callsign you set as a node)

@@ -131,7 +139,7 @@ client.pl gb7baa (using the callsign you set as a node) 

-client.pl gb7baa
+./client gb7baa
 PC38^GB7MBC^~
@@ -341,65 +349,6 @@ have no control over it. The chances are that this link will create echo and there will be no way you can stop it.

-

3.7 Automating things -

- -

Ok, you should now have DXSpider running nicely and allowing connects by cluster -nodes or users. However, it has to be shutdown and restarted manually and if -connection scripts fail they have to be started again manually too, not much use -if you are not at the console! So, in this section we will automate both. -Firstly starting the cluster. -

-

Autostarting the cluster

- -

This is not only a way to start the cluster automatically, it also works as a -watchdog, checking the sanity of DXSpider and respawning it should it crash for -any reason. Before doing the following, shutdown the cluster as you did earlier. -

-

Login as root and bring up the /etc/inittab file in your favourite editor. Add -the following lines to the file near the end ... -

-

-
-##Start DXSpider on bootup and respawn it should it crash
-DX:3:respawn:/bin/su -c "/usr/bin/perl -w /spider/perl/cluster.pl" sysop >/dev/tty7
-
-
-

-

This will automatically start DXSpider on tty7 (ALT-F7) on bootup and restart -it should it crash for any reason. -

-

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. -

-

So far so good, now to automate script connections... -

-

The crontab file

- -

Login as sysop and create a file in /spider/local_cmd called crontab. -Edit it with your favourite editor and add a line like this (I have included -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')
-
-
-

-

The callsign involved will be the callsign of the cluster node you are -going to connect to. This will now check every 10 minutes to see if -gb7xxx is connected, if it is then nothing will be done. If it is not, -then a connect attempt will be started. -

-

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 -DXSpider website -at the cron page where it is explained more fully. -

Next Previous