\r
<!-- Title information -->\r
\r
-<title>The DXSpider Administration Manual v1.50</title> \r
+<title>The DXSpider Administration Manual v1.51</title> \r
<author>Ian Maude, G0VGS, (g0vgs@gb7mbc.net), and\r
Charlie Carroll, K1XX, (k1xx@ptcnh.net)</author>\r
-<date>February 2003 revision 0.3</date>\r
+<date>June 2004 revision 1</date>\r
\r
<abstract>\r
A reference for SysOps of the DXSpider DXCluster program.\r
for example). To do this, isolate the node in the normal way and use\r
an <em>acc/spot >call< all</em> filter to override the isolate. \r
\r
+<sect1>A DXSpider Filtering Tutorial\r
+\r
+<P>\r
+There is now an excellent primer/tutorial on filtering written by Jim\r
+Samuels, W3BG with an introduction by Dave Hawes N3RD that I strongly\r
+suggest you read. You can read it here \r
+<htmlurl url="filtering_en.html" name="The DXSpider User Filtering Primer">\r
+\r
<sect>Other filters\r
\r
<sect1>Filtering Mail\r
directory.\r
\r
<verb>\r
-cvs -z3 -d:pserver:anonymous@cvs.DXSpider.sourceforge.net:/cvsroot/dxspider co spider\r
+cvs -z3 -d:pserver:anonymous@cvs.sourceforge.net:/cvsroot/dxspider co spider\r
</verb>\r
\r
This command is all on one line.\r
Restart your Spider software\r
</verb></tscreen>\r
\r
-<sect>The DXSpider command set\r
-\r
+<sect>The DXSpider Command Reference\r
\r
<sect1>accept (0)
</tt>
<P>
+<sect1>chat <group> <text> (0)
+
+<P>
+<tt>
+<bf>chat <group> <text></bf> Chat or Conference to a group
+</tt>
+
+<P>
+It is now possible to JOIN a group and have network wide conferencing to that
+group. DXSpider does not (and probably will not) implement the AK1A
+conference mode as this seems very limiting, is hardly used and doesn't seem
+to work too well anyway.
+
+This system uses the existing ANN system and is compatible with both other
+DXSpider nodes and AK1A clusters (they use ANN/<group>).
+
+You can be a member of as many "groups" as you want. To join a group type:-
+
+<tscreen><verb>
+ JOIN FOC (where FOC is the group name)
+</verb></tscreen>
+
+To leave a group type:-
+
+<tscreen><verb>
+ LEAVE FOC
+</verb></tscreen>
+
+You can see which groups you are in by typing:-
+
+<tscreen><verb>
+ STAT/USER
+</verb></tscreen>
+
+and you can see whether your mate is in the group, if he connects to the
+same node as you, by typing:-
+
+<tscreen><verb>
+ STAT/USER g1tlh
+</verb></tscreen>
+
+To send a message to a group type:-
+
+<tscreen><verb>
+ CHAT FOC hello everyone
+</verb></tscreen>
+
+or
+
+<tscreen><verb>
+ CH #9000 hello I am back
+</verb></tscreen>
+
+See also JOIN, LEAVE, SHOW/CHAT
<sect1>clear/announce <callsign> [input] [0-9|all] (8)
<P>
<P>
Title says it all really, this command lists all the databases defined
in the system. It is also aliased to SHOW/COMMAND.
+<sect1>dbcreate <name> (9)
+
+<P>
+<tt>
+<bf>dbcreate <name></bf> Create a database entry
+</tt>
+
+<P>
+<sect1>dbcreate <name> chain <name> [<name>..] (9)
+
+<P>
+<tt>
+<bf>dbcreate <name> chain <name> [<name>..]</bf> Create a chained database entry
+</tt>
+
+<P>
+<sect1>dbcreate <name> cmd <dxspider command> (9)
+
+<P>
+<tt>
+<bf>dbcreate <name> cmd <dxspider command></bf> make a local command available as a DB
+</tt>
+
+<P>
+DBCREATE allows you to define a database in the system. It doesn't actually
+create anything, just defines it.
+
+The databases that are created are simple DB_File hash databases, they are
+therefore already 'indexed'.
+
+You can define a local database with the first form of the command eg:
+
+<tscreen><verb>
+ DBCREATE oblast
+</verb></tscreen>
+
+You can also chain databases with the addition of the 'chain' keyword.
+This will search each database one after the other. A typical example
+is:
+
+<tscreen><verb>
+ DBCREATE sdx_qsl chain sql_ad
+</verb></tscreen>
+
+No checking is done to see if the any of the chained databases exist, in
+fact it is usually better to do the above staement first then do each of
+the chained databases.
+
+Databases can exist offsite. To define a database that lives on another
+node do:
+
+<tscreen><verb>
+ DBCREATE buckmaster remote gb7dxc
+</verb></tscreen>
+
+Remote databases cannot be chained; however, the last database in a
+a chain can be a remote database eg:
+
+<tscreen><verb>
+ DBCREATE qsl chain gb7dxc
+</verb></tscreen>
+
+To see what databases have been defined do:
+
+<tscreen><verb>
+ DBAVAIL (or it will have been aliased to SHOW/COMMAND)
+</verb></tscreen>
+
+It would be normal for you to add an entry into your local Aliases file
+to allow people to use the 'SHOW/<dbname>' style syntax. So you would
+need to add a line like:-
+
+<tscreen><verb>
+ 's' => [
+ ..
+ ..
+ '^sh\w*/buc', 'dbshow buckmaster', 'dbshow',
+ ..
+ ..
+ ],
+</verb></tscreen>
+
+to allow
+
+<tscreen><verb>
+ SH/BUCK g1tlh
+</verb></tscreen>
+
+to work as they may be used to.
+
+You can also make local commands available as 'pseudo' databases. You
+can therefore make spider special commands available as a database. I
+imagine that this will be primarily useful for remote access from
+legacy nodes. For example:-
+
+<tscreen><verb>
+ DBCREATE dxqsl cmd show/dxqsl
+</verb></tscreen>
+
+You also use one of these databases in a chain. This may be useful
+locally.
+
+See DBIMPORT for the importing of existing AK1A format data to databases.
+See DBSHOW for generic database enquiry
+
+<sect1>dbcreate <name> remote <node> (9)
+
+<P>
+<tt>
+<bf>dbcreate <name> remote <node></bf> Create a remote database entry
+</tt>
+
+<P>
+<sect1>dbimport <dbname> <filename> (9)
+
+<P>
+<tt>
+<bf>dbimport <dbname> <filename></bf> Import AK1A data into a database
+</tt>
+
+<P>
+If you want to import or update data in bulk to a database you can use
+this command. It will either create or update entries into an existing
+database. For example:-
+
+<tscreen><verb>
+ DBIMPORT oblast /tmp/OBLAST.FUL
+</verb></tscreen>
+
+will import the standard OBLAST database that comes with AK1A into the
+oblast database held locally.
+<sect1>dbremove <dbname> (9)
+
+<P>
+<tt>
+<bf>dbremove <dbname></bf> Delete a database
+</tt>
+
+<P>
+DBREMOVE will completely remove a database entry and also delete any data
+file that is associated with it.
+
+There is no warning, no comeback, no safety net.
+
+For example:
+
+<tscreen><verb>
+ DBREMOVE oblast
+</verb></tscreen>
+
+will remove the oblast database from the system and it will also remove
+the associated datafile.
+
+I repeat:
+
+There is no warning, no comeback, no safety net.
+
+You have been warned.
<sect1>dbshow <dbname> <key> (0)
<P>
DBSHOW buck G1TLH
</verb></tscreen>
+<sect1>debug (9)
+
+<P>
+<tt>
+<bf>debug</bf> Set the cluster program into debug mode
+</tt>
+
+<P>
+Executing this command will only have an effect if you are running the cluster
+in debug mode i.e.
+
+<tscreen><verb>
+ perl -d cluster.pl
+</verb></tscreen>
+
+It will interrupt the cluster just after the debug command has finished.
+<sect1>delete/usdb <callsign> ... (9)
+
+<P>
+<tt>
+<bf>delete/usdb <callsign> ...</bf> Delete this user from the US State Database
+</tt>
+
+<P>
+This command will completely remove a one or more callsigns
+from the US States database.
+
+There is NO SECOND CHANCE.
+
+It goes without saying that you should use this command CAREFULLY!
+
+Note that these callsign may be re-instated by any weekly updates from
+the FCC.
+<sect1>delete/user <callsign> ... (9)
+
+<P>
+<tt>
+<bf>delete/user <callsign> ...</bf> Delete this user from the User Database
+</tt>
+
+<P>
+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!
+<sect1>demonstrate <call> <command> (9)
+
+<P>
+<tt>
+<bf>demonstrate <call> <command></bf> Demonstrate a command to another user
+</tt>
+
+<P>
+This command is provided so that sysops can demonstrate commands to
+other users. It runs a command as though that user had typed it in and
+then sends the output to that user, together with the command that
+caused it.
+
+<tscreen><verb>
+ DEMO g7brn sh/dx iota oc209
+ DEMO g1tlh set/here
+</verb></tscreen>
+
+Note that this command is similar to SPOOF and will have the same side
+effects. Commands are run at the privilege of the user which is being
+demonstrated to.
<sect1>directory (0)
<P>
on the output.
+<sect1>export <msgno> <filename> (9)
+
+<P>
+<tt>
+<bf>export <msgno> <filename></bf> Export a message to a file
+</tt>
+
+<P>
+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:-
+
+<tscreen><verb>
+ EXPORT 2345 /tmp/a
+</verb></tscreen>
+
+<sect1>export_users [<filename>] (9)
+
+<P>
+<tt>
+<bf>export_users [<filename>]</bf> Export the users database to ascii
+</tt>
+
+<P>
+Export the users database to a file in ascii format. If no filename
+is given then it will export the file to /spider/data/user_asc.
+
+If the file already exists it will be renamed to <filename>.o. In fact
+up to 5 generations of the file can be kept each one with an extra 'o' on the
+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.
<sect1>filtering... (0)
<P>
Best of luck - you will need it.
+<sect1>join <group> (0)
+
+<P>
+<tt>
+<bf>join <group></bf> Join a chat or conference group
+</tt>
+
+<P>
+JOIN allows you to join a network wide conference group. To join a
+group (called FOC in this case) type:-
+
+<tscreen><verb>
+ JOIN FOC
+</verb></tscreen>
+
+See also CHAT, LEAVE, SHOW/CHAT
<sect1>kill (5)
<P>
</tt>
<P>
+<sect1>leave <group> (0)
+
+<P>
+<tt>
+<bf>leave <group></bf> Leave a chat or conference group
+</tt>
+
+<P>
+LEAVE allows you to leave a network wide conference group. To leave a
+group (called FOC in this case) type:-
+
+<tscreen><verb>
+ LEAVE FOC
+</verb></tscreen>
+
+See also CHAT, JOIN, SHOW/CHAT
<sect1>links (0)
<P>
<P>
This is a quick listing that shows which links are connected and
some information about them. See WHO for a list of all connections.
+<sect1>load/aliases (9)
+
+<P>
+<tt>
+<bf>load/aliases</bf> Reload the command alias table
+</tt>
+
+<P>
+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.
+<sect1>load/badmsg (9)
+
+<P>
+<tt>
+<bf>load/badmsg</bf> Reload the bad msg table
+</tt>
+
+<P>
+Reload the /spider/msg/badmsg.pl file if you have changed it manually whilst
+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.
+<sect1>load/badwords (9)
+
+<P>
+<tt>
+<bf>load/badwords</bf> Reload the bad words table
+</tt>
+
+<P>
+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.
+<sect1>load/bands (9)
+
+<P>
+<tt>
+<bf>load/bands</bf> Reload the band limits table
+</tt>
+
+<P>
+Reload the /spider/data/bands.pl file if you have changed it manually whilst
+the cluster is running.
+<sect1>load/cmd_cache (9)
+
+<P>
+<tt>
+<bf>load/cmd_cache</bf> Reload the automatic command cache
+</tt>
+
+<P>
+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.
+<sect1>load/forward (9)
+
+<P>
+<tt>
+<bf>load/forward</bf> Reload the msg forwarding routing table
+</tt>
+
+<P>
+Reload the /spider/msg/forward.pl file if you have changed it
+manually whilst the cluster is running.
<sect1>load/keps (5)
<P>
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.
+<sect1>load/messages (9)
+
+<P>
+<tt>
+<bf>load/messages</bf> Reload the system messages file
+</tt>
+
+<P>
+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'
+<sect1>load/prefixes (9)
+
+<P>
+<tt>
+<bf>load/prefixes</bf> Reload the prefix table
+</tt>
+
+<P>
+Reload the /spider/data/prefix_data.pl file if you have changed it
+manually whilst the cluster is running.
<sect1>merge <node> [<no spots>/<no wwv>] (5)
<P>
You can request any number of spots or wwv and although they will be appended
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).
-<sect1>pc <call> <text> (8)
+<sect1>msg <cmd> <msgno> [data ... ] (9)
<P>
<tt>
-<bf>pc <call> <text></bf> Send arbitrary text to a connected callsign
+<bf>msg <cmd> <msgno> [data ... ]</bf> Alter various message parameters
</tt>
<P>
-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:-
+Alter message parameters like To, From, Subject, whether private or bulletin
+or return receipt (RR) is required or whether to keep this message from timing
+out.
<tscreen><verb>
- pc gb7djk PC33^GB7TLH^GB7DJK^400^
+ MSG TO <msgno> <call> - change TO callsign to <call>
+ MSG FRom <msgno> <call> - change FROM callsign to <call>
+ MSG PRrivate <msgno> - set private flag
+ MSG NOPRrivate <msgno> - unset private flag
+ MSG RR <msgno> - set RR flag
+ MSG NORR <msgno> - unset RR flag
+ MSG KEep <msgno> - set the keep flag (message won't be deleted ever)
+ MSG NOKEep <msgno> - unset the keep flag
+ MSG SUbject <msgno> <new> - change the subject to <new>
+ MSG WAittime <msgno> - remove any waitting time for this message
+ MSG NOREad <msgno> - mark message as unread
+ MSG REad <msgno> - mark message as read
+ MSG QUeue - queue any outstanding bulletins
+ MSG QUeue 1 - queue any outstanding private messages
+</verb></tscreen>
+
+You can look at the status of a message by using:-
+
+<tscreen><verb>
+ STAT/MSG <msgno>
+</verb></tscreen>
+
+This will display more information on the message than DIR does.
+
+<sect1>pc <call> <text> (8)
+
+<P>
+<tt>
+<bf>pc <call> <text></bf> Send arbitrary text to a connected callsign
+</tt>
+
+<P>
+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:-
+
+<tscreen><verb>
+ pc gb7djk PC33^GB7TLH^GB7DJK^400^
</verb></tscreen>
or
<tscreen><verb>
You can also use all the extra qualifiers such as RR, PRIVATE,
NOPRIVATE, B that you can use with the SEND command (see SEND
for further details)
+<sect1>save [-d -t -a] <filename> "<cmd>" [...] (9)
+
+<P>
+<tt>
+<bf>save [-d -t -a] <filename> "<cmd>" [...]</bf> Save command output to a file
+</tt>
+
+<P>
+This sysop only cammand allows you to save the output of one or more
+commands to a file. For example:-
+
+<tscreen><verb>
+ save /spider/packclus/dxstats show/dxstat
+</verb></tscreen>
+
+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:-
+
+<tscreen><verb>
+ 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
+</verb></tscreen>
+
+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:-
+
+<tscreen><verb>
+ save /tmp/a "sh/hfstats" "blank +" "sh/vhfstats"
+</verb></tscreen>
+
+or
+
+<tscreen><verb>
+ save /tmp/a "sh/hfstats","blank +","sh/vhfstats"
+</verb></tscreen>
+
+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:-
+
+<tscreen><verb>
+ 0 0 * * * run_cmd('save /tmp/dxstats "echo DXStat Table", "sh/dxstats"')
+</verb></tscreen>
+
+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.
+
<sect1>send <call> [<call> ...] (0)
<P>
<bf>set/clx <call> [<call>..]</bf> Make the callsign an CLX node
</tt>
+<P>
+<sect1>set/debug <name> (9)
+
+<P>
+<tt>
+<bf>set/debug <name></bf> Add a debug level to the debug set
+</tt>
+
<P>
<sect1>set/dx (0)
<bf>set/dx</bf> Allow DX messages to come out on your terminal
</tt>
+<P>
+<sect1>set/dxcq (0)
+
+<P>
+<tt>
+<bf>set/dxcq</bf> Show CQ Zones on the end of DX announcements
+</tt>
+
<P>
<sect1>set/dxgrid (0)
</tt>
<P>
-<sect1>set/dxnet <call> [<call>..] (5)
+<sect1>set/dxitu (0)
<P>
<tt>
-<bf>set/dxnet <call> [<call>..]</bf> Make the callsign an DXNet node
+<bf>set/dxitu</bf> Show ITU Zones on the end of DX announcements
</tt>
<P>
-<sect1>set/dxstate (0)
+<sect1>set/dxnet <call> [<call>..] (5)
<P>
<tt>
-<bf>set/dxstate</bf> Allow US State info on the end of DX announcements
+<bf>set/dxnet <call> [<call>..]</bf> Make the callsign an DXNet node
</tt>
<P>
</tt>
<P>
+<sect1>set/isolate (9)
+
+<P>
+<tt>
+<bf>set/isolate</bf> Isolate a node from the rest of the network
+</tt>
+
+<P>
+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
+out from it nor goes back into from the rest of the nodes connected to you.
+
+You can potentially connect several nodes in this way.
+
<sect1>set/language <lang> (0)
<P>
<P>
You can select the language that you want the cluster to use. Currently
-the languages available are en (English), de (German), es (Spanish)
-and nl (Dutch).
+the languages available are en (English), de (German), es (Spanish),
+Czech (cz), French (fr), Portuguese (pt), Italian (it) and nl (Dutch).
<sect1>set/location <lat & long> (0)
<P>
<bf>set/location <lat & long></bf> Set your latitude and longitude
</tt>
+<P>
+<sect1>set/lockout <call> (9)
+
+<P>
+<tt>
+<bf>set/lockout <call></bf> Stop a callsign connecting to the cluster
+</tt>
+
<P>
<sect1>set/logininfo (0)
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.
+<sect1>set/password <callsign> <string> (9)
+
+<P>
+<tt>
+<bf>set/password <callsign> <string></bf> Set a users password
+</tt>
+
+<P>
+The password for a user can only be set by a full sysop. The string
+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:
+
+<tscreen><verb>
+ set/var $main::passwdreq = 1
+</verb></tscreen>
+
+command is executed in the startup script, then a password prompt is
+given after the normal 'login: ' prompt.
+<sect1>set/pinginterval <time> <nodecall> (9)
+
+<P>
+<tt>
+<bf>set/pinginterval <time> <nodecall></bf> Set ping time to neighbouring nodes
+</tt>
+
+<P>
+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
+affect routing decisions. The default interval is 300 secs or 5 minutes.
+
+You can use this command to set a different interval. Please don't.
+
+But if you do the value you enter is treated as minutes up 30 and seconds
+for numbers greater than that.
+
+This is used also to help determine when a link is down at the far end
+(as certain cluster software doesn't always notice), see SET/OBSCOUNT
+for more information.
+
+If you must change it (and it may be useful for internet connected nodes
+on dynamic IP addresses that go away after a set time of usage) the time
+can be specified as:-
+
+<tscreen><verb>
+ 5 which if less than 30 is converted to minutes otherwise is
+ taken as the no of seconds between pings.
+ 120s 120 seconds
+ 5m 5 minutes
+ 1h 1 hour
+</verb></tscreen>
+
+Please be aware that this causes traffic to occur on the link, setting
+this value too low may annoy your neighbours beyond the point of
+endurance!
+
+You can switch this off by setting it to 0.
+<sect1>set/privilege <n> <call> [<call..] (9)
+
+<P>
+<tt>
+<bf>set/privilege <n> <call> [<call..]</bf> Set privilege level on a call
+</tt>
+
+<P>
+Set the privilege level on a callsign. The privilege levels that pertain
+to commands are as default:-
+<tscreen><verb>
+ 0 - normal user
+ 1 - allow remote nodes normal user RCMDs
+ 5 - various privileged commands (including shutdown, but not disc-
+ connect), the normal level for another node.
+ 8 - more privileged commands (including disconnect)
+ 9 - local sysop privilege. DO NOT SET ANY REMOTE USER OR NODE TO THIS
+ LEVEL.
+</verb></tscreen>
+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.
<sect1>set/prompt <string> (0)
<P>
SET/QTH East Dereham, Norfolk
</verb></tscreen>
+<sect1>set/register <call> ... (9)
+
+<P>
+<tt>
+<bf>set/register <call> ...</bf> Mark a user as registered
+</tt>
+
+<P>
<sect1>set/spider <call> [<call>..] (5)
<P>
<P>
Tell the system that the call(s) are to be treated as DXSpider node and
fed new style DX Protocol rather normal user commands.
+<sect1>set/sys_location <lat & long> (9)
+
+<P>
+<tt>
+<bf>set/sys_location <lat & long></bf> Set your cluster latitude and longitude
+</tt>
+
+<P>
+In order to get accurate headings and such like you must tell the system
+what your latitude and longitude is. If you have not yet done a SET/QRA
+then this command will set your QRA locator for you. For example:-
+<tscreen><verb>
+ SET/LOCATION 52 22 N 0 57 E
+</verb></tscreen>
+
+<sect1>set/sys_qra <locator> (9)
+
+<P>
+<tt>
+<bf>set/sys_qra <locator></bf> Set your cluster QRA Grid locator
+</tt>
+
+<P>
<sect1>set/talk (0)
<P>
<bf>set/talk</bf> Allow TALK messages to come out on your terminal
</tt>
+<P>
+<sect1>set/usdb <call> <state> <city> (9)
+
+<P>
+<tt>
+<bf>set/usdb <call> <state> <city></bf> add/update a US DB callsign
+</tt>
+
+<P>
+This command allows you to add or alter a callsign in the US state
+database. Use with extreme caution. Anything you do here will be
+overwritten by any weekly updates that affect this callsign
+
+<tscreen><verb>
+ set/usdb g1tlh nh downtown rindge
+</verb></tscreen>
+
+see also DELETE/USDB
+<sect1>set/usstate (0)
+
+<P>
+<tt>
+<bf>set/usstate</bf> Allow US State info on the end of DX announcements
+</tt>
+
<P>
<sect1>set/wcy (0)
<P>
Display all the bad words in the system, see SET/BADWORD
for more information.
+<sect1>show/chat [<group>] [<lines>] (0)
+
+<P>
+<tt>
+<bf>show/chat [<group>] [<lines>]</bf> Show any chat or conferencing
+</tt>
+
+<P>
+This command allows you to see any chat or conferencing that has
+occurred whilst you were away. SHOW/CHAT on its own will show data for
+all groups. If you use a group name then it will show only chat for
+that group.
<sect1>show/configuration [<node>] (0)
<P>
<P>
This command shows information on all the active connections known to
the node. This command gives slightly more information than WHO.
+<sect1>show/contest <year and month> (0)
+
+<P>
+<tt>
+<bf>show/contest <year and month></bf> Show all the contests for a month
+</tt>
+
+<P>
+Show all known contests which are maintained at http://www.sk3bg.se/contest/
+for a particular month or year. The format is reasonably flexible.
+For example:-
+
+<tscreen><verb>
+ SH/CONTEST sep2003
+ SH/CONTEST 03 march
+</verb></tscreen>
+
<sect1>show/date [<prefix>|<callsign>] (0)
<P>
is provided for users of this software by http://www.qslinfo.de.
See also SHOW/QRZ, SHOW/WM7D.
+<sect1>show/debug (9)
+
+<P>
+<tt>
+<bf>show/debug</bf> Show what levels of debug information you are logging
+</tt>
+
+<P>
<sect1>show/dx (0)
<P>
You can also use this with the 'by' keyword so
eg by W dxcc
</verb></tscreen>
-
+
+<tscreen><verb>
+ real or rt - Format the output the same as for real time spots. The
+ formats are deliberately different (so you can tell
+ one sort from the other). This is useful for some
+ logging programs that can't cope with normal sh/dx
+ output. An alias of SHOW/FDX is available.
+</verb></tscreen>
+
+<tscreen><verb>
+ filter - Filter the spots, before output, with the user's
+ spot filter. An alias of SHOW/MYDX is available.
+</verb></tscreen>
+
+<tscreen><verb>
+ zone <zones> - look for spots in the cq zone (or zones) specified.
+ zones are numbers separated by commas.
+</verb></tscreen>
+
+<tscreen><verb>
+ by_zone <zones> - look for spots spotted by people in the cq zone
+ specified.
+</verb></tscreen>
+
+<tscreen><verb>
+ itu <itus> - look for spots in the itu zone (or zones) specified
+ itu zones are numbers separated by commas.
+</verb></tscreen>
+
+<tscreen><verb>
+ by_itu <itus> - look for spots spotted by people in the itu zone
+ specified.
+</verb></tscreen>
+
+<tscreen><verb>
+ state <list> - look for spots in the US state (or states) specified
+ The list is two letter state codes separated by commas.
+</verb></tscreen>
+
+<tscreen><verb>
+ by_state <list> - look for spots spotted by people in the US state
+ specified.
+</verb></tscreen>
+
<tscreen><verb>
e.g.
</verb></tscreen>
SH/DX qra jn86
SH/DX dxcc oq2
SH/DX dxcc oq2 by w dxcc
+ SH/DX zone 4,5,6
+ SH/DX by_zone 4,5,6
+ SH/DX state in,oh
+ SH/DX by_state in,oh
</verb></tscreen>
<sect1>show/dxcc <prefix> (0)
SH/DX dxcc w on 20m iota
</verb></tscreen>
+This is an alias for: SH/DX dxcc
+<sect1>show/dxqsl <callsign> (0)
+
+<P>
+<tt>
+<bf>show/dxqsl <callsign></bf> Show any QSL info gathered from spots
+</tt>
+
+<P>
+The node collects information from the comment fields in spots (things
+like 'VIA EA7WA' or 'QSL-G1TLH') and stores these in a database.
+
+This command allows you to interrogate that database and if the callsign
+is found will display the manager(s) that people have spotted. This
+information is NOT reliable, but it is normally reasonably accurate if
+it is spotted enough times.
+
+For example:-
+
+<tscreen><verb>
+ sh/dxqsl 4k9w
+</verb></tscreen>
+
+You can check the raw input spots yourself with:-
+
+<tscreen><verb>
+ sh/dx 4k9w qsl
+</verb></tscreen>
+
+This gives you more background information.
<sect1>show/dxstats [days] [date] (0)
<P>
<P>
Show the total DX spots for the last <days> no of days (default is 31),
starting from a <date> (default: today).
+<sect1>show/fdx (0)
+
+<P>
+<tt>
+<bf>show/fdx</bf> Show the DX data in realtime format.
+</tt>
+
+<P>
+Normally SHOW/DX outputs spot data in a different format to the
+realtime data. This is a deliberate policy (so you can tell the
+difference between the two). Some logging programs cannot handle
+this so SHOW/FDX outputs historical data in real time format.
+
+This is an alias for: SHOW/DX real
<sect1>show/files [<filearea> [<string>]] (0)
<P>
<bf>show/isolate</bf> Show list of ISOLATED nodes
</tt>
+<P>
+<sect1>show/lockout <prefix>|all (9)
+
+<P>
+<tt>
+<bf>show/lockout <prefix>|all</bf> Show the list of locked out or excluded callsigns
+</tt>
+
<P>
<sect1>show/log [<callsign>] (8)
Gives you an estimate of the long path propagation characterics. It
should be noted that the figures will probably not be very useful, nor
terrible accurate, but it is included for completeness.
+<sect1>show/mydx (0)
+
+<P>
+<tt>
+<bf>show/mydx</bf> Show the DX data filtered with your spot filter.
+</tt>
+
+<P>
+SHOW/DX potentially shows all the spots available in the system. Using
+SHOW/MYDX will, instead, filter the availble spots using any spot filter
+that you have set, first.
+
+This command, together with ACCEPT/SPOT or REJECT/SPOT, will allow
+you to customise the spots that you receive.
+
+So if you have said: ACC/SPOT on hf
+
+Doing a SHOW/MYDX will now only, ever, show HF spots. All the other
+options on SH/DX can still be used.
<sect1>show/newconfiguration [<node>] (0)
<P>
is provided for users of this software by http://www.qrz.com
See also SHOW/WM7D for an alternative.
+<sect1>show/registered [<prefix>] (9)
+
+<P>
+<tt>
+<bf>show/registered [<prefix>]</bf> Show the registered users
+</tt>
+
+<P>
<sect1>show/route <callsign> ... (0)
<P>
<P>
Shutdown the cluster and disconnect all the users
+<sect1>spoof <call> <command> (9)
+
+<P>
+<tt>
+<bf>spoof <call> <command></bf> Do a command as though you are another user
+</tt>
+
+<P>
+This command is provided so that sysops can set a user's parameters without
+me having to write a special 'sysop' version for every user command. It
+allows you to pretend that you are doing the command as the user you specify.
+
+eg:-
+
+<tscreen><verb>
+ SPOOF G1TLH set/name Dirk
+ SPOOF G1TLH set/qra JO02LQ
+</verb></tscreen>
+
<sect1>stat/channel [<callsign>] (5)
<P>
</tt>
<P>
+<sect1>unset/debug <name> (9)
+
+<P>
+<tt>
+<bf>unset/debug <name></bf> Remove a debug level from the debug set
+</tt>
+
+<P>
+You can choose to log several different levels. The levels are
+
+<tscreen><verb>
+ chan
+ state
+ msg
+ cron
+ connect
+</verb></tscreen>
+
+You can show what levels you are logging with SHOW/DEBUG
<sect1>unset/dx (0)
<P>
</tt>
<P>
+<sect1>unset/dxcq (0)
+
+<P>
+<tt>
+<bf>unset/dxcq</bf> Stop CQ Zones on the end of DX announcements
+</tt>
+
+<P>
+Display both the Spotter's and the Spotted's CQ Zone on the end
+of a DX announcement (there is just enough room). Some user programs
+cannot cope with this. The Spotter's CQ is on the RHS of the
+time, the Spotted's CQ is on the LHS.
+
+Conflicts with: SET/DXGRID, SET/DXITU, SHOW/USSTATE
+
+Do a STAT/USER to see which flags you have set if you are confused.
<sect1>unset/dxgrid (0)
<P>
of a DX announcement (there is just enough room). Some user programs
cannot cope with this. You can use this command to reset (or set)
this feature.
-<sect1>unset/dxstate (0)
+
+Conflicts with: SET/DXCQ, SET/DXITU
+
+Do a STAT/USER to see which flags you have set if you are confused.
+<sect1>unset/dxitu (0)
<P>
<tt>
-<bf>unset/dxstate</bf> Stop US State info on the end of DX announcements
+<bf>unset/dxitu</bf> Stop ITU Zones on the end of DX announcements
</tt>
<P>
-If the spotter's or spotted's US State is known it is output on the
-end of a DX announcement (there is just enough room).
+Display both the Spotter's and the Spotted's ITU Zone on the end
+of a DX announcement (there is just enough room). Some user programs
+cannot cope with this. The Spotter's ITU is on the RHS of the
+time, the Spotted's ITU is on the LHS.
-A spotter's state will appear on the RHS of the time (like
-SET/DXGRID) and the spotted's State will appear on the LHS of the
-time field. Any information found will override any locator
-information from SET/DXGRID.
+Conflicts with: SET/DXGRID, SET/DXCQ, SHOW/USSTATE
-Some user programs cannot cope with this. You can use this command
-to reset (or set) this feature.
+Do a STAT/USER to see which flags you have set if you are confused.
<sect1>unset/echo (0)
<P>
unset/hops gb7mbc spots
</verb></tscreen>
+<sect1>unset/isolate (9)
+
+<P>
+<tt>
+<bf>unset/isolate</bf> Stop Isolation of a node from the rest of the network
+</tt>
+
+<P>
+Remove isolation from a node - SET/ISOLATE
+<sect1>unset/lockout <call> (9)
+
+<P>
+<tt>
+<bf>unset/lockout <call></bf> Allow a callsign to connect to the cluster
+</tt>
+
+<P>
<sect1>unset/logininfo (0)
<P>
</tt>
<P>
+<sect1>unset/password <call> ... (9)
+
+<P>
+<tt>
+<bf>unset/password <call> ...</bf> Delete (remove) a user's password
+</tt>
+
+<P>
+This command allows the sysop to completely delete and remove a
+password for a user.
<sect1>unset/privilege (0)
<P>
UNSET/PROMPT will undo the SET/PROMPT command and set you prompt back to
normal.
+<sect1>unset/register <call> ... (9)
+
+<P>
+<tt>
+<bf>unset/register <call> ...</bf> Mark a user as not registered
+</tt>
+
+<P>
+Registration is a concept that you can switch on by executing the
+
+<tscreen><verb>
+ set/var $main::regreq = 1
+</verb></tscreen>
+
+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.
+
<sect1>unset/talk (0)
<P>
</tt>
<P>
+<sect1>unset/usstate (0)
+
+<P>
+<tt>
+<bf>unset/usstate</bf> Stop US State info on the end of DX announcements
+</tt>
+
+<P>
+If the spotter's or spotted's US State is known it is output on the
+end of a DX announcement (there is just enough room).
+
+A spotter's state will appear on the RHS of the time (like
+SET/DXGRID) and the spotted's State will appear on the LHS of the
+time field. Any information found will override any locator
+information from SET/DXGRID.
+
+Some user programs cannot cope with this. You can use this command
+to reset (or set) this feature.
+
+Conflicts with: SET/DXCQ, SET/DXITU
+
+Do a STAT/USER to see which flags you have set if you are confused.
<sect1>unset/wcy (0)
<P>
projects / spider.git / blobdiff