\r
<!-- Title information -->\r
\r
-<title>The DXSpider Administration Manual v1.50</title> \r
+<title>The DXSpider Administration Manual v1.51</title> \r
<author>Ian Maude, G0VGS, (g0vgs@gb7mbc.net), and\r
Charlie Carroll, K1XX, (k1xx@ptcnh.net)</author>\r
-<date>April 2003 revision 0.7</date>\r
+<date>June 2004 revision 1</date>\r
\r
<abstract>\r
A reference for SysOps of the DXSpider DXCluster program.\r
repository. You do this with the command below ...\r
\r
<verb>\r
-cvs -d:pserver:anonymous@cvs.DXSpider.sourceforge.net:/cvsroot/dxspider login\r
+cvs -d:pserver:anonymous@cvs.sourceforge.net:/cvsroot/dxspider login\r
</verb>\r
\r
You will get a password prompt. Simply hit return here and your machine should\r
directory.\r
\r
<verb>\r
-cvs -z3 -d:pserver:anonymous@cvs.DXSpider.sourceforge.net:/cvsroot/dxspider co spider\r
+cvs -z3 -d:pserver:anonymous@cvs.sourceforge.net:/cvsroot/dxspider co spider\r
</verb>\r
\r
This command is all on one line.\r
\r
In the top line for CVSROOT, enter:\r
<tscreen><verb>\r
-anonymous@cvs.DXSpider.sourceforge.net:/cvsroot/dxspider login\r
+anonymous@cvs.sourceforge.net:/cvsroot/dxspider login\r
</verb></tscreen>\r
\r
and select\r
<P>
You can select the language that you want the cluster to use. Currently
-the languages available are en (English), de (German), es (Spanish)
-and nl (Dutch).
+the languages available are en (English), de (German), es (Spanish),
+Czech (cz), French (fr), Portuguese (pt), Italian (it) and nl (Dutch).
<sect1>set/location <lat & long> (0)
<P>
<P>
<tt>
-<bf>set/logininfo</bf> Inform when a station logs in locally
+<bf>set/logininfo</bf> Inform when a station logs in/out locally
</tt>
<P>
<P>
Tell the system that the call(s) are to be treated as DXSpider node and
fed new style DX Protocol rather normal user commands.
+<sect1>set/startup (0)
+
+<P>
+<tt>
+<bf>set/startup</bf> Create your own startup script
+</tt>
+
+<P>
+Create a startup script of DXSpider commands which will be executed
+everytime that you login into this node. You can only input the whole
+script afresh, it is not possible to 'edit' it. Inputting a new script is
+just like typing in a message using SEND. To finish inputting type: /EX
+on a newline, to abandon the script type: /ABORT.
+
+You may find the (curiously named) command BLANK useful to break
+up the output. If you simply want a blank line, it is easier to
+input one or more spaces and press the <return> key.
+
+See UNSET/STARTUP to remove a script.
+<sect1>set/startup <call> (6)
+
+<P>
+<tt>
+<bf>set/startup <call></bf> Create a user startup script
+</tt>
+
+<P>
<sect1>set/sys_location <lat & long> (9)
<P>
You can also use this with the 'by' keyword so
eg by W dxcc
</verb></tscreen>
-
+
+<tscreen><verb>
+ real or rt - Format the output the same as for real time spots. The
+ formats are deliberately different (so you can tell
+ one sort from the other). This is useful for some
+ logging programs that can't cope with normal sh/dx
+ output. An alias of SHOW/FDX is available.
+</verb></tscreen>
+
+<tscreen><verb>
+ filter - Filter the spots, before output, with the user's
+ spot filter. An alias of SHOW/MYDX is available.
+</verb></tscreen>
+
+<tscreen><verb>
+ zone <zones> - look for spots in the cq zone (or zones) specified.
+ zones are numbers separated by commas.
+</verb></tscreen>
+
+<tscreen><verb>
+ by_zone <zones> - look for spots spotted by people in the cq zone
+ specified.
+</verb></tscreen>
+
+<tscreen><verb>
+ itu <itus> - look for spots in the itu zone (or zones) specified
+ itu zones are numbers separated by commas.
+</verb></tscreen>
+
+<tscreen><verb>
+ by_itu <itus> - look for spots spotted by people in the itu zone
+ specified.
+</verb></tscreen>
+
+<tscreen><verb>
+ state <list> - look for spots in the US state (or states) specified
+ The list is two letter state codes separated by commas.
+</verb></tscreen>
+
+<tscreen><verb>
+ by_state <list> - look for spots spotted by people in the US state
+ specified.
+</verb></tscreen>
+
<tscreen><verb>
e.g.
</verb></tscreen>
SH/DX qra jn86
SH/DX dxcc oq2
SH/DX dxcc oq2 by w dxcc
+ SH/DX zone 4,5,6
+ SH/DX by_zone 4,5,6
+ SH/DX state in,oh
+ SH/DX by_state in,oh
</verb></tscreen>
<sect1>show/dxcc <prefix> (0)
SH/DX dxcc w on 20m iota
</verb></tscreen>
+This is an alias for: SH/DX dxcc
<sect1>show/dxqsl <callsign> (0)
<P>
<P>
Show the total DX spots for the last <days> no of days (default is 31),
starting from a <date> (default: today).
+<sect1>show/fdx (0)
+
+<P>
+<tt>
+<bf>show/fdx</bf> Show the DX data in realtime format.
+</tt>
+
+<P>
+Normally SHOW/DX outputs spot data in a different format to the
+realtime data. This is a deliberate policy (so you can tell the
+difference between the two). Some logging programs cannot handle
+this so SHOW/FDX outputs historical data in real time format.
+
+This is an alias for: SHOW/DX real
<sect1>show/files [<filearea> [<string>]] (0)
<P>
Gives you an estimate of the long path propagation characterics. It
should be noted that the figures will probably not be very useful, nor
terrible accurate, but it is included for completeness.
+<sect1>show/mydx (0)
+
+<P>
+<tt>
+<bf>show/mydx</bf> Show the DX data filtered with your spot filter.
+</tt>
+
+<P>
+SHOW/DX potentially shows all the spots available in the system. Using
+SHOW/MYDX will, instead, filter the availble spots using any spot filter
+that you have set, first.
+
+This command, together with ACCEPT/SPOT or REJECT/SPOT, will allow
+you to customise the spots that you receive.
+
+So if you have said: ACC/SPOT on hf
+
+Doing a SHOW/MYDX will now only, ever, show HF spots. All the other
+options on SH/DX can still be used.
<sect1>show/newconfiguration [<node>] (0)
<P>
SH/SAT FENGYUN1 12 2
</verb></tscreen>
+<sect1>show/startup (0)
+
+<P>
+<tt>
+<bf>show/startup</bf> View your own startup script
+</tt>
+
+<P>
+View the contents of a startup script created with SET/STARTUP.
+<sect1>show/startup <call> (6)
+
+<P>
+<tt>
+<bf>show/startup <call></bf> View a user startup script
+</tt>
+
+<P>
<sect1>show/station all [<regex>] (6)
<P>
<P>
<tt>
-<bf>unset/logininfo</bf> Inform when a station logs out locally
+<bf>unset/logininfo</bf> No longer inform when a station logs in/out locally
</tt>
<P>
</tt>
<P>
-This command will set your user prompt to exactly the string that you
+This command will set your user prompt to the string that you
say. The point of this command to enable a user to interface to programs
that are looking for a specific prompt (or else you just want a different
-fixed prompt).
+prompt).
<tscreen><verb>
SET/PROMPT clx >
</verb></tscreen>
-UNSET/PROMPT will undo the SET/PROMPT command and set you prompt back to
+There are some substitutions that can be added to the prompt:
+
+<tscreen><verb>
+ %C - callsign [which will have ( and ) around it if not here]
+ %D - date
+ %T - time
+ %M - cluster 'mycall'
+</verb></tscreen>
+
+The standard prompt is defined as:
+
+<tscreen><verb>
+ SET/PROMPT %C de %M %D %T dxspider >
+</verb></tscreen>
+
+UNSET/PROMPT will undo the SET/PROMPT command and set your prompt back to
normal.
<sect1>unset/register <call> ... (9)
The only exception to this is that a non-registered user can TALK or
SEND messages to the sysop.
-
+<sect1>unset/startup (0)
+
+<P>
+<tt>
+<bf>unset/startup</bf> Remove your own startup script
+</tt>
+
+<P>
+You can remove your startup script with UNSET/STARTUP.
+<sect1>unset/startup <call> (6)
+
+<P>
+<tt>
+<bf>unset/startup <call></bf> Remove a user startup script
+</tt>
+
+<P>
<sect1>unset/talk (0)
<P>
projects / spider.git / blobdiff