X-Git-Url: http://scm.dxcluster.org/gitweb/gitweb.cgi?a=blobdiff_plain;f=html%2Fadminmanual-11.html;h=e08773e303a1952d9a5499aefc66f1e7e93c0dd4;hb=b85014c2efe367be21460ff3e72f4a0727e6c26c;hp=c83dd63dc62e47028225fabc6e2effc3372a1b58;hpb=c42f6d2e451d149bd3ee9059ed8a9a4589c47f6d;p=spider.git diff --git a/html/adminmanual-11.html b/html/adminmanual-11.html index c83dd63d..e08773e3 100644 --- a/html/adminmanual-11.html +++ b/html/adminmanual-11.html @@ -32,6 +32,7 @@ passed onto the user. See HELP FILTERS for more info. Please read this to understand how filters work - it will save a lot of grief later on.
You can use any of the following things in this line:-
+
info <string> eg: iota or qsl
by <prefixes> eg: G,M,2
@@ -46,24 +47,31 @@ to understand how filters work - it will save a lot of grief later on.
wx 1 filter WX announces
dest <prefixes> eg: 6MUK,WDX (distros)
+
some examples:-
+
acc/ann dest 6MUK
acc/ann 2 by_zone 14,15,16
(this could be all on one line: acc/ann dest 6MUK or by_zone 14,15,16)
+
or
+
acc/ann by G,M,2
+
This filter would only allow announces that were posted buy UK stations. You can use the tag 'all' to accept everything eg:
+
acc/ann all
+
but this probably for advanced users...
This version allows a sysop to set a filter for a callsign as well as the default for nodes and users eg:-
+
accept/ann by G,M,2
accept/ann input node_default by G,M,2
accept/ann user_default by G,M,2
+
You can use any of the following things in this line:-
+
freq <range> eg: 0/30000 or hf or hf/cw or 6m,4m,2m
on <range> same as 'freq'
@@ -107,6 +118,7 @@ to understand how filters work - it will save a lot of grief later on.
origin <prefixes>
channel <prefixes>
+
For frequencies, you can use any of the band names defined in SHOW/BANDS and you can use a subband name like: cw, rtty, data, ssb - @@ -115,15 +127,19 @@ this is more efficient than saying simply: freq HF (but don't get too hung up about that)
some examples:-
+
acc/spot 1 on hf/cw
acc/spot 2 on vhf and (by_zone 14,15,16 or call_zone 14,15,16)
+
You can use the tag 'all' to accept everything, eg:
+
acc/spot 3 all
+
but this probably for advanced users...
This version allows a sysop to set a filter for a callsign as well as the default for nodes and users eg:-
+
accept/spot db0sue-7 1 by_zone 14,15,16
accept/spot node_default all
@@ -141,6 +158,7 @@ default for nodes and users eg:-
accept/spot user_default by G,M,2
+
It is unlikely that you will want to do this, but if you do then you can filter on the following fields:-
+
by <prefixes> eg: G,M,2
origin <prefixes>
@@ -161,6 +180,7 @@ filter on the following fields:-
by_zone <numbers>
channel <prefixes>
+
There are no examples because WCY Broadcasts only come from one place and you either want them or not (see UNSET/WCY if you don't want them). @@ -176,10 +196,12 @@ WCY filter sysop version
This version allows a sysop to set a filter for a callsign as well as the default for nodes and users eg:-
+
accept/wcy node_default all
set/hops node_default 10
+
It is unlikely that you will want to do this, but if you do then you can filter on the following fields:-
+
by <prefixes> eg: G,M,2
origin <prefixes>
@@ -200,11 +223,14 @@ filter on the following fields:-
by_zone <numbers>
channel <prefixes>
+
for example
+
accept/wwv by_zone 4
+
is probably the only useful thing to do (which will only show WWV broadcasts by stations in the US).
See HELP FILTER for information. @@ -218,6 +244,7 @@ WWV filter sysop version
This version allows a sysop to set a filter for a callsign as well as the default for nodes and users eg:-
+
accept/wwv db0sue-7 1 by_zone 4
accept/wwv node_default all
@@ -225,6 +252,7 @@ default for nodes and users eg:-
accept/wwv user_default by W,K
+
+
catchup GB7DJK all
catchup GB7DJK 300 301 302 303 500-510
+
and to undo what you have just done:-
+
uncatchup GB7DJK all
uncatchup GB7DJK 300 301 302 303 500-510
+
which will arrange for them to be forward candidates again.
Order is not important.
@@ -299,25 +331,33 @@ commmands:- remove the whole filter.
If you have a filter:-
+
acc/spot 1 on hf/cw
acc/spot 2 on vhf and (by_zone 14,15,16 or call_zone 14,15,16)
+
and you say:-
+
clear/spot 1
+
you will be left with:-
+
acc/spot 2 on vhf and (by_zone 14,15,16 or call_zone 14,15,16)
+
If you do:
+
clear/spot all
+
the filter will be completely removed.
@@ -426,15 +466,19 @@ the associated datafile. It is expected that the sysop will add an entry to the local Aliases file so that users can use the more familiar AK1A style of enquiry such as:
+
SH/BUCK G1TLH
+
but if he hasn't and the database really does exist (use DBAVAIL or SHOW/COMMAND to find out) you can do the same thing with:
+
DBSHOW buck G1TLH
+
You can combine some of the various directory commands together eg:-
+
DIR TO G1TLH 5
or
DIR SUBJECT IOTA 200-250
+
You can abbreviate all the commands to one letter and use ak1a syntax:-
+
DIR/T G1* 10
DIR/S QSL 10-100 5
+
This is how you send a DX Spot to other users. You can, in fact, now enter the <freq> and the <call> either way round.
+
DX FR0G 144.600
DX 144.600 FR0G
DX 144600 FR0G
+
will all give the same result. You can add some remarks to the end of the command and they will be added to the spot.
+
DX FR0G 144600 this is a test
+
You can credit someone else by saying:-
+
DX by G1TLH FR0G 144.600 he isn't on the cluster
+
The <freq> is compared against the available bands set up in the cluster. See SHOW/BANDS for more information.
@@ -617,8 +671,10 @@ this command. You can remove more than one message at a time.
As a sysop you can kill any message on the system.
kill full <msgno> [<msgno>] Delete a message from the whole cluster
kill full <msgno> [<msgno>] Delete a message from the whole cluster
+
Delete a message (usually a 'bulletin') from the whole cluster system.
This uses the subject field, so any messages that have exactly the same subject will be deleted. Beware! @@ -643,8 +699,10 @@ changes to take effect.
load/baddx Reload the bad DX table
load/baddx Reload the bad DX table
+
Reload the /spider/data/baddx.pl file if you have changed it manually whilst the cluster is running. This table contains the DX Calls that, if spotted, will not be passed on. FR0G and TEST are classic examples. @@ -824,6 +882,7 @@ passed onto the user. See HELP FILTERS for more info. Please read this to understand how filters work - it will save a lot of grief later on.
You can use any of the following things in this line:-
+
info <string> eg: iota or qsl
by <prefixes> eg: G,M,2
@@ -838,16 +897,21 @@ to understand how filters work - it will save a lot of grief later on.
wx 1 filter WX announces
dest <prefixes> eg: 6MUK,WDX (distros)
+
some examples:-
+
rej/ann by_zone 14,15,16 and not by G,M,2
+
You can use the tag 'all' to reject everything eg:
+
rej/ann all
+
but this probably for advanced users...
This version allows a sysop to set a filter for a callsign as well as the default for nodes and users eg:-
+
reject/ann by G,M,2
reject/ann input node_default by G,M,2
reject/ann user_default by G,M,2
+
You can use any of the following things in this line:-
+
freq <range> eg: 0/30000 or hf or hf/cw or 6m,4m,2m
on <range> same as 'freq'
@@ -890,6 +957,7 @@ to understand how filters work - it will save a lot of grief later on.
origin <prefixes>
channel <prefixes>
+
For frequencies, you can use any of the band names defined in SHOW/BANDS and you can use a subband name like: cw, rtty, data, ssb - thus: hf/ssb. You can also just have a simple range like: 0/30000 - @@ -897,15 +965,19 @@ this is more efficient than saying simply: on HF (but don't get too hung up about that)
some examples:-
+
rej/spot 1 on hf
rej/spot 2 on vhf and not (by_zone 14,15,16 or call_zone 14,15,16)
+
You can use the tag 'all' to reject everything eg:
+
rej/spot 3 all
+
but this probably for advanced users...
This version allows a sysop to set a filter for a callsign as well as the default for nodes and users eg:-
+
reject/spot db0sue-7 1 by_zone 14,15,16
reject/spot node_default all
@@ -924,6 +997,7 @@ default for nodes and users eg:-
reject/spot user_default by G,M,2
+
It is unlikely that you will want to do this, but if you do then you can filter on the following fields:-
+
by <prefixes> eg: G,M,2
origin <prefixes>
@@ -944,6 +1019,7 @@ filter on the following fields:-
by_zone <numbers>
channel <prefixes>
+
There are no examples because WCY Broadcasts only come from one place and you either want them or not (see UNSET/WCY if you don't want them).
This command is really provided for future use. @@ -967,6 +1043,7 @@ default for nodes and users eg:-
It is unlikely that you will want to do this, but if you do then you can filter on the following fields:-
+
by <prefixes> eg: G,M,2
origin <prefixes>
@@ -978,11 +1055,14 @@ filter on the following fields:-
by_zone <numbers>
channel <prefixes>
+
for example
+
reject/wwv by_zone 14,15,16
+
is probably the only useful thing to do (which will only show WWV broadcasts by stations in the US).
See HELP FILTER for information. @@ -996,12 +1076,14 @@ WWV reject filter sysop version
This version allows a sysop to set a filter for a callsign as well as the default for nodes and users eg:-
+
reject/wwv db0sue-7 1 by_zone 4
reject/wwv node_default all
reject/wwv user_default by W
+
You can have more than one callsign in all of the SEND commands.
You can have multiple qualifiers so that you can have for example:-
+
SEND RR COPY 123 PRIVATE G1TLH G0RDI
+
which should send a copy of message 123 to G1TLH and G0RDI and you will receive a read receipt when they have read the message.
SB is an alias for SEND NOPRIVATE (or send a bulletin in BBS speak) @@ -1077,14 +1161,18 @@ field of a DX spot from going any further. They will not be displayed and they will not be sent onto other nodes.
The word must be wriiten in full, no wild cards are allowed eg:-
+
set/baddx FORSALE VIDEO FR0G
+
To allow a word again, use the following command ...
+
unset/baddx VIDEO
+
The call can be a full or partial call (or a prefix), eg:-
+
set/badnode K1TTT
+
will stop anything from K1TTT (including any SSID's)
+
unset/badnode K1TTT
+
will allow spots from him again.
Use with extreme care. This command may well be superceded by FILTERing.
@@ -1118,15 +1210,19 @@ going any further. They will not be displayed and they will not be sent onto other nodes.
The call must be written in full, no wild cards are allowed eg:-
+
set/badspotter VE2STN
+
will stop anything from VE2STN. If you want SSIDs as well then you must enter them specifically.
+
unset/badspotter VE2STN
+
will allow spots from him again.
Use with extreme care. This command may well be superceded by FILTERing.
@@ -1208,9 +1304,11 @@ around your callsign to indicate you are not available. to you will normally find their way there should you not be connected. eg:-
+
SET/HOMENODE gb7djk
+
This command allows you to set up special hop counts for a node for currently: announce, spots, wwv and wcy broadcasts.
+
eg:
set/hops gb7djk ann 10
set/hops gb7mbc spots 20
+
Set SHOW/HOPS for information on what is already set. This command creates a filter and works in conjunction with the filter system.
@@ -1258,9 +1358,11 @@ the languages available are en (English) and nl (Dutch).
You can set your latitude and longitude manually or alternatively use the set/qra command which will do the conversion for you.
+
set/location 54 04 N 2 02 E
+
+
SET/LOCATION 52 22 N 0 57 E
+
Tell the cluster what your name is, eg:-
+
set/name Dirk
+
From version 1.41 you can also set the following types of cluster
+
set/spider
set/dxnet
set/clx
set/arcluster
+
To see what your nodes are set to, use the show/nodes command.
+
SET/PAGE 30
SET/PAGE 0
+
The setting is stored in your user profile.
@@ -1424,9 +1534,11 @@ the node_call a DXSpider type node done a SET/LOCATION then your latitude and longitude will be set roughly correctly (assuming your locator is correct ;-). For example:-
+
SET/QRA JO02LQ
+
Tell the system where your are. For example:-
+
set/qth East Dereham, Norfolk
+
In addition you can add any number of these options in very nearly any order to the basic SHOW/DX command, they are:-
+
on <band> - eg 160m 20m 2m 23cm 6mm
@@ -1550,8 +1665,10 @@ iota [<iota>] - If the iota island number is missing it will
qra [<locator>] - this will look for the specific locator if
you specify one or else anything that looks like a locator.
+
e.g.
+
SH/DX 9m0
@@ -1562,6 +1679,7 @@ qra [<locator>] - this will look for the specific locator if
SH/DX iota eu-064
SH/DX qra jn86
+
The options for SHOW/DX also apply to this command. e.g.
+
SH/DXCC G
SH/DXCC W on 20m info iota
+
+
SH/FILES <filearea>
+
where <filearea> is the name of the filearea you want to see the contents of.
You can also use shell globbing characters like '*' and '?' in a string to see a selection of files in a filearea eg:-
+
SH/FILES bulletins arld*
+
See also TYPE - to see the contents of a file.
For example:-
+
SH/MOON
SH/MOON G1TLH W5UN
+
+
SH/MUF W
+
produces:
+
RxSens: -123 dBM SFI: 159 R: 193 Month: 10 Day: 21
Power : 20 dBW Distance: 6283 km Delay: 22.4 ms
@@ -1716,20 +1845,25 @@ hours required after the prefix. For example:-
18 23 11.5 -35 mS0+ mS2 S3
19 0 11.2 -41 mS0+ mS2 S3
+
indicating that you will have weak, fading circuits on top band and 80m but usable signals on 40m (about S3).
inputing:-
+
SH/MUF W 24
+
will get you the above display, but with the next 24 hours worth of propagation data.
+
SH/MUF W L 24
SH/MUF W 24 Long
+
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. @@ -1776,10 +1910,12 @@ distance and bearing between two locators or (if only one locator is given on the command line) the distance and beraing from your station to the locator. For example:-
+
SH/QRA IO92QL
SH/QRA JN06 IN73
+
The first example will show the distance and bearing to the locator from yourself, the second example will calculate the distance and bearing from the first locator to the second. You can use 4 or 6 character locators. @@ -1787,9 +1923,11 @@ the first locator to the second. You can use 4 or 6 character locators. using this command with a latitude and longitude as an argument, for example:-
+
SH/QRA 52 41 N 0 58 E
+
This command allows you to see to which node the callsigns specified are connected. It is a sort of inverse sh/config.
+
sh/route n2tly
+
Each pass in a period is separated with a row of '-----' characters
So for example:-
+
SH/SAT AO-10
SH/SAT FENGYUN1 12 2
+
For example:-
+
SH/SUN
SH/SUN G1TLH K9CW ZS
+
+
password = 012345678901234567890123456789
> sysop
22 10 15 17 3
+
you type:-
+
aa2bbbb0ccc5ddd7xxx3n
or 2 0 5 7 3
or 20573
+
They will all match. If there is no password you will still be offered numbers but nothing will happen when you input a string. Any match is case sensitive. @@ -1996,15 +2144,19 @@ terminal.
If you want to do something (such as send a spot) you precede the normal command with a '/' character, eg:-
+
/DX 14001 G1TLH What's a B class licensee doing on 20m CW?
/HELP talk
+
To leave talk mode type:
+
/EX
+
+
TYPE bulletins/arld051
+
See also SHOW/FILES to see what fileareas are available and a list of content.