The <freq> is compared against the available bands set up in the
cluster. See SHOW/BANDS for more information.
+=== 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
+ready to be imported back into the cluster by placing it in the import
+directory (/spider/msg/import).
+
+This command cannot overwrite an existing file. This is to provide some
+measure of security. Any files written will owned by the same user as the
+main cluster, otherwise you can put the new files anywhere the cluster can
+access. For example:-
+
+ EXPORT 2345 /tmp/a
+
+
=== 1^FORWARD/OPERNAME <call>^Send out information on this <call> to all clusters
This command sends out any information held in the user file which can
be broadcast in PC41 protocol packets. This information is Name, QTH, Location
for the <string> you specify and give you a list of likely commands
to look at with HELP.
+=== 5^INIT <node>^Re-initialise a link to an AK1A compatible node
+This command attempts to re-initialise a link to a (usually) AK1A node
+that has got confused, usually by a protocol loop of some kind. It may
+work - but you usually will be better off simply disconnecting it (or
+better, if it is a real AK1A node, doing an RCMD <node> DISC/F <your
+node>).
+
+Best of luck - you will need it.
+
=== 0^KILL <msgno> [<msgno..]^Delete a message from the local system
-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).
+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).
=== 5^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!
+This uses the subject field, so any messages that have exactly the
+same subject will be deleted. Beware!
+
+=== 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.
=== 9^LOAD/ALIASES^Reload the command alias table
-Reload the /spider/cmd/Aliases file after you have editted it. You will need to
-do this if you change this file whilst the cluster is running in order for the
-changes to take effect.
+Reload the /spider/cmd/Aliases file after you have editted it. You
+will need to do this if you change this file whilst the cluster is
+running in order for the changes to take effect.
=== 9^LOAD/BANDS^Reload the band limits table
Reload the /spider/data/bands.pl file if you have changed it manually whilst
the cluster is running.
=== 9^LOAD/CMD_CACHE^Reload the automatic command cache
-Normally, if you change a command file in the cmd or local_cmd tree it will
-automatially be picked up by the cluster program. Sometimes it can get confused
-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.
+Normally, if you change a command file in the cmd or local_cmd tree it
+will automatially be picked up by the cluster program. Sometimes it
+can get confused 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^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 cluster session by executing this
-command. You need to do this if get something like :-
+If you change the /spider/perl/Messages file (usually whilst
+fiddling/writing new commands) you can have them take effect during a
+cluster session by executing this command. You need to do this if get
+something like :-
unknown message 'xxxx' in lang 'en'
=== 9^LOAD/PREFIXES^Reload the prefix table
-Reload the /spider/data/prefix_data.pl file if you have changed it manually whilst
-the cluster is running.
+Reload the /spider/data/prefix_data.pl file if you have changed it
+manually whilst the cluster is running.
=== 5^MERGE <node> [<no spots>/<no wwv>]^Ask for the latest spots and WWV
MERGE allows you to bring your spot and wwv database up to date. By default
This will display more information on the message than DIR does.
=== 8^PC <call> <text>^Send text (eg PC Protocol) to <call>
-Send some arbitrary text to a locally connected callsign. No processing is done on
-the text. This command allows you to send PC Protocol to unstick things if problems
-arise (messages get stuck etc). eg:-
+Send some arbitrary text to a locally connected callsign. No
+processing is done on the text. This command allows you to send PC
+Protocol to unstick things if problems arise (messages get stuck
+etc). eg:-
+
pc gb7djk PC33^GB7TLH^GB7DJK^400^
or
pc G1TLH Try doing that properly!!!
=== 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/ECHO^Make the cluster echo your input
+=== 0^UNSET/ECHO^Stop the cluster echoing your input
+If you are connected via a telnet session, different implimentations
+of telnet handle echo differently depending on whether you are
+connected via port 23 or some other port. You can use this command
+to change the setting appropriately.
+
+The setting is stored in your user profile.
+
+YOU DO NOT NEED TO USE THIS COMMAND IF YOU ARE CONNECTED VIA AX25.
+
=== 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/PAGE 30
SET/PAGE 0
+The setting is stored in your user profile.
+
=== 9^SET/PINGINTERVAL <time> <nodecall>^Set ping time to neighbouring nodes
As from release 1.35 all neighbouring nodes are pinged at regular intervals
in order to determine the rolling quality of the link and, in future, to
=== 0^SET/TALK^Allow TALK messages to come out on your terminal
=== 0^UNSET/TALK^Stop TALK messages coming out on your terminal
+=== 0^SET/WCY^Allow WCY messages to come out on your terminal
+=== 0^UNSET/WCY^Stop WCY messages coming out on your terminal
+
=== 0^SET/WWV^Allow WWV messages to come out on your terminal
=== 0^UNSET/WWV^Stop WWV messages coming out on your terminal
See also TYPE - to see the contents of a file.
+=== 1^SHOW/ISOLATE^Show list of ISOLATED nodes
+
+=== 9^SHOW/LOCKOUT^Show the list of locked out or excluded callsigns
+
=== 0^SHOW/MOON [<prefix>|<callsign>]^Show Moon rise and set times
Show the Moon rise and set times for a (list of) prefixes or callsigns,
together with the azimuth and elevation of the sun currently at those
then it will show UTC and UTC + the local offset (not including DST) at
the prefixes or callsigns that you specify.
+=== 0^SHOW/WCY^Show last 10 WCY broadcasts
+=== 0^SHOW/WCY <n>^Show last <n> WCY broadcasts
+Display the most recent WCY information that has been received by the system
+
=== 0^SHOW/WWV^Show last 10 WWV broadcasts
=== 0^SHOW/WWV <n>^Show last <n> WWV broadcasts
Display the most recent WWV information that has been received by the system
projects / spider.git / blobdiff