Search the help database for <string> (it isn't case sensitive), and print
the names of all the commands that may be relevant.
+=== 0^BLANK [<string>] [<nn>]^Print nn (default 1) blank lines (or strings)
+In its basic form this command prints one or more blank lines. However if
+you pass it a string it will replicate the string for the width of the
+screen (default 80) and then print that one or more times, so:
+
+ blank 2
+
+prints two blank lines
+
+ blank -
+
+prints a row of - characters once.
+
+ blank abc
+
+prints 'abcabcabcabcabcabc....'
+
+This is really only of any use in a script file and you can print a maximum
+of 9 lines.
+
=== 0^BYE^Exit from the cluster
This will disconnect you from the cluster
Best of luck - you will need it.
=== 0^KILL <msgno> [<msgno..]^Delete a message from the local system
+=== 0^KILL <from msgno>-<to msgno>^Delete a range of messages
+=== 0^KILL from <regex>^Delete messages FROM a callsign or pattern
+=== 0^KILL to <regex>^Delete messages TO a callsign or pattern
+=== 5^KILL FULL <msgno> [<msgno..]^Delete a message from the whole cluster
Delete a message from the local system. You will only be able to
delete messages that you have originated or been sent (unless you are
-the sysop).
+the sysop).
-=== 5^KILL FULL <msgno> [<msgno..]^Delete a message from the whole cluster
-Delete a message (usually a 'bulletin') from the whole cluster system.
+ KILL 1234-1255
+
+Will delete all the messages that you own between msgnos 1234 and 1255.
+
+ KILL from g1tlh
+
+will delete all the messages from g1tlh (if you are g1tlh). Similarly:
+
+ KILL to g1tlh
+
+will delete all messages to g1tlh.
+
+ KILL FULL 1234
+
+will 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!
+=== 6^KILL EXPunge <msgno> [<msgno..]^Expunge a message
+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.
+
=== 0^LINKS^Show which nodes is physically connected
This is a quick listing that shows which links are connected and
some information about them. See WHO for a list of all connections.
=== 0^SET/ANNOUNCE^Allow announce messages to come out on your terminal
=== 0^UNSET/ANNOUNCE^Stop announce messages coming out on your terminal
+=== 0^SET/ANNTALK^Allow talk like announce messages on your terminal
+=== 0^UNSET/ANNTALK^Stop talk like announce messages on your terminal
+The announce system on legacy cluster nodes is used as a talk
+substitute because the network is so poorly connected. If you:
+
+ unset/anntalk
+
+you will suppress several of these announces, you may miss the odd
+useful one as well, but you would probably miss them anyway in the
+welter of useless ones.
+
+ set/anntalk
+
+allows you to see them again. This is the default.
+
=== 5^SET/ARCLUSTER <call> [<call>..]^Make the callsign an AR-Cluster node
-=== 8^SET/BADDX <call>..^Stop words we do not wish to see in the callsign field
-of a dx spot being propagated
-=== 8^UNSET/BADDX <call>..^Allow a word to be seen again in a DX spot
-Setting a word as 'baddx' will prevent spots with that word in the
-callsign field of a DX spot from going any further. They will not be
-displayed and they will not be sent onto other nodes.
+=== 8^SET/BADDX <call>..^Stop callsigns in a dx spot being propagated
+=== 8^UNSET/BADDX <call>..^Propagate a dx spot with this callsign again
+Setting a word as 'baddx' will prevent spots with that word in the
+'spotted' field (as in: DX 14001.1 FR0G)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:-
+The word must be written in full, no wild cards are allowed eg:-
set/baddx FORSALE VIDEO FR0G
Use with extreme care. This command may well be superceded by FILTERing.
+=== 8^SET/BADWORD <word>..^Stop things with this word being propagated
+=== 8^UNSET/BADWORD <word>..^Propagate things with this word again
+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.
+
=== 0^SET/BEEP^Add a beep to DX and other messages on your terminal
=== 0^UNSET/BEEP^Stop beeps for DX and other messages on your terminal
eg:-
SET/HOMENODE gb7djk
-=== 8^SET/HOPS <call> ann|spots|wwv|wcy <n>^Set hop count
+=== 8^SET/HOPS <call> ann|spots|route|wwv|wcy <n>^Set hop count
Set the hop count for a particular type of broadcast for a node.
This command allows you to set up special hop counts for a node
either logout and login again (if you are on a console) or use the
SYSOP command.
+=== 0^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.
+
=== 9^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.
+can contain any characters.
+
+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.
+
+=== 9^UNSET/PASSWORD <call> ...^Delete (remove) a user's password
+This command allows the sysop to completely delete and remove a
+password for a user.
=== 5^SET/SPIDER <call> [<call>..]^Make the callsign an DXSpider node
Tell the system that the call(s) are to be treated as DXSpider node and
Tell the system where you are. For example:-
SET/QTH East Dereham, Norfolk
+=== 9^SET/REGISTER <call> ...^Mark a user as registered
+=== 9^UNSET/REGISTER <call> ...^Mark a user as not 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.
+
=== 0^SET/TALK^Allow TALK messages to come out on your terminal
=== 0^UNSET/TALK^Stop TALK messages coming out on your terminal
Display all the bad spotter's callsigns in the system, see SET/BADSPOTTER
for more information.
+=== 1^SHOW/BADWORD^Show all the bad words in the system
+Display all the bad words in the system, see SET/BADWORD
+for more information.
+
=== 0^SHOW/CONFIGURATION [<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.
=== 0^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
-=== 8^SHOW/HOPS <call> [ann|spots|wcy|wwv]^Show the hop counts for a node
+=== 8^SHOW/HOPS <call> [ann|spots|route|wcy|wwv]^Show the hop counts for a node
This command shows the hop counts set up for a node. You can specify
which category you want to see. If you leave the category out then
all the categories will be listed.
=== 1^SHOW/ISOLATE^Show list of ISOLATED nodes
-=== 9^SHOW/LOCKOUT^Show the list of locked out or excluded callsigns
+=== 9^SHOW/LOCKOUT <prefix>|ALL^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
SH/MOON
SH/MOON G1TLH W5UN
+You can also use this command to see into the past or the future, so
+if you want to see yesterday's times then do:-
+
+ SH/MOON -1
+
+or in three days time:-
+
+ SH/MOON +3 W9
+
=== 0^SHOW/MUF <prefix> [<hours>][long]^Show the likely propagation to a prefix
This command allow you to estimate the likelihood of you contacting
a station with the prefix you have specified. The output assumes a modest
should be noted that the figures will probably not be very useful, nor
terrible accurate, but it is included for completeness.
+=== 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
+
+=== 0^SHOW/NEWCONFIGURATION/NODE^Show all the nodes connected locally
+Show all the nodes connected to this node in the new format.
+
=== 1^SHOW/NODE [<callsign> ...]^Show the type and version number of nodes
Show the type and version (if connected) of the nodes specified on the
command line. If no callsigns are specified then a sorted list of all
and returns any information available for that callsign. This service
is provided for users of this software by http://www.qrz.com
+=== 9^SHOW/REGISTERED [<prefix>]^Show the registered users
+
=== 0^SHOW/ROUTE <callsign> ...^Show the route to the callsign
This command allows you to see to which node the callsigns specified are
connected. It is a sort of inverse sh/config.
If no callsign is given then show the information for yourself.
-=== 0^SHOW/SUN [<prefix>|<callsign>]^Show sun rise and set times
+=== 0^SHOW/SUN [
+/- days][<prefix>|<callsign>]^Show sun rise and set times
Show the sun rise and set times for a (list of) prefixes or callsigns,
together with the azimuth and elevation of the sun currently at those
locations.
SH/SUN
SH/SUN G1TLH K9CW ZS
+You can also use this command to see into the past or the future, so
+if you want to see yesterday's times then do:-
+
+ SH/SUN -1
+
+or in three days time:-
+
+ SH/SUN +3 W9
+
=== 0^SHOW/TIME [<prefix>|<callsign>]^Show the local time
If no prefixes or callsigns are given then this command returns the local
time and UTC as the computer has it right now. If you give some prefixes
projects / spider.git / blobdiff