+
+
+
+ These commands are simply typed from within the cluster as the sysop
+ user.
+
+
+ 9\b9.\b.5\b5.\b. M\bMe\bes\bss\bsa\bag\bge\be s\bst\bta\bat\btu\bus\bs
+
+ You can check on a message from within the cluster by using the
+ command _\bs_\bt_\ba_\bt_\b/_\bm_\bs_\bg. This will give you additional information on the
+ message number including which nodes have received it, which node it
+ was received from and when etc. Here is an example of the output of
+ the command ...
+
+
+
+ G0VGS de GB7MBC 28-Jan-2001 1308Z >
+ stat/msg 6869
+ From: GB7DJK
+ Msg Time: 26-Jan-2001 1302Z
+ Msgno: 6869
+ Origin: GB7DJK
+ Size: 8012
+ Subject: AMSAT 2line KEPS 01025.AMSAT
+ To: UK
+ Got it Nodes: GB7BAA, GB7ADX
+ Private: 0
+ Read Confirm: 0
+ Times read: 0
+ G0VGS de GB7MBC 28-Jan-2001 1308Z >
+
+
+
+
+
+ 9\b9.\b.6\b6.\b. F\bFi\bil\blt\bte\ber\bri\bin\bng\bg m\bma\bai\bil\bl
+
+ This is described in the section on _\bO_\bt_\bh_\be_\br _\bf_\bi_\bl_\bt_\be_\br_\bs so I will not
+ duplicate it here.
+
+
+ 9\b9.\b.7\b7.\b. D\bDi\bis\bst\btr\bri\bib\bbu\but\bti\bio\bon\bn l\bli\bis\bst\bts\bs
+
+ Distribution lists are simply a list of users to send certain types of
+ mail to. An example of this is mail you only wish to send to other
+ sysops. In /spider/msg there is a directory called _\bd_\bi_\bs_\bt_\br_\bo. You put
+ any distibution lists in here. For example, here is a file called
+ SYSOP.pl that caters for the UK sysops.
+
+
+ qw(GB7TLH GB7DJK GB7DXM GB7CDX GB7BPQ GB7DXN GB7MBC GB7MBC-6 GB7MDX
+ GB7NDX GB7SDX GB7TDX GB7UDX GB7YDX GB7ADX GB7BAA GB7DXA GB7DXH
+ GB7DXK GB7DXI GB7DXS)
+
+
+
+
+ Any mail sent to "sysop" would only be sent to the callsigns in this
+ list.
+
+
+ 9\b9.\b.8\b8.\b. B\bBB\bBS\bS i\bin\bnt\bte\ber\brf\bfa\bac\bce\be
+
+ Spider provides a simple BBS interface. No input is required from the
+ sysop of the cluster at all. The BBS simply sets the cluster as a BBS
+ and pushes any required mail to the cluster. No mail can flow from
+ Spider to the BBS, the interface is one-way.
+
+
+ Please be careful not to flood the cluster network with unnecessary
+ mail. Make sure you only send mail to the clusters that want it by
+ using the Forward.pl file very carefully.
+
+
+ 1\b10\b0.\b. D\bDa\bat\bta\bab\bba\bas\bse\bes\bs
+
+ 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.
+
+
+ 1\b10\b0.\b.1\b1.\b. C\bCr\bre\bea\bat\bti\bin\bng\bg d\bda\bat\bta\bab\bba\bas\bse\bes\bs
+
+ Creating a database could not be more simple. All the commands are
+ sent from the cluster prompt as the _\bs_\by_\bs_\bo_\bp user.
+
+ To create a database you use the command _\bd_\bb_\bc_\br_\be_\ba_\bt_\be. 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.
+
+
+ 1\b10\b0.\b.2\b2.\b. I\bIm\bmp\bpo\bor\brt\bti\bin\bng\bg d\bda\bat\bta\bab\bba\bas\bse\bes\bs
+
+ 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.
+
+
+ 1\b10\b0.\b.3\b3.\b. C\bCh\bhe\bec\bck\bki\bin\bng\bg a\bav\bva\bai\bil\bla\bab\bbl\ble\be d\bda\bat\bta\bab\bba\bas\bse\bes\bs
+
+ Once a database is created, you will want to check that it has been
+ added. To do this use the _\bd_\bb_\ba_\bv_\ba_\bi_\bl 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 >
+
+
+
+
+
+ 1\b10\b0.\b.4\b4.\b. L\bLo\boo\bok\bki\bin\bng\bg u\bup\bp d\bda\bat\bta\bab\bba\bas\bse\bes\bs
+
+ To look for information in a defined database, simply use the _\bd_\bb_\bs_\bh_\bo_\bw
+ 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
+ _\bs_\bh_\bo_\bw command like this ...
+
+
+
+
+
+
+
+ Now you can simply use show/buckmaster or an abreviation.
+
+
+ 1\b10\b0.\b.5\b5.\b. R\bRe\bem\bmo\bov\bvi\bin\bng\bg d\bda\bat\bta\bab\bba\bas\bse\bes\bs
+
+ To delete an existing database you use the _\bd_\bb_\br_\be_\bm_\bo_\bv_\be 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.
+
+
+ 1\b11\b1.\b. I\bIn\bnf\bfo\bor\brm\bma\bat\bti\bio\bon\bn,\b, f\bfi\bil\ble\bes\bs a\ban\bnd\bd u\bus\bse\bef\bfu\bul\bl p\bpr\bro\bog\bgr\bra\bam\bms\bs
+
+ 1\b11\b1.\b.1\b1.\b. M\bMO\bOT\bTD\bD