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
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
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.
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.
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
projects / spider.git / blobdiff