The <freq> is compared against the available bands set up in the
cluster. See SHOW/BANDS for more information.
+=== 0^ECHO <line>^Echo the line to the output
+This command is useful in scripts and so forth for printing the
+line that you give to the command to the output. You can use this
+in user_default scripts and the SAVE command for titling and so forth
+
+The script will interpret certain standard "escape" sequences as follows:-
+
+ \t - becomes a TAB character (0x09 in ascii)
+ \a - becomes a BEEP character (0x07 in ascii)
+ \n - prints a new line
+
+So the following example:-
+
+ echo GB7DJK is a dxcluster
+
+produces:-
+
+ GB7DJK is a dxcluster
+
+on the output. You don't need a \n on the end of the line you want to send.
+
+A more complex example:-
+
+ echo GB7DJK\n\tg1tlh\tDirk\n\tg3xvf\tRichard
+
+produces:-
+
+ GB7DJK
+ g1tlh Dirk
+ g3xvf Richard
+
+on the output.
+
=== 9^EXPORT <msgno> <filename>^Export a message to a file
Export a message to a file. This command can only be executed on a local
console with a fully privileged user. The file produced will be in a form
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.
Reload the /spider/msg/forward.pl file if you have changed it
manually whilst the cluster is running.
+=== 5^LOAD/KEPS^Load new keps data
+=== 5^LOAD/KEPS [nn]^Load new keps data from message
+If there is no message number then reload the current Keps data from
+the Keps.pm data file. You create this file by running
+
+ /spider/perl/convkeps.pl <filename>
+
+on a file containing NASA 2 line keps as a message issued by AMSAT.
+
+If there is a message number, then it will take the message, run
+convkeps.pl on it and then load the data, all in one step.
+
+These messages are sent to ALL by GB7DJK (and others) from time to time.
+
=== 9^LOAD/MESSAGES^Reload the system messages file
If you change the /spider/perl/Messages file (usually whilst
fiddling/writing new commands) you can have them take effect during a
NOPRIVATE, B that you can use with the SEND command (see SEND
for further details)
+=== 9^SAVE [-d -t -a] <filename> "<cmd>" [...]^Save command output to a file
+This sysop only cammand allows you to save the output of one or more
+commands to a file. For example:-
+
+ save /spider/packclus/dxstats show/dxstat
+
+will save the output of the normal command "show/dxstat" to the file
+"dxstats" in the files area.
+
+You can have some extra flags to the save which will either
+date stamp or time stamp or both the filename so:-
+
+ save -d /tmp/a <cmd> creates /tmp/a_6-Jan-2002
+ save -t /tmp/a <cmd> creates /tmp/a_2301Z
+ save -d -t /tmp/a <cmd> creates /tmp/a_6-Jan-2002_2301Z
+
+The -a flag means append to the file instead of overwriting it.
+
+You can have more than one command on the line, to do this you MUST
+enclose each command in double quotes (") eg:-
+
+ save /tmp/a "sh/hfstats" "blank +" "sh/vhfstats"
+
+or
+
+ save /tmp/a "sh/hfstats","blank +","sh/vhfstats"
+
+You can only write into places that the cluster has permission for (which
+is that of the "sysop" user [which had BETTER NOT BE "root"]), you will
+need to create any directories you want to put stuff in beforehand as well.
+
+It is likely that you will want to run these commands in a crontab type
+situation. You would do that something like:-
+
+ 0 0 * * * run_cmd('save /tmp/dxstats echo "DXStat Table", "sh/dxstats"')
+
+Note that you still enclose each command with (") characters but you must
+enclose the entire save command in (') characters.
+
+Now in fact, this can be varied if you know what you are doing. See the
+admin manual for more details.
+
=== 0^SEND <call> [<call> ...]^Send a message to one or more callsigns
=== 0^SEND RR <call>^Send a message and ask for a read receipt
=== 0^SEND COPY <msgno> <call>^Send a copy of a message to someone
SEND <call> on its own acts as though you had typed SEND PRIVATE, that is
it will mark the message as personal and send it to the cluster node that
-that callsign is connected to.
+that callsign is connected to. If the <call> you have specified is in fact
+a known bulletin category on your node (eg: ALL) then the message should
+automatically become a bulletin.
You can have more than one callsign in all of the SEND commands.
SB is an alias for SEND NOPRIVATE (or send a bulletin in BBS speak)
SP is an alias for SEND PRIVATE
+The system will ask you for a subject. Conventionally this should be
+no longer than 29 characters for compatibility. Most modern cluster
+software should accept more.
+
+You will now be prompted to start entering your text.
+
+You finish the message by entering '/EX' on a new line. For instance:
+
+ ...
+ bye then Jim
+ 73 Dirk
+ /ex
+
+If you have started a message and you don't want to keep it then you
+can abandon the message with '/ABORT' on a new line, like:-
+
+ line 1
+ line 2
+ oh I just can't be bothered with this
+ /abort
+
+If you abort the message it will NOT be sent.
+
+When you are entering the text of your message, most normal output (such
+as DX announcements and so on are suppressed and stored for latter display
+(upto 20 such lines are stored, as new ones come along, so the oldest
+lines are dropped).
+
+Also, you can enter normal commands commands (and get the output
+immediately) whilst in the middle of a message. You do this by typing
+the command preceeded by a '/' character on a new line, so:-
+
+ /dx g1tlh 144010 strong signal
+
+Will issue a dx annoucement to the rest of the cluster.
+
+Also, you can add the output of a command to your message by preceeding
+the command with '//', thus :-
+
+ //sh/vhftable
+
+This will show YOU the output from SH/VHFTABLE and also store it in the
+message.
+
+You can carry on with the message until you are ready to send it.
=== 0^SET/ADDRESS <your address>^Record your postal address
=== 0^SET/ANNOUNCE^Allow announce messages to come out on your terminal
will stop anything with these words in the text.
- unset/badspotter annihilated
+ unset/badword annihilated
will allow text with this word again.
=== 0^SET/DX^Allow DX messages to come out on your terminal
=== 0^UNSET/DX^Stop DX messages coming out on your terminal
-=== 0^SET/DXGRID^Allow Grid Squares on the end of DX announcements
-=== 0^UNSET/DXGRID^Stop Grid Squares on the end of DX announcements
+=== 0^SET/DXGRID^Allow QRA Grid Squares on the end of DX announcements
+=== 0^UNSET/DXGRID^Stop QRA Grid Squares on the end of DX announcements
A standard feature which is enabled in version 1.43 and above is
that if the spotter's grid square is known it is output on the end
of a DX announcement (there is just enough room). Some user programs
YOU DO NOT NEED TO USE THIS COMMAND IF YOU ARE CONNECTED VIA AX25.
+=== 0^SET/EMAIL <email> ...^Set email address(es) and forward your personals
+=== 0^UNSET/EMAIL^Stop personal msgs being forwarded by email
+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
+
=== 0^SET/HERE^Tell the system you are present at your terminal
=== 0^UNSET/HERE^Tell the system you are absent from your terminal
SET/HOMENODE gb7djk
=== 8^SET/HOPS <call> ann|spots|route|wwv|wcy <n>^Set hop count
+=== 8^UNSET/HOPS <call> ann|spots|route|wwv|wcy^Unset 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
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 unset the hops with command UNSET/HOPS. For example:-
+
+ unset/hops gb7djk ann
+ unset/hops gb7mbc spots
+
+
=== 9^SET/ISOLATE^Isolate a node from the rest of the network
Connect a node to your system in such a way that you are a full protocol
member of its network and can see all spots on it, but nothing either leaks
=== 0^SET/LANGUAGE <lang>^Set the language you want to use
You can select the language that you want the cluster to use. Currently
-the languages available are en (english) and nl (dutch).
+the languages available are en (English), de (German), es (Spanish)
+and nl (Dutch).
=== 0^SET/LOCATION <lat & long>^Set your latitude and longitude
=== 9^SET/SYS_LOCATION <lat & long>^Set your cluster latitude and longitude
=== 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.
+
+=== 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^UNSET/PASSWORD <call> ...^Delete (remove) a user's password
+This command allows the sysop to completely delete and remove a
+password for a user.
+
+=== 0^SET/PROMPT <string>^Set your prompt to <string>
+=== 0^UNSET/PROMPT^Set your prompt back to default
+This command will set your user prompt to exactly 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).
+
+ SET/PROMPT clx >
+
+UNSET/PROMPT will undo the SET/PROMPT command and set you prompt back to
+normal.
=== 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
fed new style DX Protocol rather normal user commands.
-=== 9^SET/SYS_QRA <locator>^Set your cluster QRA locator
-=== 0^SET/QRA <locator>^Set your QRA locator
+=== 9^SET/SYS_QRA <locator>^Set your cluster QRA Grid locator
+=== 0^SET/QRA <locator>^Set your QRA Grid locator
Tell the system what your QRA (or Maidenhead) locator is. If you have not
done a SET/LOCATION then your latitude and longitude will be set roughly
correctly (assuming your locator is correct ;-). For example:-
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
on <band> - eg 160m 20m 2m 23cm 6mm
on <region> - eg hf vhf uhf shf (see SHOW/BANDS)
+on <from>/<to> - eg 1000/4000 14000-30000 (in Khz)
+ <from>-<to>
<number> - the number of spots you want
<from>-<to> - <from> spot no <to> spot no in the selected list
+<from>/<to>
<prefix> - for a spotted callsign beginning with <prefix>
*<suffix> - for a spotted callsign ending in <suffix>
day <number> - starting <number> days ago
day <from>-<to> - <from> days <to> days ago
-
+ <from>/<to>
+
info <text> - any spots containing <text> in the info or remarks
by <call> - any spots spotted by <call> (spotter <call> is the
qra [<locator>] - this will look for the specific locator if you specify
one or else anything that looks like a locator.
+
+dxcc - treat the prefix as a 'country' and look for spots
+ from that country regardless of actual prefix.
+ eg dxcc oq2
+
+ You can also use this with the 'by' keyword so
+ eg by W dxcc
e.g.
SH/DX iota
SH/DX iota eu-064
SH/DX qra jn86
+ SH/DX dxcc oq2
+ SH/DX dxcc oq2 by w dxcc
=== 0^SHOW/DXCC <prefix>^Interrogate the spot database by country
This command takes the <prefix> (which can be a full or partial
callsign if desired), looks up which internal country number it is
and then displays all the spots as per SH/DX for that country.
+
+This is now an alias for 'SHOW/DX DXCC'
The options for SHOW/DX also apply to this command.
e.g.
SH/DXCC G
- SH/DXCC W on 20m info iota
+ SH/DXCC W on 20m iota
+
+This can be done with the SHOW/DX command like this:-
+
+ SH/DX dxcc g
+ SH/DX dxcc w on 20m iota
=== 0^SHOW/DXSTATS^Show the DX Statistics for last 31 days
Show the total DX spots for the last 31 days
=== 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
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.
-=== 0^SHOW/QRA <locator> [<locator>]^Show distance between locators
-=== 0^SHOW/QRA <lat> <long>^Convert latitude and longitude to a locator
+=== 0^SHOW/QRA <locator> [<locator>]^Show distance between QRA Grid locators
+=== 0^SHOW/QRA <lat> <long>^Convert lat/long to a QRA Grid locator
This is a multipurpose command that allows you either to calculate the
distance and bearing between two locators or (if only one locator is
given on the command line) the distance and beraing from your station
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
/EX
+If you are in 'Talk' mode, there is an extention to the '/' command which
+allows you to send the output to all the people you are talking to. You do
+with the '//' command. For example:-
+
+ //sh/hftable
+
+will send the hftable as you have it to all the people you are currently
+talking to.
+
=== 0^TYPE <filearea>/<name>^Look at the contents of a file in one of the fileareas
Type out the contents of a file in a filearea. So, for example, in
filearea 'bulletins' you want to look at file 'arld051' you would