- %alias = (
- '?' => [
- '^\?', 'apropos', 'apropos',
- ],
- 'a' => [
- '^ann.*/full', 'announce full', 'announce',
- '^ann.*/sysop', 'announce sysop', 'announce',
- '^ann.*/(.*)$', 'announce $1', 'announce',
- ],
- 'b' => [
- ],
- 'c' => [
- ],
- 'd' => [
- '^del', 'kill', 'kill',
- '^del\w*/fu', 'kill full', 'kill',
- '^di\w*/a\w*', 'directory all', 'directory',
- '^di\w*/b\w*', 'directory bulletins', 'directory',
- '^di\w*/n\w*', 'directory new', 'directory',
- '^di\w*/o\w*', 'directory own', 'directory',
- '^di\w*/s\w*', 'directory subject', 'directory',
- '^di\w*/t\w*', 'directory to', 'directory',
- '^di\w*/f\w*', 'directory from', 'directory',
- '^di\w*/(\d+)', 'directory $1', 'directory',
- ],
- 'e' => [
- ],
- 'f' => [
- ],
- 'g' => [
- ],
- 'h' => [
- ],
- 'i' => [
- ],
- 'j' => [
- ],
- 'k' => [
- ],
- 'l' => [
- '^l$', 'directory', 'directory',
- '^ll$', 'directory', 'directory',
- '^ll/(\d+)', 'directory $1', 'directory',
- ],
- 'm' => [
- ],
- 'n' => [
- '^news', 'type news', 'type',
- ],
- 'o' => [
- ],
- 'p' => [
- ],
- 'q' => [
- '^q', 'bye', 'bye',
- ],
- 'r' => [
- '^r$', 'read', 'read',
- '^rcmd/(\S+)', 'rcmd $1', 'rcmd',
- ],
+ 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 ....
+
+
+
+
+
+
+ show/files bulletins
+ opdx390 21381 29-Nov-1999 1621Z opdx390.1 1670 29-Nov-1999 1621Z
+ opdx390.2 2193 29-Nov-1999 1621Z opdx391 25045 29-Nov-1999 1621Z
+ opdx392 35969 29-Nov-1999 1621Z opdx393 15023 29-Nov-1999 1621Z
+ opdx394 33429 29-Nov-1999 1621Z opdx394.1 3116 29-Nov-1999 1621Z
+ opdx395 24319 29-Nov-1999 1621Z opdx396 32647 29-Nov-1999 1621Z
+ opdx396.1 5537 29-Nov-1999 1621Z opdx396.2 6242 29-Nov-1999 1621Z
+ opdx397 18433 29-Nov-1999 1621Z opdx398 19961 29-Nov-1999 1621Z
+ opdx399 17719 29-Nov-1999 1621Z opdx400 19600 29-Nov-1999 1621Z
+ opdx401 27738 29-Nov-1999 1621Z opdx402 18698 29-Nov-1999 1621Z
+ opdx403 24994 29-Nov-1999 1621Z opdx404 15685 29-Nov-1999 1621Z
+ opdx405 13984 29-Nov-1999 1621Z opdx405.1 4166 29-Nov-1999 1621Z
+ opdx406 28934 29-Nov-1999 1621Z opdx407 24153 29-Nov-1999 1621Z
+ opdx408 15081 29-Nov-1999 1621Z opdx409 23234 29-Nov-1999 1621Z
+ Press Enter to continue, A to abort (16 lines) >
+
+
+
+
+ You can now read any file in this directory using the type command,
+ like this ....
+
+
+
+ type bulletins/opdx391
+ Ohio/Penn DX Bulletin No. 391
+ The Ohio/Penn Dx PacketCluster
+ DX Bulletin No. 391
+ BID: $OPDX.391
+ January 11, 1999
+ Editor Tedd Mirgliotta, KB8NW
+ Provided by BARF-80 BBS Cleveland, Ohio
+ Online at 440-237-8208 28.8k-1200 Baud 8/N/1 (New Area Code!)
+ Thanks to the Northern Ohio Amateur Radio Society, Northern Ohio DX
+ Association, Ohio/Penn PacketCluster Network, K1XN & Golist, WB2RAJ/WB2YQH
+ & The 59(9) DXReport, W3UR & The Daily DX, K3TEJ, KN4UG, W4DC, NC6J, N6HR,
+ Press Enter to continue, A to abort (508 lines) >
+
+
+
+
+ The page length will of course depend on what you have it set to!
+
+
+ 1\b11\b1.\b.4\b4.\b. T\bTh\bhe\be A\bAl\bli\bia\bas\bse\bes\bs f\bfi\bil\ble\be
+
+ You will find a file in /spider/cmd/ called Aliases. First, copy this
+ file to /spider/local_cmd/Aliases and edit this file. You will see
+ something like this ...
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ #!/usr/bin/perl
+
+ # provide some standard aliases for commands for terminally
+ # helpless ak1a user (helpless in the sense that they never
+ # read nor understand help files)
+
+ # This file is automagically reloaded if its modification time is
+ # later than the one stored in CmdAlias.pm
+
+ # PLEASE make this file consistant with reality! (the patterns MUST
+ # match the filenames!)
+
+ # Don't alter this file, copy it into the local_cmd tree and modify it.
+ # This file will be replaced everytime I issue a new release.
+
+ # You only need to put aliases in here for commands that don't work as
+ # you desire naturally, e.g sh/dx on its own just works as you expect
+ # so you need not add it as an alias.
+
+
+
+ package CmdAlias;
+
+ %alias = (
+ '?' => [
+ '^\?', 'apropos', 'apropos',
+ ],
+ 'a' => [
+ '^ann.*/full', 'announce full', 'announce',
+ '^ann.*/sysop', 'announce sysop', 'announce',
+ '^ann.*/(.*)$', 'announce $1', 'announce',
+ ],
+ 'b' => [
+ ],
+ 'c' => [
+ ],
+ 'd' => [
+ '^del', 'kill', 'kill',
+ '^del\w*/fu', 'kill full', 'kill',
+ '^di\w*/a\w*', 'directory all', 'directory',
+ '^di\w*/b\w*', 'directory bulletins', 'directory',
+ '^di\w*/n\w*', 'directory new', 'directory',
+ '^di\w*/o\w*', 'directory own', 'directory',
+ '^di\w*/s\w*', 'directory subject', 'directory',
+ '^di\w*/t\w*', 'directory to', 'directory',
+ '^di\w*/f\w*', 'directory from', 'directory',
+ '^di\w*/(\d+)', 'directory $1', 'directory',
+ ],
+ 'e' => [
+ ],
+ 'f' => [
+ ],
+ 'g' => [
+ ],
+ 'h' => [
+ ],
+ 'i' => [
+ ],
+ 'j' => [
+ ],
+ 'k' => [
+ ],
+ 'l' => [
+ '^l$', 'directory', 'directory',
+ '^ll$', 'directory', 'directory',
+ '^ll/(\d+)', 'directory $1', 'directory',
+ ],
+ 'm' => [
+ ],
+ 'n' => [
+ '^news', 'type news', 'type',
+ ],
+ 'o' => [
+ ],
+ 'p' => [
+ ],
+ 'q' => [
+ '^q', 'bye', 'bye',
+ ],
+ 'r' => [
+ '^r$', 'read', 'read',
+ '^rcmd/(\S+)', 'rcmd $1', 'rcmd',
+ ],