<!-- Title information -->
-<title>The DXSpider Administration Manual v1.48</title>
+<title>The DXSpider Administration Manual v1.49</title>
<author>Ian Maude, G0VGS, (ianmaude@btinternet.com)</author>
-<date>Version 1.49 November 2001 revision 1.1</date>
+<date>December 2001 revision 1.2</date>
<abstract>
A reference for SysOps of the DXSpider DXCluster program.
series of PC frame types. PC11 for example is a DX spot. The figures here
are not exhaustive but should give you a good idea of how the file works.
+<P>
+SHould any of the nodecalls include an ssid, it is important to wrap the
+whole call in single quotes, like this ...
+
+<tscreen><verb>
+ 'DB0FHF-15' => {
+ 11 => 5,
+ 12 => 8,
+ 16 => 8,
+ 17 => 8,
+ 19 => 8,
+ 21 => 8,
+ },
+</verb></tscreen>
+
+If you do not do this, you will get errors and the file will not work as
+expected.
+
<P>
You can alter this file at any time, including whilst the cluster is running.
If you alter the file during runtime, the command <em>load/hops</em> will
)
</verb></tscreen>
+<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.
export 5467 /spider/perl/keps.in
</verb></tscreen>
+<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 ...
./convkeps.pl keps.in
</verb></tscreen>
+<P>
Now go back to the cluster and issue the command ...
<tscreen><verb>
load/keps
</verb></tscreen>
+<P>
That is it! the kepler data has been updated.
<sect1>The QRZ callbook
<P>
<tt>
-<bf>accept/announce [0-9] <pattern></bf> Set an accept filter
+<bf>accept/spots [0-9] <pattern></bf> Set an accept filter
line for spots
</tt>