which will arrange for them to be forward candidates again.
Order is not important.
-
clear/announce [input] <callsign> [0-9|all] Clear an announce filter line
+
+
A sysop can clear an input or normal output filter for a user or the +node_default or user_default. +
+
clear/route [input] ^lt;callsign> [0-9|all] Clear a route filter line
+
+
This command allows you to clear (remove) a line in a route filter or to +remove the whole filter. +
see CLEAR/SPOTS for a more detailed explanation. +
A sysop can clear an input or normal output filter for a user or the +node_default or user_default. +
+
clear/spots [1|all] Clear a spot filter line
@@ -405,8 +424,49 @@ remove the whole filter.
the filter will be completely removed.
+
clear/spots [input] <callsign> [0-9|all] Clear a spot filter line
+
+
A sysop can clear an input or normal output filter for a user or the +node_default or user_default. +
+
clear/wcy [1|all] Clear a WCY filter line
+
+
This command allows you to clear (remove) a line in a WCY filter or to +remove the whole filter. +
see CLEAR/SPOTS for a more detailed explanation. +
+
clear/wcy [input] <callsign> [0-9|all] Clear a WCY filter line
+
+
A sysop can clear an input or normal output filter for a user or the +node_default or user_default. +
+
clear/wwv [1|all] Clear a WWV filter line
+
+
This command allows you to clear (remove) a line in a WWV filter or to +remove the whole filter. +
see CLEAR/SPOTS for a more detailed explanation.
-
clear/wwv [input] <callsign> [0-9|all] Clear a WWV filter line
+
+
A sysop can clear an input or normal output filter for a user or the +node_default or user_default. +
+
connect <callsign> Start a connection to another DX Cluster
@@ -416,7 +476,7 @@ DX cluster <callsign>. This process creates a new 'client' process which w
use the script in /spider/connect/<callsign> to effect the 'chat' exchange
necessary to traverse the network(s) to logon to the cluster <callsign>.
-
dbavail Show a list of all the databases in the system
@@ -424,7 +484,7 @@ necessary to traverse the network(s) to logon to the cluster <callsign>.
The title says it all really, this command lists all the databases defined in the system. It is also aliased to SHOW/COMMAND.
-
See DBIMPORT for the importing of existing AK1A format data to databases.
See DBSHOW for generic database enquiry
- will import the standard OBLAST database that comes with AK1A into the
oblast database held locally.
- There is no warning, no comeback, no safety net.
You have been warned.
-dbcreate <name> Create a database entry
@@ -474,7 +534,7 @@ need to add a line like:-
9.20 dbimport (9)
+
9.27 dbimport (9)
dbimport <dbname> Import AK1A data into a database
@@ -486,7 +546,7 @@ database. For example:-
9.21 dbremove (9)
+
9.28 dbremove (9)
dbremove <dbname> Delete a database
@@ -502,7 +562,7 @@ the associated datafile.
9.22 dbshow (0)
+
9.29 dbshow (0)
dbshow <dbname> <key> Display an entry, if it exists, in a database
@@ -526,7 +586,7 @@ SHOW/COMMAND to find out) you can do the same thing with:
-
debug Set the cluster program into debug mode
@@ -541,7 +601,17 @@ in debug mode i.e.
It will interrupt the cluster just after the debug command has finished.
-
delete/user <callsign> Delete a user from the User Database
+
+
This command will completely remove a one or more users from the database. +
There is NO SECOND CHANCE. +
It goes without saying that you should use this command CAREFULLY! +
+
+
directory List messages
directory all List all messages
@@ -578,19 +648,19 @@ or
-
Works just like the user command except that sysops can see ALL messages.
-
disconnect <call> [<call> ...] Disconnect a user or node
Disconnect any <call> connected locally
-
dx [by <call>] <freq> <call> <remarks> Send a DX spot
@@ -623,7 +693,7 @@ of the command and they will be added to the spot.
The <freq> is compared against the available bands set up in the cluster. See SHOW/BANDS for more information.
-
export <msgno> <filename> Export a message to a file
@@ -638,7 +708,7 @@ main cluster, otherwise you can put the new files anywhere the cluster can
access. For example:-
EXPORT 2345 /tmp/a
-
export_users [<filename>] Export the users database to ascii
@@ -651,7 +721,103 @@ suffix.
BE WARNED: this will write to any file you have write access to. No check is made on the filename (if any) that you specify.
-
filtering Filtering things in DXSpider
+
+
There are a number of things you can filter in the DXSpider system. They +all use the same general mechanism. +
In general terms you can create a 'reject' or an 'accept' filter which +can have up to 10 lines in it. You do this using, for example:- +
accept/spots ..... +reject/spots ..... +
where ..... are the specific commands for that type of filter. There +are filters for spots, wwv, announce, wcy and (for sysops) +connects. See each different accept or reject command reference for +more details. +
There is also a command to clear out one or more lines in a filter and +one to show you what you have set. They are:- +
clear/spots 1 +clear/spots all +
and +
show/filter +
There is clear/xxxx command for each type of filter. +
For now we are going to use spots for the examples, but you can apply +the principles to all types of filter. +
There are two main types of filter 'accept' or 'reject'; which you use +depends entirely on how you look at the world and what is least +writing to achieve what you want. Each filter has 10 lines (of any +length) which are tried in order. If a line matches then the action +you have specified is taken (ie reject means ignore it and accept +means gimme it). +
The important thing to remember is that if you specify a 'reject' +filter (all the lines in it say 'reject/spots' (for instance) then if +a spot comes in that doesn't match any of the lines then you will get +it BUT if you specify an 'accept' filter then any spots that don't +match are dumped. For example if I have a one line accept filter:- +
accept/spots on vhf and (by_zone 14,15,16 or call_zone 14,15,16) +
then automatically you will ONLY get VHF spots from or to CQ zones 14 +15 and 16. If you set a reject filter like: +
reject/spots on hf/cw +
Then you will get everything EXCEPT HF CW spots, If you am interested in IOTA +and will work it even on CW then you could say:- +
reject/spots on hf/cw and not info iota +
But in that case you might only be interested in iota and say:- +
accept/spots not on hf/cw or info iota +
which is exactly the same. You should choose one or the other until +you are confortable with the way it works. Yes, you can mix them +(actually you can have an accept AND a reject on the same line) but +don't try this at home until you can analyse the results that you get +without ringing up the sysop for help. +
You can arrange your filter lines into logical units, either for your +own understanding or simply convenience. I have one set frequently:- +
reject/spots 1 on hf/cw +reject/spots 2 on 50000/1400000 not (by_zone 14,15,16 or call_zone 14,15,16) +
What this does is to ignore all HF CW spots (being a class B I can't +read any CW and couldn't possibly be interested in HF :-) and also +rejects any spots on VHF which don't either originate or spot someone +in Europe. +
This is an exmaple where you would use the line number (1 and 2 in +this case), if you leave the digit out, the system assumes '1'. Digits +'0'-'9' are available. +
You can leave the word 'and' out if you want, it is implied. You can +use any number of brackets to make the 'expression' as you want +it. There are things called precedence rules working here which mean +that you will NEED brackets in a situation like line 2 because, +without it, will assume:- +
(on 50000/1400000 and by_zone 14,15,16) or call_zone 14,15,16 +
annoying, but that is the way it is. If you use OR - use +brackets. Whilst we are here CASE is not important. 'And BY_Zone' is +just 'and by_zone'. +
If you want to alter your filter you can just redefine one or more +lines of it or clear out one line. For example:- +
reject/spots 1 on hf/ssb +
or +
clear/spots 1 +
To remove the filter in its entirty:- +
clear/spots all +
There are similar CLEAR commands for the other filters:- +
clear/announce +clear/wcy +clear/wwv +
ADVANCED USERS:- +
Once you are happy with the results you get, you may like to experiment. +
my example that filters hf/cw spots and accepts vhf/uhf spots from EU +can be written with a mixed filter, eg: +
rej/spot on hf/cw +acc/spot on 0/30000 +acc/spot 2 on 50000/1400000 and (by_zone 14,15,16 or call_zone 14,15,16) +
each filter slot actually has a 'reject' slot and an 'accept' +slot. The reject slot is executed BEFORE the accept slot. +
It was mentioned earlier that after a reject test that doesn't match, +the default for following tests is 'accept', the reverse is true for +'accept'. In the example what happens is that the reject is executed +first, any non hf/cw spot is passed to the accept line, which lets +thru everything else on HF. +
The next filter line lets through just VHF/UHF spots from EU. +
+
forward/latlong <node_call> Send latitude and longitude information to another cluster
@@ -663,7 +829,7 @@ means that more locators are given on the DX line assuming you have
set/dxgrid enabled. This could be a LOT of information though, so
it is not recommended on slow links.
-
forward/opername <call> Send out information on this <call> to all clusters
@@ -672,7 +838,7 @@ it is not recommended on slow links.
be broadcast in PC41 protocol packets. This information is Name, QTH, Location
and Homenode. PC41s are only sent for the information that is available.
-
help <cmd> Get help on a command
@@ -683,7 +849,7 @@ to SH/DX, ANNOUNCE can be shortened to AN and so on.
for the <string> you specify and give you a list of likely commands
to look at with HELP.
-
init <node call> Re-initialise a link to an AK1A compatible node
@@ -695,7 +861,7 @@ better, if it is a real AK1A node, doing an RCMD <node> DISC/F <your
node>).
Best of luck - you will need it.
-
kill <msgno> [<msgno> ..] Delete a message from the local system
@@ -704,7 +870,7 @@ node>).
delete messages that you have originated or been sent (unless you are
the sysop).
-
As a sysop you can kill any message on the system.
- This uses the subject field, so any messages that have exactly the same subject
will be deleted. Beware!
-
+ Deleting a message using the normal KILL commands only marks that message
+for deletion. The actual deletion only happens later (usually two days later).
+ The KILL EXPUNGE command causes the message to be truly deleted more or less
+immediately.
+ It otherwise is used in the same way as the KILL command.
+
+
+
-
-
-
+ Reload the /spider/data/badwords file if you have changed it manually whilst
+the cluster is running. This file contains a list of words which, if found
+on certain text portions of PC protocol, will cause those protocol frames
+to be rejected. It will all put out a message if any of these words are
+used on the announce, dx and talk commands. The words can be one or
+more on a line, lines starting with '#' are ignored.
+
+ Reload the /spider/data/bands.pl file if you have changed it manually whilst
the cluster is running.
-
- Reload the /spider/msg/forward.pl file if you have changed it
manually whilst the cluster is running.
- unknown message 'xxxx' in lang 'en'
- Reload the /spider/data/prefix_data.pl file if you have changed it manually
whilst the cluster is running.
-
- STAT/MSG <msgno>
This will display more information on the message than DIR does.
- pc G1TLH Try doing that properly!!!
-
-
-
-
As a sysop you may read any message on the system
- but this probably for advanced users...
-
-kill <msgno> [<msgno> ...] Remove or erase a message from the system
@@ -715,7 +881,7 @@ the sysop).
this command. You can remove more than one message at a time.
9.36 kill full (5)
+
9.45 kill full (5)
kill full <msgno> [<msgno>] Delete a message from the whole cluster
@@ -724,7 +890,19 @@ this command. You can remove more than one message at a time.
9.37 links (0)
+
9.46 kill/expunge (6)
+
+
+kill/expunge <msgno> [<msgno>..]Expunge a message
+9.47 links (0)
links Show which nodes are physically connected
@@ -733,7 +911,7 @@ will be deleted. Beware!
some information about them. See WHO for a list of all connections.
9.38 load/aliases (9)
+
9.48 load/aliases (9)
load/aliases Reload the command alias table
@@ -742,7 +920,7 @@ some information about them. See WHO for a list of all connections.
do this if you change this file whilst the cluster is running in order for the
changes to take effect.
9.39 load/badmsg (9)
+
9.49 load/badmsg (9)
load/badmsg Reload the bad message table
@@ -752,7 +930,19 @@ the cluster is running. This table contains a number of perl regular
expressions which are searched for in the fields targetted of each message.
If any of them match then that message is immediately deleted on receipt.
9.40 load/bands (9)
+
9.50 load/badwords (9)
+
+
+load/badwords Reload the bad words table
+9.51 load/bands (9)
load/bands Reload the band limits table
@@ -760,7 +950,7 @@ If any of them match then that message is immediately deleted on receipt.
9.41 load/cmd_cache (9)
+
9.52 load/cmd_cache (9)
load/cmd_cache Reload the automatic command cache
@@ -771,14 +961,14 @@ if you are doing a lot of moving commands about or delete a command in the
local_cmd tree and want to use the normal one again. Execute this command to
reset everything back to the state it was just after a cluster restart.
9.42 load/forward (9)
+
9.53 load/forward (9)
load/forward Reload the msg forwarding routing table
9.43 load/messages (9)
+
9.54 load/messages (9)
load/messages Reload the system messages file
@@ -788,7 +978,7 @@ commands) you can have them take effect during a cluster session by executing th
command. You need to do this if get something like :-
9.44 load/prefixes (9)
+
9.55 load/prefixes (9)
load/prefixes Reload the prefix table
@@ -796,7 +986,7 @@ command. You need to do this if get something like :-
9.45 merge (5)
+
9.56 merge (5)
merge <node> [<no spots>/<no wwv>] Ask for the latest spots and WWV
@@ -808,7 +998,7 @@ node must be connected locally.
to your databases they will not duplicate any that have recently been added
(the last 2 days for spots and last month for WWV data).
9.46 msg (9)
+
9.57 msg (9)
msg <cmd> <msgno> [data ...] Alter various message parameters
@@ -839,7 +1029,7 @@ out.
9.47 pc (8)
+
9.58 pc (8)
pc <call> <text> Send text (eg PC Protocol) to <call>
@@ -852,7 +1042,7 @@ arise (messages get stuck etc). eg:-
without any processing, added of "from <blah> to <blah>" or whatever.
9.48 ping (1)
+
9.59 ping (1)
ping <node> Check the link quality between nodes
@@ -864,7 +1054,7 @@ it takes is output to the console in seconds.
Any visible cluster node can be PINGed.
9.49 rcmd (1)
+
9.60 rcmd (1)
rcmd <node call> <cmd> Send a command to another DX cluster
@@ -876,7 +1066,7 @@ that the node callsign of this cluster is in fact a node b) whether the
other system is allowing RCMDs from this node and c) whether you have
permission to send this command at all.
9.50 read (0)
+
9.61 read (0)
read Read the next unread personal message addressed to you
@@ -886,14 +1076,14 @@ permission to send this command at all.
message either sent by or sent to your callsign.
9.51 read (extended for sysops) (5)
+
9.62 read (extended for sysops) (5)
read <msgno> Read a message on the system
9.52 reject/announce
+
9.63 reject/announce
reject/announce [0-9] <pattern> Set a reject filter
@@ -937,7 +1127,7 @@ to understand how filters work - it will save a lot of grief later on.
9.53 reject/announce (extended for sysops) (8)
+
9.64 reject/announce (extended for sysops) (8)
reject/announce <call> [input] [0-9] <pattern> Announce filter sysop version
@@ -953,7 +1143,7 @@ default for nodes and users eg:-
9.54 reject/route (8)
+
9.65 reject/route (8)
reject/route <call> [0-9] <pattern> Set an 'reject' filter line for routing
@@ -994,7 +1184,7 @@ You can use any of the following things in this line:-
-
reject/spots [0-9] <pattern> Set a reject filter line for spots
@@ -1044,7 +1234,7 @@ too hung up about that)
but this probably for advanced users...
-
reject/spots <call> [input] [0-9] <pattern>
@@ -1063,7 +1253,7 @@ default for nodes and users eg:-
-
reject/wcy [0-9] <pattern> Set a reject WCY filter
@@ -1089,7 +1279,7 @@ you either want them or not (see UNSET/WCY if you don't want them).
This command is really provided for future use.
See HELP FILTER for information.
-
reject/wcy <call> [input] [0-9] <pattern>
@@ -1099,7 +1289,7 @@ WCY reject filter sysop version
default for nodes and users eg:-
reject/wcy gb7djk all
-
reject/wwv [0-9] <pattern> Set a reject WWV filter
@@ -1131,7 +1321,7 @@ filter on the following fields:-
by stations in the US).
See HELP FILTER for information.
-
reject/wwv <call> [input] [0-9] <pattern>
@@ -1149,7 +1339,7 @@ default for nodes and users eg:-
-
- SB is an alias for SEND NOPRIVATE (or send a bulletin in BBS speak)
SP is an alias for SEND PRIVATE
-
Literally, record your address details on the cluster.
-
Allow announce messages to arrive at your terminal.
-
Set the node_call as an AR-Cluster type node
-
- will allow spots from him again.
Use with extreme care. This command may well be superceded by FILTERing.
- will allow spots from him again.
Use with extreme care. This command may well be superceded by FILTERing.
-
+ Setting a word as a 'badword' will prevent things like spots,
+announces or talks with this word in the the text part from going any
+further. They will not be displayed and they will not be sent onto
+other nodes.
+ The word must be written in full, no wild cards are allowed eg:-
+ set/badword annihilate annihilated annihilation
+ will stop anything with these words in the text.
+ unset/badword annihilated
+ will allow text with this word again.
+
+
+
Add a beep to DX and other terminal messages.
-
-
Set the node_call as a CLX type node
- You can remove a debug level with unset/debug <name>
-
You can stop DX messages with the unset/dx command
-
-
Set the node_call as a DXNet type node
- The setting is stored in your user profile.
YOU DO NOT NEED TO USE THIS COMMAND IF YOU ARE CONNECTED VIA AX25.
-
+ If any personal messages come in for your callsign then you can use
+these commands to control whether they are forwarded onto your email
+address. To enable the forwarding do something like:-
+ SET/EMAIL mike.tubby@somewhere.com
+ You can have more than one email address (each one separated by a space).
+Emails are forwarded to all the email addresses you specify.
+ You can disable forwarding by:-
+ UNSET/EMAIL
+
+
- Set SHOW/HOPS for information on what is already set. This command
creates a filter and works in conjunction with the filter system.
- You can see which nodes are isolated with the show/isolate (1) command.
You can remove the isolation with the command unset/isolate.
- You can select the language that you want the cluster to use. Currently
the languages available are en (English) and nl (Dutch).
-
-
-
- You can show who is locked out with the show/lockout command.
To allow the user to connect again, use the unset/lockout command.
-reply Reply (privately) to the last message that you have read
@@ -1165,7 +1355,7 @@ message
NOPRIVATE, B that you can use with the SEND command (see SEND
for further details)
9.62 send (0)
+
9.73 send (0)
send <call> [<call> ...] Send a message to one or more callsigns
@@ -1192,21 +1382,21 @@ receive a read receipt when they have read the message.
9.63 set/address (0)
+
9.74 set/address (0)
set/address <your_address> Record your postal address
9.64 set/announce (0)
+
9.75 set/announce (0)
set/announce Allow announce messages
9.65 set/arcluster (5)
+
9.76 set/arcluster (5)
set/arcluster <node_call> [<node_call> ...] Make
@@ -1214,7 +1404,7 @@ the node_call an AR-Cluster type node
9.66 set/baddx (8)
+
9.77 set/baddx (8)
set/baddx <call> Stop words we do not wish to see in the callsign field
@@ -1238,7 +1428,7 @@ will not be sent onto other nodes.
9.67 set/badnode (6)
+
9.78 set/badnode (6)
set/badnode <node_call> Stop spots from this node_call
@@ -1264,7 +1454,7 @@ sent onto other nodes.
9.68 set/badspotter (8)
+
9.79 set/badspotter (8)
set/badspotter <call> Stop spots from this callsign being propagated
@@ -1290,19 +1480,35 @@ enter them specifically.
9.69 set/beep (0)
+
9.80 set/badword (8)
+
+
+set/badword <word> Stop things with this word being propogated
+9.81 set/beep (0)
set/beep Add beeps to terminal messages
9.70 set/bbs (5)
+
9.82 set/bbs (5)
set/bbs <call> [<call>..]Make <call> a BBS
9.71 set/clx (5)
+
9.83 set/clx (5)
set/clx <node_call> [<node_call> ...] Make
@@ -1310,7 +1516,7 @@ the node_call a CLX type node
9.72 set/debug (9)
+
9.84 set/debug (9)
set/debug <name> Add a debug level to the debug set
@@ -1325,14 +1531,14 @@ connect
command.
9.73 set/dx (0)
+
9.85 set/dx (0)
set/dxAllow DX messages to arrive at your terminal
9.74 set/dxgrid (0)
+
9.86 set/dxgrid (0)
set/dxgridAllow grid squares on the end of DX messages
@@ -1341,7 +1547,7 @@ command.
the end of a DX spot. If this is the case, use the unset/dxgrid
command to remove the grid squares.
9.75 set/dxnet (5)
+
9.87 set/dxnet (5)
set/dxnet <node_call> [<node_call> ...] Make
@@ -1349,7 +1555,7 @@ the node_call a DXNet type node
9.76 set/echo (0)
+
9.88 set/echo (0)
set/echo Make the cluster echo your input
@@ -1362,7 +1568,21 @@ to change the setting appropriately.
9.77 set/here (0)
+
9.89 set/email (0)
+
+
+set/email <email_address> Set email address(es) and forward your personals
+9.90 set/here (0)
set/here Set the here flag
@@ -1372,7 +1592,7 @@ callsign. If you are away from your terminal you can use the unset/here
-9.78 set/homenode (0)
+
9.91 set/homenode (0)
set/homenode <node_call> Set your home cluster
@@ -1387,7 +1607,7 @@ eg:-
9.79 set/hops (8)
+
9.92 set/hops (8)
set/hops <node_call> ann|spots|wwv|wcy <n>
@@ -1407,7 +1627,7 @@ eg:
9.80 set/isolate (9)
+
9.93 set/isolate (9)
set/isolate <node call> Isolate a node from the rest of the network
@@ -1419,7 +1639,7 @@ out from it nor goes back into from the rest of the nodes connected to you.
9.81 set/language (0)
+
9.94 set/language (0)
set/language <language> Set the language you wish to use
@@ -1427,7 +1647,7 @@ out from it nor goes back into from the rest of the nodes connected to you.
9.82 set/location (0)
+
9.95 set/location (0)
set/location <lat and long> Set your latitude and longitude
@@ -1442,7 +1662,7 @@ the languages available are en (English) and nl (Dutch).
9.83 set/sys_location (9)
+
9.96 set/sys_location (9)
set/sys_location <lat & long> Set your cluster latitude and longitude
@@ -1457,7 +1677,7 @@ then this command will set your QRA locator for you. For example:-
9.84 set/logininfo (0)
+
9.97 set/logininfo (0)
set/logininfo Show logins and logouts of nodes and users
@@ -1466,7 +1686,7 @@ then this command will set your QRA locator for you. For example:-
can stop these messages by using the unset/logininfo command.
9.85 set/lockout (9)
+
9.98 set/lockout (9)
set/lockout <call> Stop a callsign connecting to the cluster
@@ -1474,7 +1694,7 @@ can stop these messages by using the unset/logininfo command.
9.86 set/name (0)
+
9.99 set/name (0)
set/name <your_name> Set your name
@@ -1487,7 +1707,7 @@ To allow the user to connect again, use the unset/lockout command.
-
set/node <call> [<call> ...] Make the callsign an AK1A cluster
@@ -1506,7 +1726,7 @@ fed PC Protocol rather normal user commands.
To see what your nodes are set to, use the show/nodes command.
-
set/obscount <count> <node call> Set the 'pump-up' obsolescence counter
@@ -1523,7 +1743,7 @@ what would be the third attempt, that node is disconnected.
default values, if a node has not responded to a ping within 15 minutes,
it is disconnected.
-
set/page <n> Set the number of lines per page
@@ -1540,19 +1760,39 @@ explicitly to 0 will disable paging.
The setting is stored in your user profile.
+
set/password Set your own password
+
+
This command only works for a 'telnet' user (currently). It will +only work if you have a password already set. This initial password +can only be set by the sysop. +
When you execute this command it will ask you for your old password, +then ask you to type in your new password twice (to make sure you +get it right). You may or may not see the data echoed on the screen +as you type, depending on the type of telnet client you have.
-
set/password <callsign> <string> Set a users password
The password for a user can only be set by a full sysop. The string -can contain any characters but any spaces are removed (you can type in -spaces - but they won't appear in the password). You can see the -result with STAT/USER. The password is the usual 30 character baycom -type password. -
-
The way this field is used depends on context. If it is being used in +the SYSOP command context then you are offered 5 random numbers and you +have to supply the corresponding letters. This is now mainly for ax25 +connections. +
If it is being used on incoming telnet connections then, if a password +is set or the: +
set/var $main::passwdreq = 1 +
command is executed in the startup script, then a password prompt is +given after the normal 'login: ' prompt. +
The command "unset/password" is provided to allow a sysop to remove a +users password completely in case a user forgets or loses their password. +
+
set/pinginterval <time> <node call> Set the ping time to neighbouring nodes
@@ -1567,7 +1807,7 @@ for numbers greater than that.
(as certain cluster software doesn't always notice), see SET/OBSCOUNT
for more information.
-
set/privilege <n> <call> [<call> ...] Set the privilege level on a call
@@ -1589,7 +1829,7 @@ to commands are as default:-
If you are a sysop and you come in as a normal user on a remote connection your privilege will automatically be set to 0.
-
set/spider <node_call> [<node_call> ...] Make
@@ -1597,12 +1837,12 @@ the node_call a DXSpider type node
Set the node_call as a DXSpider type node
-
set/sys_qra <locator> Set your cluster QRA locator
-
set/qra <locator> Set your QRA locator
@@ -1617,7 +1857,7 @@ correctly (assuming your locator is correct ;-). For example:-
-
set/qth <your QTH> Set your QTH
@@ -1630,7 +1870,24 @@ correctly (assuming your locator is correct ;-). For example:-
-
set/register <call> Mark a user as registered
+
+
Registration is a concept that you can switch on by executing the +
set/var $main::regreq = 1 +
command (usually in your startup file) +
If a user is NOT registered then, firstly, instead of the normal +motd file (/spider/data/motd) being sent to the user at startup, the +user is sent the motd_nor file instead. Secondly, the non registered +user only has READ-ONLY access to the node. The non-registered user +cannot use DX, ANN etc. +
The only exception to this is that a non-registered user can TALK or +SEND messages to the sysop. +
To unset a user use the 'unset/register' command +
+
set/talk Allow talk messages to be seen at your console
@@ -1638,7 +1895,7 @@ correctly (assuming your locator is correct ;-). For example:-
Allow talk messages to arrive at your console. You can switch off talks with the unset/talk command.
-
set/wcy Allow WCY messages to be seen at your console
@@ -1646,7 +1903,7 @@ talks with the unset/talk command.
Allow WCY information to be seen at your console. You can switch off WCY messages with the unset/wcy command.
-
set/wwv Allow WWV messages to be seen at your console
@@ -1654,7 +1911,7 @@ WCY messages with the unset/wcy command.
Allow WWV information to be seen at your console. You can switch off WWV messages with the unset/wwv command.
-
set/wx Allow WX messages to be seen at your console
@@ -1662,7 +1919,7 @@ WWV messages with the unset/wwv command.
Allow WX information to be seen at your console. You can switch off WX messages with the unset/wx command.
-
show/baddxShow all the bad dx calls in the system
@@ -1670,7 +1927,7 @@ WX messages with the unset/wx command.
Display all the bad dx callsigns in the system, see SET/BADDX for more information.
-
show/badnode Show all the bad nodes in the system
@@ -1678,7 +1935,7 @@ for more information.
Display all the bad node callsigns in the system, see SET/BADNODE for more information.
-
show/badspotter Show all the bad spotters in the system
@@ -1686,7 +1943,15 @@ for more information.
Display all the bad spotter's callsigns in the system, see SET/BADSPOTTER for more information.
-
show/badword Show all the bad words in the system
+
+
Display all the bad words in the system, see SET/BADWORD +for more information. +
+
show/configuration [<node>] Show all visible nodes and their users
@@ -1697,14 +1962,14 @@ you can specify a particular node to look at.
This command is normally abbreviated to: sh/c
BE WARNED: the list that is returned can be VERY long
-
show/configuration/node Show all the nodes connected
Show all the nodes connected locally and the nodes they have connected.
-
show/connect Show all the active connections
@@ -1712,7 +1977,7 @@ you can specify a particular node to look at.
This command shows information on all the active connections known to the node. This command gives slightly more information than WHO.
-
-
The levels can be set with set/debug
-show/date [<prefix>|<callsign>] Show
@@ -1725,14 +1990,14 @@ time and UTC as the computer has it right now. If you give some prefixes
then it will show UTC and UTC + the local offset (not including DST) at
the prefixes or callsigns that you specify.
9.108 show/debug (9)
+
9.124 show/debug (9)
show/debug Show what levels of debug you are logging
9.109 show/dx (0)
+
9.125 show/dx (0)
show/dx [options] interrogate the spot database
@@ -1791,7 +2056,7 @@ qra [<locator>] - this will look for the specific locator if
-
show/dxcc <prefix> Interrogate the spot database by country
@@ -1810,7 +2075,15 @@ e.g.
-
sh/dxstats Show the DX Statistics for last 31 days
+
+
Show the total DX spots for the last 31 days +
+
+
show/files [<filearea> [<string>]] List
@@ -1837,7 +2110,7 @@ string to see a selection of files in a filearea eg:-
See also TYPE - to see the contents of a file.
-
show/filter Show the filters you have set
@@ -1845,14 +2118,28 @@ string to see a selection of files in a filearea eg:-
Show the contents of all the filters that are set by you. This command displays all the filters set - for all the various categories.
-
show/filter <callsign> Show the filters set by <callsign>
A sysop can look at any filters that have been set.
-
show/hfstats Show the HF DX Statistics for last 31 days
+
+
Show the HF DX spots breakdown by band for the last 31 days +
+
show/hftable Show the HF DX Spotter Table for your country
+
+
Show the HF DX Spotter table for your country for the last 31 days +
+
show/hops <node_call> [ann|spots|wcy|wwv|] Show the hop counts for a node
@@ -1861,14 +2148,14 @@ displays all the filters set - for all the various categories.
which category you want to see. If you leave the category out then
all the categories will be listed.
-
show/isolate Show a list of isolated nodes
Show which nodes are currently set to be isolated.
-
show/lockout Show a list of excluded callsigns
@@ -1876,7 +2163,7 @@ all the categories will be listed.
Show a list of callsigns that have been excluded (locked out) of the cluster locally with the set/lockout command
-
show/log [<callsign>] Show excerpts from the system log
@@ -1885,7 +2172,7 @@ cluster locally with the set/lockout command
it will output a general logfile. With the optional callsign it will
show output from the log associated with that callsign.
-
show/moon [<prefix>|<callsign>] Show moon
@@ -1910,7 +2197,7 @@ that you are connected to.
-
show/muf <prefix> [<hours>][long] Show
@@ -1967,7 +2254,7 @@ hours required after the prefix. For example:-
indicating that you will have weak, fading circuits on top band and 80m but usable signals on 40m (about S3). -
inputing:- +
inputting:-
@@ -1987,7 +2274,28 @@ propagation data.
should be noted that the figures will probably not be very useful, nor
terrible accurate, but it is included for completeness.
-
9.120 show/node (1)
+9.139 show/newconfiguration (0)
+
+
+
show/newconfiguration [<node>] Show all the nodes and users visible
+
+
This command allows you to see all the users that can be seen
+and the nodes to which they are connected.
+
This command produces essentially the same information as
+SHOW/CONFIGURATION except that it shows all the duplication of
+any routes that might be present It also uses a different format
+which may not take up quite as much space if you don't have any
+loops.
+
BE WARNED: the list that is returned can be VERY long
+
+
9.140 show/newconfiguration/node (0)
+
+
+show/newconfiguration/node Show all the nodes connected locally
+
+
Show all the nodes connected to this node in the new format.
+
+
9.141 show/node (1)
show/node [<node_call> ...] Show the type and version
@@ -1997,7 +2305,7 @@ number of nodes
command line. If no callsigns are specified then a sorted list of all
the non-user callsigns known to the system will be displayed.
-
9.121 show/prefix (0)
+9.142 show/prefix (0)
show/prefix <callsign> Interrogate the prefix database
@@ -2009,7 +2317,7 @@ together with the internal country no, the CQ and ITU regions.
See also SHOW/DXCC
-
9.122 show/program (5)
+9.143 show/program (5)
show/program Show the locations of all the included program modules
@@ -2017,7 +2325,7 @@ together with the internal country no, the CQ and ITU regions.
Show the name and location where every program module was load from. This
is useful for checking where you think you have loaded a .pm file from.
-
9.123 show/qra (0)
+9.144 show/qra (0)
show/qra <locator> [<locator>] Show the distance
@@ -2048,7 +2356,7 @@ SH/QRA 52 41 N 0 58 E
-
show/qrz <callsign> Show any callbook details on a callsign
@@ -2057,7 +2365,12 @@ SH/QRA 52 41 N 0 58 E
and returns any information available for that callsign. This service
is provided for users of this software by http://www.qrz.com
-
show/registered [<prefix>[ Show the registered users
+
+
show/route <callsign> Show the route to <callsign>
@@ -2071,7 +2384,7 @@ connected. It is a sort of inverse sh/config.
-
show/satellite <name> [<hours> <interval>]
@@ -2096,7 +2409,7 @@ SH/SAT FENGYUN1 12 2
-
show/sun [<prefix>|<callsign>] Show
@@ -2119,7 +2432,7 @@ that you are connected to.
-
-
+ Show the VHF DX spots breakdown by band for the last 31 days
+
+
+ Show the VHF DX Spotter table for your country for the last 31 days
+
+
Display the most recent WCY information that has been received by the system
- Display the most recent WWV information that has been received by the system
- Shutdown the cluster and disconnect all the users. If you have Spider
set to respawn in /etc/inittab it will of course restart.
-
- Depending on your privilege level you will see more or less information.
This command is unlikely to be of much use to anyone other than a sysop.
- Only the fields that are defined (in perl term) will be displayed.
- If no message number is given then the status of the message system is
displayed.
-
-
- Only the fields that are defined (in perl term) will be displayed.
-
-
- See also SHOW/FILES to see what fileareas are available and a
list of content.
- This is a quick listing that shows which callsigns are connected and
what sort of connection they have
- Weather messages can sometimes be useful if you are experiencing an extreme
that may indicate enhanced conditions
-show/time [<prefix>|<callsign>] Show
@@ -2130,7 +2443,21 @@ time and UTC as the computer has it right now. If you give some prefixes
then it will show UTC and UTC + the local offset (not including DST) at
the prefixes or callsigns that you specify.
9.129 show/wcy (0)
+
9.151 show/vhfstats (0)
+
+
+show/vhfstats Show the VHF DX Statistics for last 31 days
+9.152 show/vhftable (0)
+
+
+show/vhftable Show the VHF DX Spotter Table for your country
+9.153 show/wcy (0)
show/wcy Show the last 10 WCY broadcasts
@@ -2138,7 +2465,7 @@ the prefixes or callsigns that you specify.
9.130 show/wwv (0)
+
9.154 show/wwv (0)
show/wwv Show the last 10 WWV broadcasts
@@ -2147,7 +2474,7 @@ the prefixes or callsigns that you specify.
9.131 shutdown (5)
+
9.155 shutdown (5)
shutdown Shutdown the cluster
@@ -2155,7 +2482,7 @@ the prefixes or callsigns that you specify.
9.132 spoof (9)
+
9.156 spoof (9)
spoof <callsign> <command> Run commands as another user
@@ -2165,7 +2492,7 @@ issue commands as if you were a different user. This is very useful for the
kind of things that users seem to always get wrong.. like home_node for
example.
9.133 stat/db (5)
+
9.157 stat/db (5)
stat/db <dbname> Show the status of a database
@@ -2174,7 +2501,7 @@ example.
9.134 stat/channel (5)
+
9.158 stat/channel (5)
stat/channel <callsign> Show the status of a channel on the cluster
@@ -2183,7 +2510,7 @@ This command is unlikely to be of much use to anyone other than a sysop.
you are on or else for the callsign that you asked for.
9.135 stat/msg (5)
+
9.159 stat/msg (5)
stat/msg <msgno> Show the status of a message
@@ -2194,17 +2521,17 @@ such as to whom it has been forwarded, its size, origin etc etc.
9.136 stat/route_node (5)
+
9.160 stat/route_node (5)
stat/route_node <callsign> Show the data in a Route::Node object
9.137 stat/route_user (5)
+
9.161 stat/route_user (5)
stat/route_user <callsign> Show the data in a Route::User object
9.138 stat/user (5)
+
9.162 stat/user (5)
stat/user <callsign> Show the full status of a user
@@ -2213,7 +2540,7 @@ displayed.
and stuff.
9.139 sysop (0)
+
9.163 sysop (0)
sysop Regain your privileges if you login remotely
@@ -2249,7 +2576,7 @@ these values are for explanation :-):
numbers but nothing will happen when you input a string. Any match is
case sensitive.
9.140 talk (0)
+
9.164 talk (0)
talk <callsign> Enter talk mode with <callsign>
@@ -2290,7 +2617,7 @@ command with a '/' character, eg:-
9.141 type (0)
+
9.165 type (0)
type <filearea>/<name> Look at a file in one of the fileareas
@@ -2307,7 +2634,7 @@ enter:-
9.142 who (0)
+
9.166 who (0)
who Show who is physically connected locally
@@ -2315,7 +2642,7 @@ list of content.
9.143 wx (0)
+
9.167 wx (0)
wx <text> Send a weather message to local users
@@ -2324,7 +2651,7 @@ what sort of connection they have
9.144 wx (enhanced for sysops) (5)
+
9.168 wx (enhanced for sysops) (5)
wx sysop <text> Send a weather message to other clusters only