+ 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
+
+ One of the more important things a cluster sysop needs to do is to get
+ information to his users. The simplest way to do this is to have a
+ banner that is sent to the user on login. This is know as a "message
+ of the day" 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.
+
+
+ 1\b11\b1.\b.2\b2.\b. D\bDo\bow\bwn\bnt\bti\bim\bme\be m\bme\bes\bss\bsa\bag\bge\be
+
+ If for any reason the cluster is down, maybe for upgrade or
+ maintenance but the machine is still running, a message can be sent to
+ the user advising them of the fact. This message lives in the
+ /spider/data directory and is called "offline". Simply create the
+ file and edit it to say whatever you wish. This file will be sent to
+ a user attempting to log into the cluster when DXSpider is not
+ actually running.
+
+
+ 1\b11\b1.\b.3\b3.\b. O\bOt\bth\bhe\ber\br t\bte\bex\bxt\bt m\bme\bes\bss\bsa\bag\bge\bes\bs
+
+ You can set other text messages to be read by the user if they input
+ the file name. This could be for news items or maybe information for
+ new users. To set this up, make a directory under /spider called
+ _\bp_\ba_\bc_\bk_\bc_\bl_\bu_\bs. Under this directory you can create files called _\bn_\be_\bw_\bs or
+ _\bn_\be_\bw_\bu_\bs_\be_\br for example. In fact you can create files with any names you
+ like. These can be listed by the user with the command ....
+
+
+ show/files
+
+
+
+
+ They can be read by the user by typing the command ....
+
+
+
+ type news
+
+
+
+
+ If the file they want to read is called _\bn_\be_\bw_\bs. You could also set an
+ alias for this in the Alias file to allow them just to type _\bn_\be_\bw_\bs
+
+
+ You can also store other information in this directory, either
+ directly or nested under directories. One use for this would be to
+ store DX bulletins such as the OPDX bulletins. These can be listed
+ and read by the user. To keep things tidy, make a directory under
+ /spider/packclus called _\bb_\bu_\bl_\bl_\be_\bt_\bi_\bn_\bs. Now copy any OPDX or similar
+ bulletins into it. These can be listed by the user in the same way as
+ above using the _\bs_\bh_\bo_\bw_\b/_\bf_\bi_\bl_\be_\bs command with an extension for the bulletins
+ directory you have just created, like this ....
+
+
+
+ show/files bulletins
+
+
+
+
+
+ An example would look like this ....
+
+
+
+ sh/files
+ bulletins DIR 20-Dec-1999 1715Z news 1602 14-Dec-1999 1330Z
+
+
+
+
+ You can see that in the files area (basically the packclus directory)
+ there is a file called _\bn_\be_\bw_\bs and a directory called _\bb_\bu_\bl_\bl_\be_\bt_\bi_\bn_\bs. You can
+ also see that dates they were created. In the case of the file _\bn_\be_\bw_\bs,
+ you can also see the time it was last modified, a good clue as to
+ whether the file has been updated since you last read it. To read the
+ file called _\bn_\be_\bw_\bs you would simply issue the command ....
+
+
+
+ type news
+
+
+
+
+ To look what is in the bulletins directory you issue the command ....
+