Spider allows the creation of local or remote databases. It supports -chained databases, allowing several different databases to be scanned -with one simple command. Importing of databases is limited at present -to the standard AK1A databases such as OBLAST and the DB0SDX QSL -database but will expand with time. -
-
Creating a database could not be more simple. All the commands are -sent from the cluster prompt as the sysop user. -
To create a database you use the command dbcreate. It can -be used in 3 different ways like so .. +
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.
-
-
-dbcreate <name>
-
-To simply create a database locally, you just tell the command the -name of the database. This does not create the actual database, it -simply defines it to say that it exists. +
THIS IS NOT FOR THE FAINT HEARTED!!! ONLY DO THIS IF YOU HAVE A TEST +INSTALLATION OR ARE WILLING TO HAVE YOUR CLUSTER CRASH ON YOU!!! +THIS MUST BE CONSIDERED AT LEAST BETA TESTING AND MAYBE EVEN ALPHA!! +YOU HAVE BEEN WARNED!!!
-
-
-dbcreate <name> chain <name> [<name>...]
-
-This creates a chained database entry. The first database will be -scanned, then the second, the third etc... +
DID I MENTION..... ONLY DO THIS IF YOU ARE WILLING TO ACCEPT THE +CONSEQUENCES!!!
-
-
-dbcreate <name> remote <name>
-
-This creates a remote entry. the first name field is the database -name at the remote node, then the remote switch, then the actual -node_call of the remote node, for example... +
I am of course assuming that you have a machine with both DXSpider and +Internet access running.
-
-
-dbcreate buckmaster remote gb7dxc
-
-Remote databases cannot be chained, however, the last database in a -chain can be a remote database. +
BEFORE YOU EVEN CONSIDER STARTING WITH THIS MAKE A BACKUP OF YOUR +ENTIRE SPIDER TREE!!
-
The only databases that Spider can currently import are the standard -AK1A databases such as OBLAST or the DB0SDX qsl and address database. -This will be added to with time. -
To import such a database, first put the file somewhere useful like /tmp -and then issue the following command ... +
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 ...
-
-dbimport oblast /tmp/OBLAST.FUL
+cvs -d:pserver:anonymous@cvs.DXSpider.sourceforge.net:/cvsroot/dxspider login
-This will update the existing local oblast database or create it if -it does not exist. +
You will get a password prompt. Simply hit return here and your machine should +return to a normal linux prompt.
-
Once a database is created, you will want to check that it has been -added. To do this use the dbavail command. This will -output the available databases. For example ... +
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.
-
-dbavail
-DB Name Location Chain
-qsl Local
-buck GB7ADX
-hftest GB7DXM
-G0VGS de GB7MBC 3-Feb-2001 1925Z >
+cvs -z3 -d:pserver:anonymous@cvs.DXSpider.sourceforge.net:/cvsroot/dxspider co spider
-This command is all on one line.
-
To look for information in a defined database, simply use the dbshow -command, for example ... +
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.
-
-
-dbshow buckmaster G0YLM
-
-will show the information for the callsign G0YLM from the buckmaster -database if it exists. To make things more standard for the users -you can add an entry in the Aliases file so that it looks like a standard -show command like this ... +
Now if you are doing a new installation, that's it. Carry on as if you have +just downloaded and untarred the lastest tarball. +
+
If you want to upgrade your current installation then do this ...
-'^sh\w*/buc', 'dbshow buckmaster', 'dbshow',
+tar cvfz /tmp/s.tgz spider
+cd /
+tar xvfzp /tmp/s.tgz
Now you can simply use show/buckmaster or an abreviation. +
This is assuming you downloaded to the /tmp directory of course.
-
To delete an existing database you use the dbremove command. -For example ... +
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 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! +
+
Now the magic part! From now on when you want to update, simply connect to the +Internet and then, as the user sysop ...
-dbremove oblast
+cd /spider
+cvs -z3 update -d
would remove the oblast database and its associated datafile from the -system. There are no warnings or recovery possible from this command. -If you remove a database it ceases to exist and would have to be created -from scratch if you still required it. +
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.