X-Git-Url: http://dxcluster.org/gitweb/gitweb.cgi?a=blobdiff_plain;f=html%2Fadminmanual-5.html;fp=html%2Fadminmanual-5.html;h=0000000000000000000000000000000000000000;hb=7d315a555a73d4a650405d0c2da48bacde2b1853;hp=57b15b2492a57d129500dad223a1c2119b6b1ce9;hpb=1bb3ae1a09a6117d93c02041bff9b5cd2d4819ef;p=spider.git diff --git a/html/adminmanual-5.html b/html/adminmanual-5.html deleted file mode 100644 index 57b15b24..00000000 --- a/html/adminmanual-5.html +++ /dev/null @@ -1,154 +0,0 @@ - - -
- -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 ..
--
-
-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.
--
-
-dbcreate <name> chain <name> [<name>...]
-
-
-
-This creates a chained database entry. The first database will be -scanned, then the second, the third etc...
--
-
-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...
--
-
-dbcreate buckmaster remote gb7dxc
-
-
-
-Remote databases cannot be chained, however, the last database in a -chain can be a remote database.
- -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 ...
--
-
-dbimport oblast /tmp/OBLAST.FUL
-
-
-
-This will update the existing local oblast database or create it if -it does not exist.
- -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 ...
--
-
-dbavail
-DB Name Location Chain
-qsl Local
-buck GB7ADX
-hftest GB7DXM
-G0VGS de GB7MBC 3-Feb-2001 1925Z >
-
-
-
-
-To look for information in a defined database, simply use the dbshow -command, for example ...
--
-
-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 ...
--
-
-'^sh\w*/buc', 'dbshow buckmaster', 'dbshow',
-
-
-
-Now you can simply use show/buckmaster or an abreviation.
- -To delete an existing database you use the dbremove command. -For example ...
--
-
-dbremove oblast
-
-
-
-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.
- -