X-Git-Url: http://gb7djk.dxcluster.net/gitweb/gitweb.cgi?a=blobdiff_plain;f=sgml%2Fadminmanual.sgml;h=967a4cb36fc83595a6efce35fd6d3fb283a4a793;hb=0c1c82537e95268c2ef2b23b4e9ef317a0119b2d;hp=f075b7988bb9a35e03316d921e811fe9350b3e60;hpb=54d689969977ab0247f4e2b6768db6e5bfdaaa5d;p=spider.git diff --git a/sgml/adminmanual.sgml b/sgml/adminmanual.sgml index f075b798..967a4cb3 100644 --- a/sgml/adminmanual.sgml +++ b/sgml/adminmanual.sgml @@ -6,7 +6,7 @@ The DXSpider Administration Manual v1.48 Ian Maude, G0VGS, (ianmaude@btinternet.com) -Version 1.48 September 2001 revision 1.2 +Version 1.49 November 2001 revision 1.0 A reference for SysOps of the DXSpider DXCluster program. @@ -1041,6 +1041,13 @@ or "motd". To set this up, simply create a file in /spider/data called motd and edit it to say whatever you want. It is purely a text file and will be sent automatically to anyone logging in to the cluster. +MOTD_NOR + +

+This message of the day file lives in the same directory as the standard +motd file but is only sent to non-registered users. Once registered they +will receive the same message as any other user. + Downtime message

@@ -1349,6 +1356,130 @@ ID and password. You also at this point need to set $allow=1 to complete the setup. Many thanks to Fred Lloyd, the proprieter of for allowing this access. +Scripts + +

+The directory /spider/scripts 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. 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. + + +# +# startup script example +# +# set maximum no of spots allowed to 100 +# set/var $Spot::maxspots = 1 +# +# Set registration on +# set/var $main::reqreg = 1 +# +# Set passwords on +# set/var $main::passwdreq = 1 +# + + +Secondly, it is used to store the login scripts for users. 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. + + +# +# G0FYD +# +blank + +sh/wwv 3 +blank + +sh/dx +blank + +t g0jhc You abt? +blank + + + +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. + +Security + +

+From version 1.49 DXSpider has some additional security features. These +are not by any means meant to be exhaustive, however they do afford some +security against piracy. These two new features can be used independently +of each other or in concert to tighten the security. + +Registration + +

+The basic principle of registration is simple. If a user is not registered +by the sysop, then they have read-only access to the cluster. The only +thing they can actually send is a talk or a message to the sysop. In +order for them to be able to spot, send announces or talks etc the sysop +must register them with the set/register command, like this ... + + +set/register g0vgs + + +The user g0vgs can now fully use the cluster. In order to enable +registration, you can issue the command ... + + +set/var $main::reqreg = 1 + + +Any users that are not registered will now see the motd_nor file rather +than the motd file as discussed in the Information, files and useful +programs section. + +

+Entering this line at the prompt will only last for the time the cluster +is running of course and would not be present on a restart. To make the +change permanent, add the above line to /spider/scripts/startup. To +read more on the startup file, see the section on Information, files +and useful programs. + +

+To unregister a user use unset/register and to show the list +of registered users, use the command show/register. + +Passwords + +

+At the moment, passwords only affect users who login to a DXSpider +cluster node via telnet. If a user requires a password, they can +either set it themselves or have the sysop enter it for them by using +the set/password command. Any users who already have passwords, +such as remote sysops, will be asked for their passwords automatically +by the cluster. Using passwords in this way means that the user has a +choice on whether to have a password or not. To force the use of +passwords at login, issue the command ... + + +set/var $main::passwdreq = 1 + + +at the cluster prompt. This can also be added to the /spider/scripts/startup +file as above to make the change permanent. + +

+Of course, if you do this you will have to assign a password for each of +your users. If you were asking them to register, it is anticipated that +you would ask them to send you a message both to ask to be registered and +to give you the password they wish to use. + +

+Should a user forget their password, it can be reset by the sysop by +first removing the existing password and then setting a new one like so ... + + +unset/password g0vgs +set/password g0vgs new_password + + CVS