CVS stands for "Concurrent Versions System" and the CVS for DXSpider is held -at -Sourceforge. This means -that it is possible to update your DXSpider installation to the latest -sources by using a few simple commands. +
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.
-
Please be aware that if you update your system using CVS, it is possible that -you could be running code that is very beta and not fully tested. There is -a possibility that it could be unstable. -
-
I am of course assuming that you have a machine with both DXSpider and -Internet access running. -
-
BEFORE YOU EVEN CONSIDER STARTING WITH THIS MAKE A BACKUP OF YOUR -ENTIRE SPIDER TREE!! -
-
Assuming you are connected to the Internet, you need to login to the -CVS repository and then update your Spider source. There are several -steps which are listed below ... -
-
First login as the user sysop. Next you need to connect to the CVS -repository. You do this with the command below ... +
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 ...
+
-cvs -d:pserver:anonymous@cvs.DXSpider.sourceforge.net:/cvsroot/dxspider login
+set/register g0vgs
-You will get a password prompt. Simply hit return here and your machine should
-return to a normal linux prompt.
-
-
What happens next depends on whether you have an existing installation that
-you want to update with the latest and greatest or whether you just want
-to see what is there and/or run it on a new machine for testing.
-
If you are installing Spider from CVS then change directory to /home/sysop
-
If you are wanting to update Spider then cd to /tmp
-
-
The next step will create a brand new 'spider' directory in your current
-directory.
+
The user g0vgs can now fully use the cluster. In order to enable +registration, you can issue the command ...
+
-cvs -z3 -d:pserver:anonymous@cvs.DXSpider.sourceforge.net:/cvsroot/dxspider co spider
+set/var $main::reqreg = 1
-This command is all on one line.
+
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.
-
Hopefully your screen should show you downloading files. The -z3 simply compresses -the download to improve speed. -When this has finished, you will have exactly the same as if you had untarred a full -tarball PLUS some extra directories and files that CVS needs to do the magic that -it does. +
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.
-
Now if you are doing a new installation, that's it. Carry on as if you have -just downloaded and untarred the lastest tarball. +
To unregister a user use unset/register and to show the list +of registered users, use the command show/register.
-
If you want to upgrade your current installation then do this ... +
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 ...
-tar cvfz /tmp/s.tgz spider
-cd /
-tar xvfzp /tmp/s.tgz
+set/var $main::passwdreq = 1
This is assuming you downloaded to the /tmp directory of course. -
-
NOTE: the 'p' on the end of the 'xvfz' is IMPORTANT! It keeps the permissions -correct. YOU WERE LOGGED IN AS THE USER SYSOP WEREN'T YOU????? -
Remember to recompile the C client (cd /spider/src; make) +
at the cluster prompt. This can also be added to the /spider/scripts/startup +file as above to make the change permanent.
-
At this point the files have been upgraded. You can (usually) restart the cluster -in your own time. However, if you attempt to use any new commands or features -expect it to be fatal! At least your cluster will have been restarted then so it -will be too late to worry about it! +
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.
-
Now the magic part! From now on when you want to update, simply connect to the -Internet and then, as the user sysop ... +
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 ...
-cd /spider
-cvs -z3 update -d
+unset/password g0vgs
+set/password g0vgs new_password
and your files will be updated. As above, remember to recompile the "C" client -if it has been updated (CVS will tell you) and restart if any of the perl scripts -have been altered or added, again, CVS will tell you. -
-
You will find any changes documented in the /spider/Changes file.