mirror of
git://scm.dxcluster.org/scm/spider
synced 2024-09-21 07:47:10 +00:00
Various additions and changes to documentation
This commit is contained in:
parent
8945b9430c
commit
b2478484ac
2
Changes
2
Changes
@ -1,3 +1,5 @@
|
|||||||
|
03Feb01=======================================================================
|
||||||
|
1. Changes and additions to the manual and added a help file for sh/log (g0vgs)
|
||||||
13Jan01=======================================================================
|
13Jan01=======================================================================
|
||||||
1. Documentation alterations to match new commands etc (g0vgs)
|
1. Documentation alterations to match new commands etc (g0vgs)
|
||||||
08Jan01=======================================================================
|
08Jan01=======================================================================
|
||||||
|
@ -1277,6 +1277,11 @@ all the categories will be listed.
|
|||||||
|
|
||||||
=== 9^SHOW/LOCKOUT^Show the list of locked out or excluded callsigns
|
=== 9^SHOW/LOCKOUT^Show the list of locked out or excluded callsigns
|
||||||
|
|
||||||
|
=== 8^SHOW/LOG [<callsign>]^Show excerpts from the system log
|
||||||
|
This command outputs a short section of the system log. On its own
|
||||||
|
it will output a general logfile. With the optional callsign it will
|
||||||
|
show output from the log associated with that callsign.
|
||||||
|
|
||||||
=== 0^SHOW/MOON [<prefix>|<callsign>]^Show Moon rise and set times
|
=== 0^SHOW/MOON [<prefix>|<callsign>]^Show Moon rise and set times
|
||||||
Show the Moon rise and set times for a (list of) prefixes or callsigns,
|
Show the Moon rise and set times for a (list of) prefixes or callsigns,
|
||||||
together with the azimuth and elevation of the sun currently at those
|
together with the azimuth and elevation of the sun currently at those
|
||||||
|
@ -2,7 +2,7 @@
|
|||||||
<HTML>
|
<HTML>
|
||||||
<HEAD>
|
<HEAD>
|
||||||
<META NAME="GENERATOR" CONTENT="SGML-Tools 1.0.9">
|
<META NAME="GENERATOR" CONTENT="SGML-Tools 1.0.9">
|
||||||
<TITLE>The DXSpider Installation and Administration Manual : Information, files and useful programs</TITLE>
|
<TITLE>The DXSpider Installation and Administration Manual : Databases</TITLE>
|
||||||
<LINK HREF="adminmanual-11.html" REL=next>
|
<LINK HREF="adminmanual-11.html" REL=next>
|
||||||
<LINK HREF="adminmanual-9.html" REL=previous>
|
<LINK HREF="adminmanual-9.html" REL=previous>
|
||||||
<LINK HREF="adminmanual.html#toc10" REL=contents>
|
<LINK HREF="adminmanual.html#toc10" REL=contents>
|
||||||
@ -13,323 +13,129 @@
|
|||||||
<A HREF="adminmanual-9.html">Previous</A>
|
<A HREF="adminmanual-9.html">Previous</A>
|
||||||
<A HREF="adminmanual.html#toc10">Contents</A>
|
<A HREF="adminmanual.html#toc10">Contents</A>
|
||||||
<HR>
|
<HR>
|
||||||
<H2><A NAME="s10">10. Information, files and useful programs</A></H2>
|
<H2><A NAME="s10">10. Databases</A></H2>
|
||||||
|
|
||||||
<H2><A NAME="ss10.1">10.1 MOTD</A>
|
<P>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.
|
||||||
|
<P>
|
||||||
|
<H2><A NAME="ss10.1">10.1 Creating databases</A>
|
||||||
</H2>
|
</H2>
|
||||||
|
|
||||||
<P>One of the more important things a cluster sysop needs to do is to get
|
<P>Creating a database could not be more simple. All the commands are
|
||||||
information to his users. The simplest way to do this is to have a banner
|
sent from the cluster prompt as the <EM>sysop</EM> user.
|
||||||
that is sent to the user on login. This is know as a "message of the day"
|
<P>To create a database you use the command <EM>dbcreate</EM>. It can
|
||||||
or "motd". To set this up, simply create a file in /spider/data called motd
|
be used in 3 different ways like so ..
|
||||||
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.
|
|
||||||
<P>
|
<P>
|
||||||
<H2><A NAME="ss10.2">10.2 Downtime message</A>
|
<BLOCKQUOTE><CODE>
|
||||||
|
<PRE>
|
||||||
|
dbcreate <name>
|
||||||
|
</PRE>
|
||||||
|
</CODE></BLOCKQUOTE>
|
||||||
|
<P>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.
|
||||||
|
<P>
|
||||||
|
<BLOCKQUOTE><CODE>
|
||||||
|
<PRE>
|
||||||
|
dbcreate <name> chain <name> [<name>...]
|
||||||
|
</PRE>
|
||||||
|
</CODE></BLOCKQUOTE>
|
||||||
|
<P>This creates a chained database entry. The first database will be
|
||||||
|
scanned, then the second, the third etc...
|
||||||
|
<P>
|
||||||
|
<BLOCKQUOTE><CODE>
|
||||||
|
<PRE>
|
||||||
|
dbcreate <name> remote <name>
|
||||||
|
</PRE>
|
||||||
|
</CODE></BLOCKQUOTE>
|
||||||
|
<P>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...
|
||||||
|
<P>
|
||||||
|
<BLOCKQUOTE><CODE>
|
||||||
|
<PRE>
|
||||||
|
dbcreate buckmaster remote gb7dxc
|
||||||
|
</PRE>
|
||||||
|
</CODE></BLOCKQUOTE>
|
||||||
|
<P>Remote databases cannot be chained, however, the last database in a
|
||||||
|
chain can be a remote database.
|
||||||
|
<P>
|
||||||
|
<H2><A NAME="ss10.2">10.2 Importing databases</A>
|
||||||
</H2>
|
</H2>
|
||||||
|
|
||||||
<P>If for any reason the cluster is down, maybe for upgrade or maintenance but
|
<P>The only databases that Spider can currently import are the standard
|
||||||
the machine is still running, a message can be sent to the user advising them
|
AK1A databases such as OBLAST or the DB0SDX qsl and address database.
|
||||||
of the fact. This message lives in the /spider/data directory and is called
|
This will be added to with time.
|
||||||
"offline". Simply create the file and edit it to say whatever you wish.
|
<P>To import such a database, first put the file somewhere useful like /tmp
|
||||||
This file will be sent to a user attempting to log into the cluster when
|
and then issue the following command ...
|
||||||
DXSpider is not actually running.
|
|
||||||
<P>
|
<P>
|
||||||
<H2><A NAME="ss10.3">10.3 Other text messages</A>
|
<BLOCKQUOTE><CODE>
|
||||||
|
<PRE>
|
||||||
|
dbimport oblast /tmp/OBLAST.FUL
|
||||||
|
</PRE>
|
||||||
|
</CODE></BLOCKQUOTE>
|
||||||
|
<P>This will update the existing local oblast database or create it if
|
||||||
|
it does not exist.
|
||||||
|
<P>
|
||||||
|
<H2><A NAME="ss10.3">10.3 Checking available databases</A>
|
||||||
</H2>
|
</H2>
|
||||||
|
|
||||||
<P>You can set other text messages to be read by the user if they input the file
|
<P>Once a database is created, you will want to check that it has been
|
||||||
name. This could be for news items or maybe information for new users.
|
added. To do this use the <EM>dbavail</EM> command. This will
|
||||||
To set this up, make a directory under /spider called <EM>packclus</EM>.
|
output the available databases. For example ...
|
||||||
Under this directory you can create files called <EM>news</EM> or <EM>newuser</EM>
|
|
||||||
for example. In fact you can create files with any names you like. These can
|
|
||||||
be listed by the user with the command ....
|
|
||||||
<P>
|
<P>
|
||||||
<BLOCKQUOTE><CODE>
|
<BLOCKQUOTE><CODE>
|
||||||
<PRE>
|
<PRE>
|
||||||
show/files
|
dbavail
|
||||||
</PRE>
|
DB Name Location Chain
|
||||||
</CODE></BLOCKQUOTE>
|
qsl Local
|
||||||
<P>They can be read by the user by typing the command ....
|
buck GB7ADX
|
||||||
<P>
|
hftest GB7DXM
|
||||||
<BLOCKQUOTE><CODE>
|
G0VGS de GB7MBC 3-Feb-2001 1925Z >
|
||||||
<PRE>
|
|
||||||
type news
|
|
||||||
</PRE>
|
|
||||||
</CODE></BLOCKQUOTE>
|
|
||||||
<P>If the file they want to read is called <EM>news</EM>. You could also set
|
|
||||||
an alias for this in the Alias file to allow them just to type <EM>news</EM>
|
|
||||||
<P>
|
|
||||||
<P>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
|
|
||||||
<EM>bulletins</EM>. Now copy any OPDX or similar bulletins into it. These
|
|
||||||
can be listed by the user in the same way as above using the <EM>show/files</EM>
|
|
||||||
command with an extension for the bulletins directory you have just created,
|
|
||||||
like this ....
|
|
||||||
<P>
|
|
||||||
<BLOCKQUOTE><CODE>
|
|
||||||
<PRE>
|
|
||||||
show/files bulletins
|
|
||||||
</PRE>
|
</PRE>
|
||||||
</CODE></BLOCKQUOTE>
|
</CODE></BLOCKQUOTE>
|
||||||
<P>
|
<P>
|
||||||
<P>An example would look like this ....
|
<H2><A NAME="ss10.4">10.4 Looking up databases</A>
|
||||||
<P>
|
|
||||||
<BLOCKQUOTE><CODE>
|
|
||||||
<PRE>
|
|
||||||
sh/files
|
|
||||||
bulletins DIR 20-Dec-1999 1715Z news 1602 14-Dec-1999 1330Z
|
|
||||||
</PRE>
|
|
||||||
</CODE></BLOCKQUOTE>
|
|
||||||
<P>You can see that in the files area (basically the packclus directory) there is a
|
|
||||||
file called <EM>news</EM> and a directory called <EM>bulletins</EM>. You can
|
|
||||||
also see that dates they were created. In the case of the file <EM>news</EM>,
|
|
||||||
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
|
|
||||||
<EM>news</EM> you would simply issue the command ....
|
|
||||||
<P>
|
|
||||||
<BLOCKQUOTE><CODE>
|
|
||||||
<PRE>
|
|
||||||
type news
|
|
||||||
</PRE>
|
|
||||||
</CODE></BLOCKQUOTE>
|
|
||||||
<P>To look what is in the bulletins directory you issue the command ....
|
|
||||||
<P>
|
|
||||||
<BLOCKQUOTE><CODE>
|
|
||||||
<PRE>
|
|
||||||
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) >
|
|
||||||
</PRE>
|
|
||||||
</CODE></BLOCKQUOTE>
|
|
||||||
<P>You can now read any file in this directory using the type command, like this ....
|
|
||||||
<P>
|
|
||||||
<BLOCKQUOTE><CODE>
|
|
||||||
<PRE>
|
|
||||||
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) >
|
|
||||||
</PRE>
|
|
||||||
</CODE></BLOCKQUOTE>
|
|
||||||
<P>The page length will of course depend on what you have it set to!
|
|
||||||
<P>
|
|
||||||
<H2><A NAME="ss10.4">10.4 The Aliases file</A>
|
|
||||||
</H2>
|
</H2>
|
||||||
|
|
||||||
<P>You will find a file in /spider/cmd/ called Aliases. First, copy this file to
|
<P>To look for information in a defined database, simply use the <EM>dbshow</EM>
|
||||||
/spider/local_cmd/Aliases and edit this file. You will see something like this ...
|
command, for example ...
|
||||||
<P>
|
<P>
|
||||||
<BLOCKQUOTE><CODE>
|
<BLOCKQUOTE><CODE>
|
||||||
<PRE>
|
<PRE>
|
||||||
|
dbshow buckmaster G0YLM
|
||||||
#!/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',
|
|
||||||
],
|
|
||||||
's' => [
|
|
||||||
'^s/p$', 'send', 'send',
|
|
||||||
'^sb$', 'send noprivate', 'send',
|
|
||||||
'^set/home$', 'set/homenode', 'set/homenode',
|
|
||||||
'^set/nobe', 'unset/beep', 'unset/beep',
|
|
||||||
'^set/nohe', 'unset/here', 'unset/here',
|
|
||||||
'^set/noan', 'unset/announce', 'unset/announce',
|
|
||||||
'^set/nodx', 'unset/dx', 'unset/dx',
|
|
||||||
'^set/nota', 'unset/talk', 'unset/talk',
|
|
||||||
'^set/noww', 'unset/wwv', 'unset/wwv',
|
|
||||||
'^set/nowx', 'unset/wx', 'unset/wx',
|
|
||||||
'^sh$', 'show', 'show',
|
|
||||||
'^sh\w*/buck', 'dbshow buck', 'dbshow',
|
|
||||||
'^sh\w*/bu', 'show/files bulletins', 'show/files',
|
|
||||||
'^sh\w*/c/n', 'show/configuration nodes', 'show/configuration',
|
|
||||||
'^sh\w*/c$', 'show/configuration', 'show/configuration',
|
|
||||||
'^sh\w*/com', 'dbavail', 'dbavail',
|
|
||||||
'^sh\w*/dx/(\d+)-(\d+)', 'show/dx $1-$2', 'show/dx',
|
|
||||||
'^sh\w*/dx/(\d+)', 'show/dx $1', 'show/dx',
|
|
||||||
'^sh\w*/dx/d(\d+)', 'show/dx from $1', 'show/dx',
|
|
||||||
'^sh\w*/email', 'dbshow email', 'dbshow',
|
|
||||||
'^sh\w*/hftest', 'dbshow hftest', 'dbshow',
|
|
||||||
'^sh\w*/vhftest', 'dbshow vhftest', 'dbshow',
|
|
||||||
'^sh\w*/qsl', 'dbshow qsl', 'dbshow',
|
|
||||||
'^sh\w*/tnc', 'who', 'who',
|
|
||||||
'^sh\w*/up', 'show/cluster', 'show/cluster',
|
|
||||||
'^sh\w*/w\w*/(\d+)-(\d+)', 'show/wwv $1-$2', 'show/wwv',
|
|
||||||
'^sh\w*/w\w*/(\d+)', 'show/wwv $1', 'show/wwv',
|
|
||||||
'^sp$', 'send', 'send',
|
|
||||||
|
|
||||||
],
|
|
||||||
't' => [
|
|
||||||
'^ta$', 'talk', 'talk',
|
|
||||||
'^t$', 'talk', 'talk',
|
|
||||||
],
|
|
||||||
'u' => [
|
|
||||||
],
|
|
||||||
'v' => [
|
|
||||||
],
|
|
||||||
'w' => [
|
|
||||||
'^wx/full', 'wx full', 'wx',
|
|
||||||
'^wx/sysop', 'wx sysop', 'wx',
|
|
||||||
],
|
|
||||||
'x' => [
|
|
||||||
],
|
|
||||||
'y' => [
|
|
||||||
],
|
|
||||||
'z' => [
|
|
||||||
],
|
|
||||||
)
|
|
||||||
</PRE>
|
</PRE>
|
||||||
</CODE></BLOCKQUOTE>
|
</CODE></BLOCKQUOTE>
|
||||||
<P>You can create aliases for commands at will. Beware though, these may not
|
<P>will show the information for the callsign G0YLM from the buckmaster
|
||||||
always turn out as you think. Care is needed and you need to test the
|
database if it exists. To make things more standard for the users
|
||||||
results once you have set an alias.
|
you can add an entry in the Aliases file so that it looks like a standard
|
||||||
|
<EM>show</EM> command like this ...
|
||||||
<P>
|
<P>
|
||||||
<H2><A NAME="ss10.5">10.5 Console.pl</A>
|
<BLOCKQUOTE><CODE>
|
||||||
|
<PRE>
|
||||||
|
'^sh\w*/buc', 'dbshow buckmaster', 'dbshow',
|
||||||
|
</PRE>
|
||||||
|
</CODE></BLOCKQUOTE>
|
||||||
|
<P>Now you can simply use show/buckmaster or an abreviation.
|
||||||
|
<P>
|
||||||
|
<H2><A NAME="ss10.5">10.5 Removing databases</A>
|
||||||
</H2>
|
</H2>
|
||||||
|
|
||||||
<P>In later versions of Spider a simple console program is provided for the sysop.
|
<P>To delete an existing database you use the <EM>dbremove</EM> command.
|
||||||
This has a type ahead buffer with line editing facilities and colour for spots,
|
For example ...
|
||||||
announces etc. To use this program, simply use console.pl instead of client.pl.
|
|
||||||
<P>
|
|
||||||
<P>To edit the colours, copy /spider/perl/Console.pl to /spider/local and edit the
|
|
||||||
file with your favourite editor.
|
|
||||||
<P>
|
|
||||||
<H2><A NAME="ss10.6">10.6 Updating kepler data</A>
|
|
||||||
</H2>
|
|
||||||
|
|
||||||
<P>Spider has a powerful and flexible show/satellite command. In order for
|
|
||||||
this to be accurate, the kepler data has to be updated regularly. In
|
|
||||||
general, this data is available as an email or via cluster mail.
|
|
||||||
Updating it is simple. First you need to export the mail message as a
|
|
||||||
file. You do this with the <EM>export</EM> command from the cluster prompt
|
|
||||||
as the sysop. For example ...
|
|
||||||
<P>
|
<P>
|
||||||
<BLOCKQUOTE><CODE>
|
<BLOCKQUOTE><CODE>
|
||||||
<PRE>
|
<PRE>
|
||||||
export 5467 /spider/perl/keps.in
|
dbremove oblast
|
||||||
</PRE>
|
</PRE>
|
||||||
</CODE></BLOCKQUOTE>
|
</CODE></BLOCKQUOTE>
|
||||||
<P>would export message number 5467 as a file called keps.in in the
|
<P>would remove the oblast database and its associated datafile from the
|
||||||
/spider/perl directory.
|
system. There are no warnings or recovery possible from this command.
|
||||||
<P>Now login to a VT as sysop and cd /spider/perl. There is a command in
|
If you remove a database it ceases to exist and would have to be created
|
||||||
the perl directory called <EM>convkeps.pl</EM>. All we need to do now is
|
from scratch if you still required it.
|
||||||
convert the file like so ...
|
|
||||||
<P>
|
|
||||||
<BLOCKQUOTE><CODE>
|
|
||||||
<PRE>
|
|
||||||
./convkeps.pl keps.in
|
|
||||||
</PRE>
|
|
||||||
</CODE></BLOCKQUOTE>
|
|
||||||
<P>Now go back to the cluster and issue the command ...
|
|
||||||
<P>
|
|
||||||
<BLOCKQUOTE><CODE>
|
|
||||||
<PRE>
|
|
||||||
load/keps
|
|
||||||
</PRE>
|
|
||||||
</CODE></BLOCKQUOTE>
|
|
||||||
<P>That is it! the kepler data has been updated.
|
|
||||||
<P>
|
|
||||||
<P>
|
<P>
|
||||||
<HR>
|
<HR>
|
||||||
<A HREF="adminmanual-11.html">Next</A>
|
<A HREF="adminmanual-11.html">Next</A>
|
||||||
|
@ -2,7 +2,7 @@
|
|||||||
<HTML>
|
<HTML>
|
||||||
<HEAD>
|
<HEAD>
|
||||||
<META NAME="GENERATOR" CONTENT="SGML-Tools 1.0.9">
|
<META NAME="GENERATOR" CONTENT="SGML-Tools 1.0.9">
|
||||||
<TITLE>The DXSpider Installation and Administration Manual : CVS</TITLE>
|
<TITLE>The DXSpider Installation and Administration Manual : Information, files and useful programs</TITLE>
|
||||||
<LINK HREF="adminmanual-12.html" REL=next>
|
<LINK HREF="adminmanual-12.html" REL=next>
|
||||||
<LINK HREF="adminmanual-10.html" REL=previous>
|
<LINK HREF="adminmanual-10.html" REL=previous>
|
||||||
<LINK HREF="adminmanual.html#toc11" REL=contents>
|
<LINK HREF="adminmanual.html#toc11" REL=contents>
|
||||||
@ -13,99 +13,323 @@
|
|||||||
<A HREF="adminmanual-10.html">Previous</A>
|
<A HREF="adminmanual-10.html">Previous</A>
|
||||||
<A HREF="adminmanual.html#toc11">Contents</A>
|
<A HREF="adminmanual.html#toc11">Contents</A>
|
||||||
<HR>
|
<HR>
|
||||||
<H2><A NAME="s11">11. CVS</A></H2>
|
<H2><A NAME="s11">11. Information, files and useful programs</A></H2>
|
||||||
|
|
||||||
<P>CVS stands for "Concurrent Versions System" and the CVS for DXSpider is held
|
<H2><A NAME="ss11.1">11.1 MOTD</A>
|
||||||
at
|
</H2>
|
||||||
<A HREF="http://www.sourceforge.net">Sourceforge</A>. This means
|
|
||||||
that it is possible to update your DXSpider installation to the latest
|
<P>One of the more important things a cluster sysop needs to do is to get
|
||||||
sources by using a few simple commands.
|
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.
|
||||||
<P>
|
<P>
|
||||||
<P>THIS IS NOT FOR THE FAINT HEARTED!!! ONLY DO THIS IF YOU HAVE A TEST
|
<H2><A NAME="ss11.2">11.2 Downtime message</A>
|
||||||
INSTALLATION OR ARE WILLING TO HAVE YOUR CLUSTER CRASH ON YOU!!!
|
</H2>
|
||||||
THIS MUST BE CONSIDERED AT LEAST BETA TESTING AND MAYBE EVEN ALPHA!!
|
|
||||||
YOU HAVE BEEN WARNED!!!
|
<P>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.
|
||||||
<P>
|
<P>
|
||||||
<P>DID I MENTION..... ONLY DO THIS IF YOU ARE WILLING TO ACCEPT THE
|
<H2><A NAME="ss11.3">11.3 Other text messages</A>
|
||||||
CONSEQUENCES!!!
|
</H2>
|
||||||
<P>
|
|
||||||
<P>I am of course assuming that you have a machine with both DXSpider and
|
<P>You can set other text messages to be read by the user if they input the file
|
||||||
Internet access running.
|
name. This could be for news items or maybe information for new users.
|
||||||
<P>
|
To set this up, make a directory under /spider called <EM>packclus</EM>.
|
||||||
<P>BEFORE YOU EVEN CONSIDER STARTING WITH THIS MAKE A BACKUP OF YOUR
|
Under this directory you can create files called <EM>news</EM> or <EM>newuser</EM>
|
||||||
ENTIRE SPIDER TREE!!
|
for example. In fact you can create files with any names you like. These can
|
||||||
<P>
|
be listed by the user with the command ....
|
||||||
<P>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 ...
|
|
||||||
<P>
|
|
||||||
<P>First login as the user <EM>sysop</EM>. Next you need to connect to the CVS
|
|
||||||
repository. You do this with the command below ...
|
|
||||||
<P>
|
|
||||||
<PRE>
|
|
||||||
cvs -d:pserver:anonymous@cvs.DXSpider.sourceforge.net:/cvsroot/dxspider login
|
|
||||||
</PRE>
|
|
||||||
<P>You will get a password prompt. Simply hit return here and your machine should
|
|
||||||
return to a normal linux prompt.
|
|
||||||
<P>
|
|
||||||
<P>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.
|
|
||||||
Either way you will want to change directory to a new place, if you want to
|
|
||||||
update an existing installation then I suggest /tmp, otherwise choose a
|
|
||||||
suitable place according to the normal installation instructions.
|
|
||||||
<P>
|
|
||||||
<P>The next step will create a brand new 'spider' directory in your current
|
|
||||||
directory.
|
|
||||||
<P>
|
|
||||||
<PRE>
|
|
||||||
cvs -z3 -d:pserver:anonymous@cvs.DXSpider.sourceforge.net:/cvsroot/dxspider co spider
|
|
||||||
</PRE>
|
|
||||||
<P>This command is all on one line.
|
|
||||||
<P>
|
|
||||||
<P>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.
|
|
||||||
<P>
|
|
||||||
<P>Now if you are doing a new installation, that's it. Carry on as if you have
|
|
||||||
just downloaded and untarred the lastest tarball.
|
|
||||||
<P>
|
|
||||||
<P>If you want to upgrade your current installation then do this ...
|
|
||||||
<P>
|
<P>
|
||||||
<BLOCKQUOTE><CODE>
|
<BLOCKQUOTE><CODE>
|
||||||
<PRE>
|
<PRE>
|
||||||
tar cvfz /tmp/s.tgz spider
|
show/files
|
||||||
cd /
|
|
||||||
tar xvfzp /tmp/s.tgz
|
|
||||||
</PRE>
|
</PRE>
|
||||||
</CODE></BLOCKQUOTE>
|
</CODE></BLOCKQUOTE>
|
||||||
<P>This is assuming you downloaded to the /tmp directory of course.
|
<P>They can be read by the user by typing the command ....
|
||||||
<P>
|
|
||||||
<P>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?????
|
|
||||||
<P>Remember to recompile the C client (cd /spider/src; make)
|
|
||||||
<P>
|
|
||||||
<P>At this point the files have been upgraded. You can (usually) restrt 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!
|
|
||||||
<P>
|
|
||||||
<P>Now the magic part! From now on when you want to update, simply connect to the
|
|
||||||
Internet and then, as the user <EM>sysop</EM> ...
|
|
||||||
<P>
|
<P>
|
||||||
<BLOCKQUOTE><CODE>
|
<BLOCKQUOTE><CODE>
|
||||||
<PRE>
|
<PRE>
|
||||||
cd /spider
|
type news
|
||||||
cvs -z3 update -d
|
|
||||||
</PRE>
|
</PRE>
|
||||||
</CODE></BLOCKQUOTE>
|
</CODE></BLOCKQUOTE>
|
||||||
<P>and your files will be updated. As above, remember to recompile the "C" client
|
<P>If the file they want to read is called <EM>news</EM>. You could also set
|
||||||
if it has been updated (CVS will tell you) and restart if any of the perl scripts
|
an alias for this in the Alias file to allow them just to type <EM>news</EM>
|
||||||
have been altered or added, again, CVS will tell you.
|
<P>
|
||||||
|
<P>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
|
||||||
|
<EM>bulletins</EM>. Now copy any OPDX or similar bulletins into it. These
|
||||||
|
can be listed by the user in the same way as above using the <EM>show/files</EM>
|
||||||
|
command with an extension for the bulletins directory you have just created,
|
||||||
|
like this ....
|
||||||
|
<P>
|
||||||
|
<BLOCKQUOTE><CODE>
|
||||||
|
<PRE>
|
||||||
|
show/files bulletins
|
||||||
|
</PRE>
|
||||||
|
</CODE></BLOCKQUOTE>
|
||||||
|
<P>
|
||||||
|
<P>An example would look like this ....
|
||||||
|
<P>
|
||||||
|
<BLOCKQUOTE><CODE>
|
||||||
|
<PRE>
|
||||||
|
sh/files
|
||||||
|
bulletins DIR 20-Dec-1999 1715Z news 1602 14-Dec-1999 1330Z
|
||||||
|
</PRE>
|
||||||
|
</CODE></BLOCKQUOTE>
|
||||||
|
<P>You can see that in the files area (basically the packclus directory) there is a
|
||||||
|
file called <EM>news</EM> and a directory called <EM>bulletins</EM>. You can
|
||||||
|
also see that dates they were created. In the case of the file <EM>news</EM>,
|
||||||
|
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
|
||||||
|
<EM>news</EM> you would simply issue the command ....
|
||||||
|
<P>
|
||||||
|
<BLOCKQUOTE><CODE>
|
||||||
|
<PRE>
|
||||||
|
type news
|
||||||
|
</PRE>
|
||||||
|
</CODE></BLOCKQUOTE>
|
||||||
|
<P>To look what is in the bulletins directory you issue the command ....
|
||||||
|
<P>
|
||||||
|
<BLOCKQUOTE><CODE>
|
||||||
|
<PRE>
|
||||||
|
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) >
|
||||||
|
</PRE>
|
||||||
|
</CODE></BLOCKQUOTE>
|
||||||
|
<P>You can now read any file in this directory using the type command, like this ....
|
||||||
|
<P>
|
||||||
|
<BLOCKQUOTE><CODE>
|
||||||
|
<PRE>
|
||||||
|
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) >
|
||||||
|
</PRE>
|
||||||
|
</CODE></BLOCKQUOTE>
|
||||||
|
<P>The page length will of course depend on what you have it set to!
|
||||||
|
<P>
|
||||||
|
<H2><A NAME="ss11.4">11.4 The Aliases file</A>
|
||||||
|
</H2>
|
||||||
|
|
||||||
|
<P>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 ...
|
||||||
|
<P>
|
||||||
|
<BLOCKQUOTE><CODE>
|
||||||
|
<PRE>
|
||||||
|
|
||||||
|
#!/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',
|
||||||
|
],
|
||||||
|
's' => [
|
||||||
|
'^s/p$', 'send', 'send',
|
||||||
|
'^sb$', 'send noprivate', 'send',
|
||||||
|
'^set/home$', 'set/homenode', 'set/homenode',
|
||||||
|
'^set/nobe', 'unset/beep', 'unset/beep',
|
||||||
|
'^set/nohe', 'unset/here', 'unset/here',
|
||||||
|
'^set/noan', 'unset/announce', 'unset/announce',
|
||||||
|
'^set/nodx', 'unset/dx', 'unset/dx',
|
||||||
|
'^set/nota', 'unset/talk', 'unset/talk',
|
||||||
|
'^set/noww', 'unset/wwv', 'unset/wwv',
|
||||||
|
'^set/nowx', 'unset/wx', 'unset/wx',
|
||||||
|
'^sh$', 'show', 'show',
|
||||||
|
'^sh\w*/buck', 'dbshow buck', 'dbshow',
|
||||||
|
'^sh\w*/bu', 'show/files bulletins', 'show/files',
|
||||||
|
'^sh\w*/c/n', 'show/configuration nodes', 'show/configuration',
|
||||||
|
'^sh\w*/c$', 'show/configuration', 'show/configuration',
|
||||||
|
'^sh\w*/com', 'dbavail', 'dbavail',
|
||||||
|
'^sh\w*/dx/(\d+)-(\d+)', 'show/dx $1-$2', 'show/dx',
|
||||||
|
'^sh\w*/dx/(\d+)', 'show/dx $1', 'show/dx',
|
||||||
|
'^sh\w*/dx/d(\d+)', 'show/dx from $1', 'show/dx',
|
||||||
|
'^sh\w*/email', 'dbshow email', 'dbshow',
|
||||||
|
'^sh\w*/hftest', 'dbshow hftest', 'dbshow',
|
||||||
|
'^sh\w*/vhftest', 'dbshow vhftest', 'dbshow',
|
||||||
|
'^sh\w*/qsl', 'dbshow qsl', 'dbshow',
|
||||||
|
'^sh\w*/tnc', 'who', 'who',
|
||||||
|
'^sh\w*/up', 'show/cluster', 'show/cluster',
|
||||||
|
'^sh\w*/w\w*/(\d+)-(\d+)', 'show/wwv $1-$2', 'show/wwv',
|
||||||
|
'^sh\w*/w\w*/(\d+)', 'show/wwv $1', 'show/wwv',
|
||||||
|
'^sp$', 'send', 'send',
|
||||||
|
|
||||||
|
],
|
||||||
|
't' => [
|
||||||
|
'^ta$', 'talk', 'talk',
|
||||||
|
'^t$', 'talk', 'talk',
|
||||||
|
],
|
||||||
|
'u' => [
|
||||||
|
],
|
||||||
|
'v' => [
|
||||||
|
],
|
||||||
|
'w' => [
|
||||||
|
'^wx/full', 'wx full', 'wx',
|
||||||
|
'^wx/sysop', 'wx sysop', 'wx',
|
||||||
|
],
|
||||||
|
'x' => [
|
||||||
|
],
|
||||||
|
'y' => [
|
||||||
|
],
|
||||||
|
'z' => [
|
||||||
|
],
|
||||||
|
)
|
||||||
|
</PRE>
|
||||||
|
</CODE></BLOCKQUOTE>
|
||||||
|
<P>You can create aliases for commands at will. Beware though, these may not
|
||||||
|
always turn out as you think. Care is needed and you need to test the
|
||||||
|
results once you have set an alias.
|
||||||
|
<P>
|
||||||
|
<H2><A NAME="ss11.5">11.5 Console.pl</A>
|
||||||
|
</H2>
|
||||||
|
|
||||||
|
<P>In later versions of Spider a simple console program is provided for the sysop.
|
||||||
|
This has a type ahead buffer with line editing facilities and colour for spots,
|
||||||
|
announces etc. To use this program, simply use console.pl instead of client.pl.
|
||||||
|
<P>
|
||||||
|
<P>To edit the colours, copy /spider/perl/Console.pl to /spider/local and edit the
|
||||||
|
file with your favourite editor.
|
||||||
|
<P>
|
||||||
|
<H2><A NAME="ss11.6">11.6 Updating kepler data</A>
|
||||||
|
</H2>
|
||||||
|
|
||||||
|
<P>Spider has a powerful and flexible show/satellite command. In order for
|
||||||
|
this to be accurate, the kepler data has to be updated regularly. In
|
||||||
|
general, this data is available as an email or via cluster mail.
|
||||||
|
Updating it is simple. First you need to export the mail message as a
|
||||||
|
file. You do this with the <EM>export</EM> command from the cluster prompt
|
||||||
|
as the sysop. For example ...
|
||||||
|
<P>
|
||||||
|
<BLOCKQUOTE><CODE>
|
||||||
|
<PRE>
|
||||||
|
export 5467 /spider/perl/keps.in
|
||||||
|
</PRE>
|
||||||
|
</CODE></BLOCKQUOTE>
|
||||||
|
<P>would export message number 5467 as a file called keps.in in the
|
||||||
|
/spider/perl directory.
|
||||||
|
<P>Now login to a VT as sysop and cd /spider/perl. There is a command in
|
||||||
|
the perl directory called <EM>convkeps.pl</EM>. All we need to do now is
|
||||||
|
convert the file like so ...
|
||||||
|
<P>
|
||||||
|
<BLOCKQUOTE><CODE>
|
||||||
|
<PRE>
|
||||||
|
./convkeps.pl keps.in
|
||||||
|
</PRE>
|
||||||
|
</CODE></BLOCKQUOTE>
|
||||||
|
<P>Now go back to the cluster and issue the command ...
|
||||||
|
<P>
|
||||||
|
<BLOCKQUOTE><CODE>
|
||||||
|
<PRE>
|
||||||
|
load/keps
|
||||||
|
</PRE>
|
||||||
|
</CODE></BLOCKQUOTE>
|
||||||
|
<P>That is it! the kepler data has been updated.
|
||||||
<P>
|
<P>
|
||||||
<P>You will find any changes documented in the /spider/Changes file.
|
|
||||||
<P>
|
<P>
|
||||||
<HR>
|
<HR>
|
||||||
<A HREF="adminmanual-12.html">Next</A>
|
<A HREF="adminmanual-12.html">Next</A>
|
||||||
|
File diff suppressed because it is too large
Load Diff
@ -15,7 +15,7 @@ Contents
|
|||||||
<HR>
|
<HR>
|
||||||
<H1>The DXSpider Installation and Administration Manual </H1>
|
<H1>The DXSpider Installation and Administration Manual </H1>
|
||||||
|
|
||||||
<H2>Ian Maude, G0VGS, (ianmaude@btinternet.com)</H2>Version 1.31 January 2001
|
<H2>Ian Maude, G0VGS, (ianmaude@btinternet.com)</H2>Version 1.32 February 2001
|
||||||
<P><HR>
|
<P><HR>
|
||||||
<EM>A reference for SysOps of the DXSpider DXCluster program.</EM>
|
<EM>A reference for SysOps of the DXSpider DXCluster program.</EM>
|
||||||
<HR>
|
<HR>
|
||||||
@ -97,159 +97,170 @@ Contents
|
|||||||
<LI><A HREF="adminmanual-9.html#ss9.8">9.8 BBS interface</A>
|
<LI><A HREF="adminmanual-9.html#ss9.8">9.8 BBS interface</A>
|
||||||
</UL>
|
</UL>
|
||||||
<P>
|
<P>
|
||||||
<H2><A NAME="toc10">10.</A> <A HREF="adminmanual-10.html">Information, files and useful programs</A></H2>
|
<H2><A NAME="toc10">10.</A> <A HREF="adminmanual-10.html">Databases</A></H2>
|
||||||
|
|
||||||
<UL>
|
<UL>
|
||||||
<LI><A HREF="adminmanual-10.html#ss10.1">10.1 MOTD</A>
|
<LI><A HREF="adminmanual-10.html#ss10.1">10.1 Creating databases</A>
|
||||||
<LI><A HREF="adminmanual-10.html#ss10.2">10.2 Downtime message</A>
|
<LI><A HREF="adminmanual-10.html#ss10.2">10.2 Importing databases</A>
|
||||||
<LI><A HREF="adminmanual-10.html#ss10.3">10.3 Other text messages</A>
|
<LI><A HREF="adminmanual-10.html#ss10.3">10.3 Checking available databases</A>
|
||||||
<LI><A HREF="adminmanual-10.html#ss10.4">10.4 The Aliases file</A>
|
<LI><A HREF="adminmanual-10.html#ss10.4">10.4 Looking up databases</A>
|
||||||
<LI><A HREF="adminmanual-10.html#ss10.5">10.5 Console.pl</A>
|
<LI><A HREF="adminmanual-10.html#ss10.5">10.5 Removing databases</A>
|
||||||
<LI><A HREF="adminmanual-10.html#ss10.6">10.6 Updating kepler data</A>
|
|
||||||
</UL>
|
</UL>
|
||||||
<P>
|
<P>
|
||||||
<H2><A NAME="toc11">11.</A> <A HREF="adminmanual-11.html">CVS</A></H2>
|
<H2><A NAME="toc11">11.</A> <A HREF="adminmanual-11.html">Information, files and useful programs</A></H2>
|
||||||
|
|
||||||
<P>
|
|
||||||
<H2><A NAME="toc12">12.</A> <A HREF="adminmanual-12.html">The DXSpider command set</A></H2>
|
|
||||||
|
|
||||||
<UL>
|
<UL>
|
||||||
<LI><A HREF="adminmanual-12.html#ss12.1">12.1 accept/announce (0)</A>
|
<LI><A HREF="adminmanual-11.html#ss11.1">11.1 MOTD</A>
|
||||||
<LI><A HREF="adminmanual-12.html#ss12.2">12.2 accept/announce (extended for sysops) (8)</A>
|
<LI><A HREF="adminmanual-11.html#ss11.2">11.2 Downtime message</A>
|
||||||
<LI><A HREF="adminmanual-12.html#ss12.3">12.3 accept/spots (0)</A>
|
<LI><A HREF="adminmanual-11.html#ss11.3">11.3 Other text messages</A>
|
||||||
<LI><A HREF="adminmanual-12.html#ss12.4">12.4 accept/spots (extended for sysops) (8)</A>
|
<LI><A HREF="adminmanual-11.html#ss11.4">11.4 The Aliases file</A>
|
||||||
<LI><A HREF="adminmanual-12.html#ss12.5">12.5 accept/wcy (0)</A>
|
<LI><A HREF="adminmanual-11.html#ss11.5">11.5 Console.pl</A>
|
||||||
<LI><A HREF="adminmanual-12.html#ss12.6">12.6 accept/wcy (extended for sysops) (8)</A>
|
<LI><A HREF="adminmanual-11.html#ss11.6">11.6 Updating kepler data</A>
|
||||||
<LI><A HREF="adminmanual-12.html#ss12.7">12.7 accept/wwv (0)</A>
|
</UL>
|
||||||
<LI><A HREF="adminmanual-12.html#ss12.8">12.8 accept/wwv (extended for sysops) (8)</A>
|
<P>
|
||||||
<LI><A HREF="adminmanual-12.html#ss12.9">12.9 announce (0)</A>
|
<H2><A NAME="toc12">12.</A> <A HREF="adminmanual-12.html">CVS</A></H2>
|
||||||
<LI><A HREF="adminmanual-12.html#ss12.10">12.10 announce full (0)</A>
|
|
||||||
<LI><A HREF="adminmanual-12.html#ss12.11">12.11 announce sysop (5)</A>
|
<P>
|
||||||
<LI><A HREF="adminmanual-12.html#ss12.12">12.12 apropos (0)</A>
|
<H2><A NAME="toc13">13.</A> <A HREF="adminmanual-13.html">The DXSpider command set</A></H2>
|
||||||
<LI><A HREF="adminmanual-12.html#ss12.13">12.13 bye (0)</A>
|
|
||||||
<LI><A HREF="adminmanual-12.html#ss12.14">12.14 catchup (5)</A>
|
<UL>
|
||||||
<LI><A HREF="adminmanual-12.html#ss12.15">12.15 clear/spots (0)</A>
|
<LI><A HREF="adminmanual-13.html#ss13.1">13.1 accept/announce (0)</A>
|
||||||
<LI><A HREF="adminmanual-12.html#ss12.16">12.16 connect (5) </A>
|
<LI><A HREF="adminmanual-13.html#ss13.2">13.2 accept/announce (extended for sysops) (8)</A>
|
||||||
<LI><A HREF="adminmanual-12.html#ss12.17">12.17 dbavail (0)</A>
|
<LI><A HREF="adminmanual-13.html#ss13.3">13.3 accept/spots (0)</A>
|
||||||
<LI><A HREF="adminmanual-12.html#ss12.18">12.18 dbcreate (9)</A>
|
<LI><A HREF="adminmanual-13.html#ss13.4">13.4 accept/spots (extended for sysops) (8)</A>
|
||||||
<LI><A HREF="adminmanual-12.html#ss12.19">12.19 dbimport (9)</A>
|
<LI><A HREF="adminmanual-13.html#ss13.5">13.5 accept/wcy (0)</A>
|
||||||
<LI><A HREF="adminmanual-12.html#ss12.20">12.20 dbremove (9)</A>
|
<LI><A HREF="adminmanual-13.html#ss13.6">13.6 accept/wcy (extended for sysops) (8)</A>
|
||||||
<LI><A HREF="adminmanual-12.html#ss12.21">12.21 dbshow (0)</A>
|
<LI><A HREF="adminmanual-13.html#ss13.7">13.7 accept/wwv (0)</A>
|
||||||
<LI><A HREF="adminmanual-12.html#ss12.22">12.22 debug (9)</A>
|
<LI><A HREF="adminmanual-13.html#ss13.8">13.8 accept/wwv (extended for sysops) (8)</A>
|
||||||
<LI><A HREF="adminmanual-12.html#ss12.23">12.23 directory (0)</A>
|
<LI><A HREF="adminmanual-13.html#ss13.9">13.9 announce (0)</A>
|
||||||
<LI><A HREF="adminmanual-12.html#ss12.24">12.24 directory (extended for sysops) (5)</A>
|
<LI><A HREF="adminmanual-13.html#ss13.10">13.10 announce full (0)</A>
|
||||||
<LI><A HREF="adminmanual-12.html#ss12.25">12.25 disconnect (8)</A>
|
<LI><A HREF="adminmanual-13.html#ss13.11">13.11 announce sysop (5)</A>
|
||||||
<LI><A HREF="adminmanual-12.html#ss12.26">12.26 dx (0)</A>
|
<LI><A HREF="adminmanual-13.html#ss13.12">13.12 apropos (0)</A>
|
||||||
<LI><A HREF="adminmanual-12.html#ss12.27">12.27 export (9)</A>
|
<LI><A HREF="adminmanual-13.html#ss13.13">13.13 bye (0)</A>
|
||||||
<LI><A HREF="adminmanual-12.html#ss12.28">12.28 export_users (9)</A>
|
<LI><A HREF="adminmanual-13.html#ss13.14">13.14 catchup (5)</A>
|
||||||
<LI><A HREF="adminmanual-12.html#ss12.29">12.29 forward/latlong (8)</A>
|
<LI><A HREF="adminmanual-13.html#ss13.15">13.15 clear/spots (0)</A>
|
||||||
<LI><A HREF="adminmanual-12.html#ss12.30">12.30 forward/opername (1)</A>
|
<LI><A HREF="adminmanual-13.html#ss13.16">13.16 connect (5) </A>
|
||||||
<LI><A HREF="adminmanual-12.html#ss12.31">12.31 help (0)</A>
|
<LI><A HREF="adminmanual-13.html#ss13.17">13.17 dbavail (0)</A>
|
||||||
<LI><A HREF="adminmanual-12.html#ss12.32">12.32 init (5)</A>
|
<LI><A HREF="adminmanual-13.html#ss13.18">13.18 dbcreate (9)</A>
|
||||||
<LI><A HREF="adminmanual-12.html#ss12.33">12.33 kill (0)</A>
|
<LI><A HREF="adminmanual-13.html#ss13.19">13.19 dbimport (9)</A>
|
||||||
<LI><A HREF="adminmanual-12.html#ss12.34">12.34 kill (5)</A>
|
<LI><A HREF="adminmanual-13.html#ss13.20">13.20 dbremove (9)</A>
|
||||||
<LI><A HREF="adminmanual-12.html#ss12.35">12.35 kill full (5)</A>
|
<LI><A HREF="adminmanual-13.html#ss13.21">13.21 dbshow (0)</A>
|
||||||
<LI><A HREF="adminmanual-12.html#ss12.36">12.36 links (0)</A>
|
<LI><A HREF="adminmanual-13.html#ss13.22">13.22 debug (9)</A>
|
||||||
<LI><A HREF="adminmanual-12.html#ss12.37">12.37 load/aliases (9)</A>
|
<LI><A HREF="adminmanual-13.html#ss13.23">13.23 directory (0)</A>
|
||||||
<LI><A HREF="adminmanual-12.html#ss12.38">12.38 load/baddx (9)</A>
|
<LI><A HREF="adminmanual-13.html#ss13.24">13.24 directory (extended for sysops) (5)</A>
|
||||||
<LI><A HREF="adminmanual-12.html#ss12.39">12.39 load/badmsg (9)</A>
|
<LI><A HREF="adminmanual-13.html#ss13.25">13.25 disconnect (8)</A>
|
||||||
<LI><A HREF="adminmanual-12.html#ss12.40">12.40 load/badwords (9)</A>
|
<LI><A HREF="adminmanual-13.html#ss13.26">13.26 dx (0)</A>
|
||||||
<LI><A HREF="adminmanual-12.html#ss12.41">12.41 load/bands (9)</A>
|
<LI><A HREF="adminmanual-13.html#ss13.27">13.27 export (9)</A>
|
||||||
<LI><A HREF="adminmanual-12.html#ss12.42">12.42 load/cmd_cache (9)</A>
|
<LI><A HREF="adminmanual-13.html#ss13.28">13.28 export_users (9)</A>
|
||||||
<LI><A HREF="adminmanual-12.html#ss12.43">12.43 load/forward (9)</A>
|
<LI><A HREF="adminmanual-13.html#ss13.29">13.29 forward/latlong (8)</A>
|
||||||
<LI><A HREF="adminmanual-12.html#ss12.44">12.44 load/messages (9)</A>
|
<LI><A HREF="adminmanual-13.html#ss13.30">13.30 forward/opername (1)</A>
|
||||||
<LI><A HREF="adminmanual-12.html#ss12.45">12.45 load/prefixes (9)</A>
|
<LI><A HREF="adminmanual-13.html#ss13.31">13.31 help (0)</A>
|
||||||
<LI><A HREF="adminmanual-12.html#ss12.46">12.46 merge (5)</A>
|
<LI><A HREF="adminmanual-13.html#ss13.32">13.32 init (5)</A>
|
||||||
<LI><A HREF="adminmanual-12.html#ss12.47">12.47 msg (9)</A>
|
<LI><A HREF="adminmanual-13.html#ss13.33">13.33 kill (0)</A>
|
||||||
<LI><A HREF="adminmanual-12.html#ss12.48">12.48 pc (8)</A>
|
<LI><A HREF="adminmanual-13.html#ss13.34">13.34 kill (5)</A>
|
||||||
<LI><A HREF="adminmanual-12.html#ss12.49">12.49 ping (1)</A>
|
<LI><A HREF="adminmanual-13.html#ss13.35">13.35 kill full (5)</A>
|
||||||
<LI><A HREF="adminmanual-12.html#ss12.50">12.50 rcmd (1)</A>
|
<LI><A HREF="adminmanual-13.html#ss13.36">13.36 links (0)</A>
|
||||||
<LI><A HREF="adminmanual-12.html#ss12.51">12.51 read (0)</A>
|
<LI><A HREF="adminmanual-13.html#ss13.37">13.37 load/aliases (9)</A>
|
||||||
<LI><A HREF="adminmanual-12.html#ss12.52">12.52 read (extended for sysops) (5) </A>
|
<LI><A HREF="adminmanual-13.html#ss13.38">13.38 load/baddx (9)</A>
|
||||||
<LI><A HREF="adminmanual-12.html#ss12.53">12.53 reject/announce</A>
|
<LI><A HREF="adminmanual-13.html#ss13.39">13.39 load/badmsg (9)</A>
|
||||||
<LI><A HREF="adminmanual-12.html#ss12.54">12.54 reject/announce (extended for sysops) (8)</A>
|
<LI><A HREF="adminmanual-13.html#ss13.40">13.40 load/badwords (9)</A>
|
||||||
<LI><A HREF="adminmanual-12.html#ss12.55">12.55 reject/spots (0)</A>
|
<LI><A HREF="adminmanual-13.html#ss13.41">13.41 load/bands (9)</A>
|
||||||
<LI><A HREF="adminmanual-12.html#ss12.56">12.56 reject/spots (extended for sysops) (8)</A>
|
<LI><A HREF="adminmanual-13.html#ss13.42">13.42 load/cmd_cache (9)</A>
|
||||||
<LI><A HREF="adminmanual-12.html#ss12.57">12.57 reject/wcy (0)</A>
|
<LI><A HREF="adminmanual-13.html#ss13.43">13.43 load/forward (9)</A>
|
||||||
<LI><A HREF="adminmanual-12.html#ss12.58">12.58 reject/wcy (extended for sysops) (8)</A>
|
<LI><A HREF="adminmanual-13.html#ss13.44">13.44 load/messages (9)</A>
|
||||||
<LI><A HREF="adminmanual-12.html#ss12.59">12.59 reject/wwv (0)</A>
|
<LI><A HREF="adminmanual-13.html#ss13.45">13.45 load/prefixes (9)</A>
|
||||||
<LI><A HREF="adminmanual-12.html#ss12.60">12.60 reject/wwv (extended for sysops) (8)</A>
|
<LI><A HREF="adminmanual-13.html#ss13.46">13.46 merge (5)</A>
|
||||||
<LI><A HREF="adminmanual-12.html#ss12.61">12.61 reply (0)</A>
|
<LI><A HREF="adminmanual-13.html#ss13.47">13.47 msg (9)</A>
|
||||||
<LI><A HREF="adminmanual-12.html#ss12.62">12.62 send (0)</A>
|
<LI><A HREF="adminmanual-13.html#ss13.48">13.48 pc (8)</A>
|
||||||
<LI><A HREF="adminmanual-12.html#ss12.63">12.63 set/address (0)</A>
|
<LI><A HREF="adminmanual-13.html#ss13.49">13.49 ping (1)</A>
|
||||||
<LI><A HREF="adminmanual-12.html#ss12.64">12.64 set/announce (0)</A>
|
<LI><A HREF="adminmanual-13.html#ss13.50">13.50 rcmd (1)</A>
|
||||||
<LI><A HREF="adminmanual-12.html#ss12.65">12.65 set/arcluster (5)</A>
|
<LI><A HREF="adminmanual-13.html#ss13.51">13.51 read (0)</A>
|
||||||
<LI><A HREF="adminmanual-12.html#ss12.66">12.66 set/baddx (8)</A>
|
<LI><A HREF="adminmanual-13.html#ss13.52">13.52 read (extended for sysops) (5) </A>
|
||||||
<LI><A HREF="adminmanual-12.html#ss12.67">12.67 set/badnode (6)</A>
|
<LI><A HREF="adminmanual-13.html#ss13.53">13.53 reject/announce</A>
|
||||||
<LI><A HREF="adminmanual-12.html#ss12.68">12.68 set/badspotter (8)</A>
|
<LI><A HREF="adminmanual-13.html#ss13.54">13.54 reject/announce (extended for sysops) (8)</A>
|
||||||
<LI><A HREF="adminmanual-12.html#ss12.69">12.69 set/beep (0)</A>
|
<LI><A HREF="adminmanual-13.html#ss13.55">13.55 reject/spots (0)</A>
|
||||||
<LI><A HREF="adminmanual-12.html#ss12.70">12.70 set/clx (5)</A>
|
<LI><A HREF="adminmanual-13.html#ss13.56">13.56 reject/spots (extended for sysops) (8)</A>
|
||||||
<LI><A HREF="adminmanual-12.html#ss12.71">12.71 set/debug (9)</A>
|
<LI><A HREF="adminmanual-13.html#ss13.57">13.57 reject/wcy (0)</A>
|
||||||
<LI><A HREF="adminmanual-12.html#ss12.72">12.72 set/dx (0)</A>
|
<LI><A HREF="adminmanual-13.html#ss13.58">13.58 reject/wcy (extended for sysops) (8)</A>
|
||||||
<LI><A HREF="adminmanual-12.html#ss12.73">12.73 set/dxgrid (0)</A>
|
<LI><A HREF="adminmanual-13.html#ss13.59">13.59 reject/wwv (0)</A>
|
||||||
<LI><A HREF="adminmanual-12.html#ss12.74">12.74 set/dxnet (5)</A>
|
<LI><A HREF="adminmanual-13.html#ss13.60">13.60 reject/wwv (extended for sysops) (8)</A>
|
||||||
<LI><A HREF="adminmanual-12.html#ss12.75">12.75 set/echo (0)</A>
|
<LI><A HREF="adminmanual-13.html#ss13.61">13.61 reply (0)</A>
|
||||||
<LI><A HREF="adminmanual-12.html#ss12.76">12.76 set/here (0)</A>
|
<LI><A HREF="adminmanual-13.html#ss13.62">13.62 send (0)</A>
|
||||||
<LI><A HREF="adminmanual-12.html#ss12.77">12.77 set/homenode (0)</A>
|
<LI><A HREF="adminmanual-13.html#ss13.63">13.63 set/address (0)</A>
|
||||||
<LI><A HREF="adminmanual-12.html#ss12.78">12.78 set/hops (8)</A>
|
<LI><A HREF="adminmanual-13.html#ss13.64">13.64 set/announce (0)</A>
|
||||||
<LI><A HREF="adminmanual-12.html#ss12.79">12.79 set/isolate (9)</A>
|
<LI><A HREF="adminmanual-13.html#ss13.65">13.65 set/arcluster (5)</A>
|
||||||
<LI><A HREF="adminmanual-12.html#ss12.80">12.80 set/language (0)</A>
|
<LI><A HREF="adminmanual-13.html#ss13.66">13.66 set/baddx (8)</A>
|
||||||
<LI><A HREF="adminmanual-12.html#ss12.81">12.81 set/location (0)</A>
|
<LI><A HREF="adminmanual-13.html#ss13.67">13.67 set/badnode (6)</A>
|
||||||
<LI><A HREF="adminmanual-12.html#ss12.82">12.82 set/sys_location (9)</A>
|
<LI><A HREF="adminmanual-13.html#ss13.68">13.68 set/badspotter (8)</A>
|
||||||
<LI><A HREF="adminmanual-12.html#ss12.83">12.83 set/logininfo (0)</A>
|
<LI><A HREF="adminmanual-13.html#ss13.69">13.69 set/beep (0)</A>
|
||||||
<LI><A HREF="adminmanual-12.html#ss12.84">12.84 set/lockout (9)</A>
|
<LI><A HREF="adminmanual-13.html#ss13.70">13.70 set/clx (5)</A>
|
||||||
<LI><A HREF="adminmanual-12.html#ss12.85">12.85 set/name (0)</A>
|
<LI><A HREF="adminmanual-13.html#ss13.71">13.71 set/debug (9)</A>
|
||||||
<LI><A HREF="adminmanual-12.html#ss12.86">12.86 set/node (9)</A>
|
<LI><A HREF="adminmanual-13.html#ss13.72">13.72 set/dx (0)</A>
|
||||||
<LI><A HREF="adminmanual-12.html#ss12.87">12.87 set/obscount (9)</A>
|
<LI><A HREF="adminmanual-13.html#ss13.73">13.73 set/dxgrid (0)</A>
|
||||||
<LI><A HREF="adminmanual-12.html#ss12.88">12.88 set/page (0)</A>
|
<LI><A HREF="adminmanual-13.html#ss13.74">13.74 set/dxnet (5)</A>
|
||||||
<LI><A HREF="adminmanual-12.html#ss12.89">12.89 set/password (9)</A>
|
<LI><A HREF="adminmanual-13.html#ss13.75">13.75 set/echo (0)</A>
|
||||||
<LI><A HREF="adminmanual-12.html#ss12.90">12.90 set/pinginterval (9)</A>
|
<LI><A HREF="adminmanual-13.html#ss13.76">13.76 set/here (0)</A>
|
||||||
<LI><A HREF="adminmanual-12.html#ss12.91">12.91 set/privilege (9)</A>
|
<LI><A HREF="adminmanual-13.html#ss13.77">13.77 set/homenode (0)</A>
|
||||||
<LI><A HREF="adminmanual-12.html#ss12.92">12.92 set/spider (5)</A>
|
<LI><A HREF="adminmanual-13.html#ss13.78">13.78 set/hops (8)</A>
|
||||||
<LI><A HREF="adminmanual-12.html#ss12.93">12.93 set/sys_qra (9)</A>
|
<LI><A HREF="adminmanual-13.html#ss13.79">13.79 set/isolate (9)</A>
|
||||||
<LI><A HREF="adminmanual-12.html#ss12.94">12.94 set/qra (0)</A>
|
<LI><A HREF="adminmanual-13.html#ss13.80">13.80 set/language (0)</A>
|
||||||
<LI><A HREF="adminmanual-12.html#ss12.95">12.95 set/qth (0)</A>
|
<LI><A HREF="adminmanual-13.html#ss13.81">13.81 set/location (0)</A>
|
||||||
<LI><A HREF="adminmanual-12.html#ss12.96">12.96 set/talk (0)</A>
|
<LI><A HREF="adminmanual-13.html#ss13.82">13.82 set/sys_location (9)</A>
|
||||||
<LI><A HREF="adminmanual-12.html#ss12.97">12.97 set/wcy (0)</A>
|
<LI><A HREF="adminmanual-13.html#ss13.83">13.83 set/logininfo (0)</A>
|
||||||
<LI><A HREF="adminmanual-12.html#ss12.98">12.98 set/wwv (0)</A>
|
<LI><A HREF="adminmanual-13.html#ss13.84">13.84 set/lockout (9)</A>
|
||||||
<LI><A HREF="adminmanual-12.html#ss12.99">12.99 set/wx (0)</A>
|
<LI><A HREF="adminmanual-13.html#ss13.85">13.85 set/name (0)</A>
|
||||||
<LI><A HREF="adminmanual-12.html#ss12.100">12.100 show/baddx (1)</A>
|
<LI><A HREF="adminmanual-13.html#ss13.86">13.86 set/node (9)</A>
|
||||||
<LI><A HREF="adminmanual-12.html#ss12.101">12.101 show/badnode (6)</A>
|
<LI><A HREF="adminmanual-13.html#ss13.87">13.87 set/obscount (9)</A>
|
||||||
<LI><A HREF="adminmanual-12.html#ss12.102">12.102 show/badspotter (1)</A>
|
<LI><A HREF="adminmanual-13.html#ss13.88">13.88 set/page (0)</A>
|
||||||
<LI><A HREF="adminmanual-12.html#ss12.103">12.103 show/date (0)</A>
|
<LI><A HREF="adminmanual-13.html#ss13.89">13.89 set/password (9)</A>
|
||||||
<LI><A HREF="adminmanual-12.html#ss12.104">12.104 show/dx (0)</A>
|
<LI><A HREF="adminmanual-13.html#ss13.90">13.90 set/pinginterval (9)</A>
|
||||||
<LI><A HREF="adminmanual-12.html#ss12.105">12.105 show/dxcc (0)</A>
|
<LI><A HREF="adminmanual-13.html#ss13.91">13.91 set/privilege (9)</A>
|
||||||
<LI><A HREF="adminmanual-12.html#ss12.106">12.106 show/files (0)</A>
|
<LI><A HREF="adminmanual-13.html#ss13.92">13.92 set/spider (5)</A>
|
||||||
<LI><A HREF="adminmanual-12.html#ss12.107">12.107 show/filter (0)</A>
|
<LI><A HREF="adminmanual-13.html#ss13.93">13.93 set/sys_qra (9)</A>
|
||||||
<LI><A HREF="adminmanual-12.html#ss12.108">12.108 show/filter (extended for sysops) (5)</A>
|
<LI><A HREF="adminmanual-13.html#ss13.94">13.94 set/qra (0)</A>
|
||||||
<LI><A HREF="adminmanual-12.html#ss12.109">12.109 show/hops (8)</A>
|
<LI><A HREF="adminmanual-13.html#ss13.95">13.95 set/qth (0)</A>
|
||||||
<LI><A HREF="adminmanual-12.html#ss12.110">12.110 show/isolate (1)</A>
|
<LI><A HREF="adminmanual-13.html#ss13.96">13.96 set/talk (0)</A>
|
||||||
<LI><A HREF="adminmanual-12.html#ss12.111">12.111 show/lockout (9)</A>
|
<LI><A HREF="adminmanual-13.html#ss13.97">13.97 set/wcy (0)</A>
|
||||||
<LI><A HREF="adminmanual-12.html#ss12.112">12.112 show/moon (0)</A>
|
<LI><A HREF="adminmanual-13.html#ss13.98">13.98 set/wwv (0)</A>
|
||||||
<LI><A HREF="adminmanual-12.html#ss12.113">12.113 show/muf (0)</A>
|
<LI><A HREF="adminmanual-13.html#ss13.99">13.99 set/wx (0)</A>
|
||||||
<LI><A HREF="adminmanual-12.html#ss12.114">12.114 show/node (1)</A>
|
<LI><A HREF="adminmanual-13.html#ss13.100">13.100 show/baddx (1)</A>
|
||||||
<LI><A HREF="adminmanual-12.html#ss12.115">12.115 show/prefix (0)</A>
|
<LI><A HREF="adminmanual-13.html#ss13.101">13.101 show/badnode (6)</A>
|
||||||
<LI><A HREF="adminmanual-12.html#ss12.116">12.116 show/program (5)</A>
|
<LI><A HREF="adminmanual-13.html#ss13.102">13.102 show/badspotter (1)</A>
|
||||||
<LI><A HREF="adminmanual-12.html#ss12.117">12.117 show/qra (0)</A>
|
<LI><A HREF="adminmanual-13.html#ss13.103">13.103 show/date (0)</A>
|
||||||
<LI><A HREF="adminmanual-12.html#ss12.118">12.118 show/qrz (0)</A>
|
<LI><A HREF="adminmanual-13.html#ss13.104">13.104 show/dx (0)</A>
|
||||||
<LI><A HREF="adminmanual-12.html#ss12.119">12.119 show/route (0)</A>
|
<LI><A HREF="adminmanual-13.html#ss13.105">13.105 show/dxcc (0)</A>
|
||||||
<LI><A HREF="adminmanual-12.html#ss12.120">12.120 show/satellite (0)</A>
|
<LI><A HREF="adminmanual-13.html#ss13.106">13.106 show/files (0)</A>
|
||||||
<LI><A HREF="adminmanual-12.html#ss12.121">12.121 show/sun (0)</A>
|
<LI><A HREF="adminmanual-13.html#ss13.107">13.107 show/filter (0)</A>
|
||||||
<LI><A HREF="adminmanual-12.html#ss12.122">12.122 show/time (0)</A>
|
<LI><A HREF="adminmanual-13.html#ss13.108">13.108 show/filter (extended for sysops) (5)</A>
|
||||||
<LI><A HREF="adminmanual-12.html#ss12.123">12.123 show/wcy (0)</A>
|
<LI><A HREF="adminmanual-13.html#ss13.109">13.109 show/hops (8)</A>
|
||||||
<LI><A HREF="adminmanual-12.html#ss12.124">12.124 show/wwv (0)</A>
|
<LI><A HREF="adminmanual-13.html#ss13.110">13.110 show/isolate (1)</A>
|
||||||
<LI><A HREF="adminmanual-12.html#ss12.125">12.125 shutdown (5)</A>
|
<LI><A HREF="adminmanual-13.html#ss13.111">13.111 show/lockout (9)</A>
|
||||||
<LI><A HREF="adminmanual-12.html#ss12.126">12.126 spoof (9)</A>
|
<LI><A HREF="adminmanual-13.html#ss13.112">13.112 show/log (8)</A>
|
||||||
<LI><A HREF="adminmanual-12.html#ss12.127">12.127 stat/db (5)</A>
|
<LI><A HREF="adminmanual-13.html#ss13.113">13.113 show/moon (0)</A>
|
||||||
<LI><A HREF="adminmanual-12.html#ss12.128">12.128 stat/channel (5)</A>
|
<LI><A HREF="adminmanual-13.html#ss13.114">13.114 show/muf (0)</A>
|
||||||
<LI><A HREF="adminmanual-12.html#ss12.129">12.129 stat/msg (5)</A>
|
<LI><A HREF="adminmanual-13.html#ss13.115">13.115 show/node (1)</A>
|
||||||
<LI><A HREF="adminmanual-12.html#ss12.130">12.130 stat/user (5)</A>
|
<LI><A HREF="adminmanual-13.html#ss13.116">13.116 show/prefix (0)</A>
|
||||||
<LI><A HREF="adminmanual-12.html#ss12.131">12.131 sysop (0)</A>
|
<LI><A HREF="adminmanual-13.html#ss13.117">13.117 show/program (5)</A>
|
||||||
<LI><A HREF="adminmanual-12.html#ss12.132">12.132 talk (0)</A>
|
<LI><A HREF="adminmanual-13.html#ss13.118">13.118 show/qra (0)</A>
|
||||||
<LI><A HREF="adminmanual-12.html#ss12.133">12.133 type (0)</A>
|
<LI><A HREF="adminmanual-13.html#ss13.119">13.119 show/qrz (0)</A>
|
||||||
<LI><A HREF="adminmanual-12.html#ss12.134">12.134 who (0)</A>
|
<LI><A HREF="adminmanual-13.html#ss13.120">13.120 show/route (0)</A>
|
||||||
<LI><A HREF="adminmanual-12.html#ss12.135">12.135 wx (0)</A>
|
<LI><A HREF="adminmanual-13.html#ss13.121">13.121 show/satellite (0)</A>
|
||||||
<LI><A HREF="adminmanual-12.html#ss12.136">12.136 wx (enhanced for sysops) (5)</A>
|
<LI><A HREF="adminmanual-13.html#ss13.122">13.122 show/sun (0)</A>
|
||||||
|
<LI><A HREF="adminmanual-13.html#ss13.123">13.123 show/time (0)</A>
|
||||||
|
<LI><A HREF="adminmanual-13.html#ss13.124">13.124 show/wcy (0)</A>
|
||||||
|
<LI><A HREF="adminmanual-13.html#ss13.125">13.125 show/wwv (0)</A>
|
||||||
|
<LI><A HREF="adminmanual-13.html#ss13.126">13.126 shutdown (5)</A>
|
||||||
|
<LI><A HREF="adminmanual-13.html#ss13.127">13.127 spoof (9)</A>
|
||||||
|
<LI><A HREF="adminmanual-13.html#ss13.128">13.128 stat/db (5)</A>
|
||||||
|
<LI><A HREF="adminmanual-13.html#ss13.129">13.129 stat/channel (5)</A>
|
||||||
|
<LI><A HREF="adminmanual-13.html#ss13.130">13.130 stat/msg (5)</A>
|
||||||
|
<LI><A HREF="adminmanual-13.html#ss13.131">13.131 stat/user (5)</A>
|
||||||
|
<LI><A HREF="adminmanual-13.html#ss13.132">13.132 sysop (0)</A>
|
||||||
|
<LI><A HREF="adminmanual-13.html#ss13.133">13.133 talk (0)</A>
|
||||||
|
<LI><A HREF="adminmanual-13.html#ss13.134">13.134 type (0)</A>
|
||||||
|
<LI><A HREF="adminmanual-13.html#ss13.135">13.135 who (0)</A>
|
||||||
|
<LI><A HREF="adminmanual-13.html#ss13.136">13.136 wx (0)</A>
|
||||||
|
<LI><A HREF="adminmanual-13.html#ss13.137">13.137 wx (enhanced for sysops) (5)</A>
|
||||||
</UL>
|
</UL>
|
||||||
<HR>
|
<HR>
|
||||||
<A HREF="adminmanual-1.html">Next</A>
|
<A HREF="adminmanual-1.html">Next</A>
|
||||||
|
@ -6,7 +6,7 @@
|
|||||||
|
|
||||||
<title>The DXSpider Installation and Administration Manual
|
<title>The DXSpider Installation and Administration Manual
|
||||||
<author>Ian Maude, G0VGS, (ianmaude@btinternet.com)
|
<author>Ian Maude, G0VGS, (ianmaude@btinternet.com)
|
||||||
<date>Version 1.31 January 2001
|
<date>Version 1.32 February 2001
|
||||||
<abstract>
|
<abstract>
|
||||||
A reference for SysOps of the DXSpider DXCluster program.
|
A reference for SysOps of the DXSpider DXCluster program.
|
||||||
</abstract>
|
</abstract>
|
||||||
@ -1502,6 +1502,123 @@ 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
|
Make sure you only send mail to the clusters that want it by using the
|
||||||
Forward.pl file very carefully.
|
Forward.pl file very carefully.
|
||||||
|
|
||||||
|
<sect>Databases
|
||||||
|
|
||||||
|
<P>
|
||||||
|
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.
|
||||||
|
|
||||||
|
<sect1>Creating databases
|
||||||
|
|
||||||
|
<P>
|
||||||
|
Creating a database could not be more simple. All the commands are
|
||||||
|
sent from the cluster prompt as the <em>sysop</em> user.
|
||||||
|
|
||||||
|
To create a database you use the command <em>dbcreate</em>. It can
|
||||||
|
be used in 3 different ways like so ..
|
||||||
|
|
||||||
|
<tscreen><verb>
|
||||||
|
dbcreate <name>
|
||||||
|
</verb></tscreen>
|
||||||
|
|
||||||
|
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.
|
||||||
|
|
||||||
|
<tscreen><verb>
|
||||||
|
dbcreate <name> chain <name> [<name>...]
|
||||||
|
</verb></tscreen>
|
||||||
|
|
||||||
|
This creates a chained database entry. The first database will be
|
||||||
|
scanned, then the second, the third etc...
|
||||||
|
|
||||||
|
<tscreen><verb>
|
||||||
|
dbcreate <name> remote <name>
|
||||||
|
</verb></tscreen>
|
||||||
|
|
||||||
|
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...
|
||||||
|
|
||||||
|
<tscreen><verb>
|
||||||
|
dbcreate buckmaster remote gb7dxc
|
||||||
|
</verb></tscreen>
|
||||||
|
|
||||||
|
Remote databases cannot be chained, however, the last database in a
|
||||||
|
chain can be a remote database.
|
||||||
|
|
||||||
|
<sect1>Importing databases
|
||||||
|
|
||||||
|
<P>
|
||||||
|
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 ...
|
||||||
|
|
||||||
|
<tscreen><verb>
|
||||||
|
dbimport oblast /tmp/OBLAST.FUL
|
||||||
|
</verb></tscreen>
|
||||||
|
|
||||||
|
This will update the existing local oblast database or create it if
|
||||||
|
it does not exist.
|
||||||
|
|
||||||
|
<sect1>Checking available databases
|
||||||
|
|
||||||
|
<P>
|
||||||
|
Once a database is created, you will want to check that it has been
|
||||||
|
added. To do this use the <em>dbavail</em> command. This will
|
||||||
|
output the available databases. For example ...
|
||||||
|
|
||||||
|
<tscreen><verb>
|
||||||
|
dbavail
|
||||||
|
DB Name Location Chain
|
||||||
|
qsl Local
|
||||||
|
buck GB7ADX
|
||||||
|
hftest GB7DXM
|
||||||
|
G0VGS de GB7MBC 3-Feb-2001 1925Z >
|
||||||
|
</verb></tscreen>
|
||||||
|
|
||||||
|
<sect1>Looking up databases
|
||||||
|
|
||||||
|
<P>
|
||||||
|
To look for information in a defined database, simply use the <em>dbshow</em>
|
||||||
|
command, for example ...
|
||||||
|
|
||||||
|
<tscreen><verb>
|
||||||
|
dbshow buckmaster G0YLM
|
||||||
|
</verb></tscreen>
|
||||||
|
|
||||||
|
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
|
||||||
|
<em>show</em> command like this ...
|
||||||
|
|
||||||
|
<tscreen><verb>
|
||||||
|
'^sh\w*/buc', 'dbshow buckmaster', 'dbshow',
|
||||||
|
</verb></tscreen>
|
||||||
|
|
||||||
|
Now you can simply use show/buckmaster or an abreviation.
|
||||||
|
|
||||||
|
<sect1>Removing databases
|
||||||
|
|
||||||
|
<P>
|
||||||
|
To delete an existing database you use the <em>dbremove</em> command.
|
||||||
|
For example ...
|
||||||
|
|
||||||
|
<tscreen><verb>
|
||||||
|
dbremove oblast
|
||||||
|
</verb></tscreen>
|
||||||
|
|
||||||
|
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.
|
||||||
|
|
||||||
<sect>Information, files and useful programs
|
<sect>Information, files and useful programs
|
||||||
|
|
||||||
<sect1>MOTD
|
<sect1>MOTD
|
||||||
@ -4031,6 +4148,18 @@ Show which nodes are currently set to be isolated.
|
|||||||
Show a list of callsigns that have been excluded (locked out) of the
|
Show a list of callsigns that have been excluded (locked out) of the
|
||||||
cluster locally with the <em>set/lockout</em> command
|
cluster locally with the <em>set/lockout</em> command
|
||||||
|
|
||||||
|
<sect1>show/log (8)
|
||||||
|
|
||||||
|
<P>
|
||||||
|
<tt>
|
||||||
|
<bf>show/log [<callsign>]</bf> Show excerpts from the system log
|
||||||
|
</tt>
|
||||||
|
|
||||||
|
<P>
|
||||||
|
This command outputs a short section of the system log. On its own
|
||||||
|
it will output a general logfile. With the optional callsign it will
|
||||||
|
show output from the log associated with that callsign.
|
||||||
|
|
||||||
<sect1>show/moon (0)
|
<sect1>show/moon (0)
|
||||||
|
|
||||||
<P>
|
<P>
|
||||||
|
File diff suppressed because it is too large
Load Diff
Loading…
Reference in New Issue
Block a user