X-Git-Url: http://scm.dxcluster.org/gitweb/gitweb.cgi?a=blobdiff_plain;f=html%2Fadminmanual-4.html;h=f74b9e43dddbff1bf9cbc1b612a1b8483bb4c400;hb=584945a122922aebe94f733c8f9a734f412aa5cb;hp=d7652b3f4c018fd6a63b14c78c172da93847688a;hpb=e674587476599456cce169e02b0e441d985f9dd8;p=spider.git diff --git a/html/adminmanual-4.html b/html/adminmanual-4.html index d7652b3f..f74b9e43 100644 --- a/html/adminmanual-4.html +++ b/html/adminmanual-4.html @@ -1,8 +1,8 @@
- -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. -
-
From 1.48 onwards it will become increasingly possible to control DXSpider's +operation with scripts of various kinds.
-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 ... +
The directory /spider/scripts is where it all happens and is used for several +things. Firstly it contains a file called startup that can be used to call +in any changes to the cluster from the default settings on startup. This +script is executed immediately after all initialisation of the node is done +but before any connections are possible. Examples of this include how many +spots it is possible to get with the sh/dx command, whether you want +registration/passwords to be permanently on etc. An example file is shown +below and is included in the distribution as startup.issue.
-##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
+#
+# startup script example
+#
+# set maximum no of spots allowed to 100
+# set/var $Spot::maxspots = 100
+#
+# Set registration on
+# set/var $main::reqreg = 1
+#
+# Set passwords on
+# set/var $main::passwdreq = 1
+#
--
This line works fine for RedHat and SuSE distributions. The line required for -Slackware distributions is slightly different. My thanks to Aurelio, PA3EZL for -this information. +
+ +As usual, any text behind a # is treated as a comment and not read. To use +this file, simply rename it from startup.issue to startup. In our example +above there are three options. The first option is the amount of spots that +a user can request with the sh/dx command. Normally the default is +to give 10 spots unless the user specifies more. Without this line enabled, +the maximum a user can request is 100 spots. Depending on your link quality +you may wish to enable more or less by specifying the number.
+ +The other 2 options are dealt with more fully in the security section.
+ +Secondly, it is used to store the login scripts for users and nodes. Currently +this can only be done by the sysop but it is envisaged that eventually users will +be able to set their own. An example is included in the distibution but here is +a further example.
-DX:23:respawn:/bin/su - sysop -c "/usr/bin/perl -w /spider/perl/cluster.pl" >/dev/tty7
+#
+# G0FYD
+#
+blank +
+sh/wwv 3
+blank +
+sh/dx
+blank +
+t g0jhc You abt?
+blank +
--
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 lines in between commands can simply insert a blank line or a character +such as a + sign to make the output easier to read. Simply create this script +with your favourite editor and save it with the callsign of the user as the +filename. Filenames should always be in lower case.
-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
+Commands can be inserted in the same way for nodes. A node may wish a series
+of commands to be issued on login, such as a merge command for example.
+
+Thirdly, there are 2 default scripts for users and nodes who do not have a
+specifically defined script. These are user_default and
+node_default
-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. -