X-Git-Url: http://gb7djk.dxcluster.net/gitweb/gitweb.cgi?a=blobdiff_plain;f=html%2Fadminmanual_en-11.html;h=c445b70c931f64f79352f7faf53b72cbc3a383a0;hb=cbb49d0c832bfe94e35fa79e0fd978e9d3d287db;hp=a4fa0fcdf5fbac3cb66d5b0c6f4fd62c53c52bb5;hpb=ded9826c433e14be019cb8713ebfb5a7ff65ea13;p=spider.git diff --git a/html/adminmanual_en-11.html b/html/adminmanual_en-11.html index a4fa0fcd..c445b70c 100644 --- a/html/adminmanual_en-11.html +++ b/html/adminmanual_en-11.html @@ -1,8 +1,8 @@
- -catchup <node call> all|[<msgno> ...] Mark a message as sent
chat <group> <text> Chat or Conference to a group
It is now possible to JOIN a group and have network wide conferencing to thatgroup. DXSpider does not (and probably will not) implement the AK1A conference mode as this seems very limiting, is hardly used and doesn't seemto work too well anyway.This system uses the existing ANN system and is compatible with both otherDXSpider 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:- +
+
+ JOIN FOC (where FOC is the group name)
+
+
+To leave a group type:-
+
+
+ LEAVE FOC
+
+
+You can see which groups you are in by typing:-
+
+
+ STAT/USER
+
+
+and you can see whether your mate is in the group, if he connects to thesame node as you, by typing:-
+
+
+ STAT/USER g1tlh
+
+
+To send a message to a group type:-
+
+
+ CHAT FOC hello everyone
+
+
+or
+
+
+ CH #9000 hello I am back
+
+
+See also JOIN, LEAVE, SHOW/CHAT
+clear/announce <callsign> [input] [0-9|all] Clear a announce filter line
A sysop can clear an input or normal output filter for a user or thenode_default or user_default.
-clear/announce [1|all] Clear a announce filter line
This command allows you to clear (remove) a line in a annouce filter or to remove the whole filter.see CLEAR/SPOTS for a more detailed explanation.
-clear/route <callsign> [input] [0-9|all] Clear a route filter line
A sysop can clear an input or normal output filter for a user or thenode_default or user_default.
-clear/route [1|all] Clear a route filter line
This command allows you to clear (remove) a line in a route filter or to remove the whole filter.see CLEAR/SPOTS for a more detailed explanation.
-clear/spots <callsign> [input] [0-9|all] Clear a spot filter line
A sysop can clear an input or normal output filter for a user or thenode_default or user_default.
-clear/spots [0-9|all] Clear a spot filter line
clear/wcy <callsign> [input] [0-9|all] Clear a WCY filter line
A sysop can clear an input or normal output filter for a user or thenode_default or user_default.
-clear/wcy [1|all] Clear a WCY filter line
This command allows you to clear (remove) a line in a WCY filter or to remove the whole filter.see CLEAR/SPOTS for a more detailed explanation.
-clear/wwv <callsign> [input] [0-9|all] Clear a WWV filter line
A sysop can clear an input or normal output filter for a user or thenode_default or user_default.
-clear/wwv [1|all] Clear a WWV filter line
This command allows you to clear (remove) a line in a WWV filter or to remove the whole filter.see CLEAR/SPOTS for a more detailed explanation.
-connect <callsign> Start a connection to another DX Cluster
Start a connection process that will culminate in a new connection to theDX cluster <callsign>. This process creates a new 'client' process which willuse the script in /spider/connect/<callsign> to effect the 'chat' exchangenecessary to traverse the network(s) to logon to the cluster <callsign>.
-dbavail Show a list of all the Databases in the system
Title says it all really, this command lists all the databases definedin the system. It is also aliased to SHOW/COMMAND.
-dbcreate <name> Create a database entry
dbcreate <name> chain <name> [<name>..] Create a chained database entry
dbcreate <name> cmd <dxspider command> make a local command available as a DB
DBCREATE allows you to define a database in the system. It doesn't actuallycreate 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: +
+
+ DBCREATE oblast
+
+
+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:
+
+
+ DBCREATE sdx_qsl chain sql_ad
+
+
+No checking is done to see if the any of the chained databases exist, infact it is usually better to do the above staement first then do each ofthe chained databases.Databases can exist offsite. To define a database that lives on another node do:
+
+
+ DBCREATE buckmaster remote gb7dxc
+
+
+Remote databases cannot be chained; however, the last database in a a chain can be a remote database eg:
+
+
+ DBCREATE qsl chain gb7dxc
+
+
+To see what databases have been defined do:
+
+
+ DBAVAIL (or it will have been aliased to SHOW/COMMAND)
+
+
+It would be normal for you to add an entry into your local Aliases fileto allow people to use the 'SHOW/<dbname>' style syntax. So you wouldneed to add a line like:-
+
+
+ 's' => [ .. .. '^sh\w*/buc', 'dbshow buckmaster', 'dbshow', .. .. ],
+
+
+to allow
+
+
+ SH/BUCK g1tlh
+
+
+to work as they may be used to.You can also make local commands available as 'pseudo' databases. Youcan therefore make spider special commands available as a database. Iimagine that this will be primarily useful for remote access from legacy nodes. For example:-
+
+
+ DBCREATE dxqsl cmd show/dxqsl
+
+
+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
+dbcreate <name> remote <node> Create a remote database entry
dbimport <dbname> <filename> Import AK1A data into a database
If you want to import or update data in bulk to a database you can usethis command. It will either create or update entries into an existingdatabase. For example:- +
+
+ DBIMPORT oblast /tmp/OBLAST.FUL
+
+
+will import the standard OBLAST database that comes with AK1A into theoblast database held locally.
+dbremove <dbname> Delete a database
DBREMOVE will completely remove a database entry and also delete any datafile that is associated with it. There is no warning, no comeback, no safety net. For example: +
+
+ DBREMOVE oblast
+
+
+will remove the oblast database from the system and it will also removethe associated datafile.I repeat:There is no warning, no comeback, no safety net.You have been warned.
+dbshow <dbname> <key> Display an entry, if it exists, in a database
debug Set the cluster program into debug mode
Executing this command will only have an effect if you are running the clusterin debug mode i.e. +
+
+ perl -d cluster.pl
+
+
+It will interrupt the cluster just after the debug command has finished.
+delete/usdb <callsign> ... Delete this user from the US State Database
This command will completely remove a one or more callsignsfrom 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.
+delete/user <callsign> ... Delete this user from the User Database
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!
+demonstrate <call> <command> Demonstrate a command to another user
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 andthen sends the output to that user, together with the command that caused it. +
+
+ DEMO g7brn sh/dx iota oc209 DEMO g1tlh set/here
+
+
+Note that this command is similar to SPOOF and will have the same sideeffects. Commands are run at the privilege of the user which is beingdemonstrated to.
+directory List messages
directory <from>-<to> List messages <from> message <to> message
directory <nn> List last <nn> messages
directory all List all messages
directory from <call> List all messages from <call>
directory new List all new messages
directory own List your own messages
directory subject <string> List all messages with <string> in subject
directory to <call> List all messages to <call>
directory-
Sysops can see all users' messages.
-disconnect <call> [<call> ...] Disconnect a user or cluster
Disconnect any <call> connected locally
-dx [by <call>] <freq> <call> <remarks> Send a DX spot
echo <line> Echo the line to the output
export <msgno> <filename> Export a message to a file
Export a message to a file. This command can only be executed on a localconsole with a fully privileged user. The file produced will be in a formready 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 canaccess. For example:- +
+
+ EXPORT 2345 /tmp/a
+
+
+
+export_users [<filename>] Export the users database to ascii
Export the users database to a file in ascii format. If no filenameis 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 factup to 5 generations of the file can be kept each one with an extra 'o' on thesuffix. BE WARNED: this will write to any file you have write access to. No check ismade on the filename (if any) that you specify.
+filtering... Filtering things in DXSpider
forward/latlong <node_call> Send latitude and longitude information to another cluster
This command sends all the latitude and longitude information that yourcluster is holding against callsigns. One advantage of recieving thisinformation is that more locator information is held by you. Thismeans that more locators are given on the DX line assuming you haveSET/DXGRID enabled. This could be a LOT of information though, soit is not recommended on slow links.
-forward/opernam <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, Locationand Homenode. PC41s are only sent for the information that is available.
-help The HELP Command
init <node> Re-initialise a link to an AK1A compatible node
This command attempts to re-initialise a link to a (usually) AK1A nodethat has got confused, usually by a protocol loop of some kind. It maywork - but you usually will be better off simply disconnecting it (orbetter, if it is a real AK1A node, doing an RCMD <node> DISC/F <yournode>).Best of luck - you will need it.
-join <group> Join a chat or conference group
JOIN allows you to join a network wide conference group. To join agroup (called FOC in this case) type:- +
+
+ JOIN FOC
+
+
+See also CHAT, LEAVE, SHOW/CHAT
+kill
As a sysop you can kill any message on the system.
-kill <from msgno>-<to msgno> Delete a range of messages
kill <from>-<to> Remove a range of messages from the system
kill <msgno> [<msgno..] Delete a message from the local system
kill <msgno> [<msgno> ...] Remove or erase a message from the system
You can get rid of any message to or originating from your callsign using this command. You can remove more than one message at a time.
-kill expunge <msgno> [<msgno..] Expunge a message
Deleting a message using the normal KILL commands only marks that messagefor deletion. The actual deletion only happens later (usually two days later).The KILL EXPUNGE command causes the message to be truly deleted more or lessimmediately.It otherwise is used in the same way as the KILL command.
-kill from <call> Remove all messages from a callsign
kill full <msgno> [<msgno..] Delete a message from the whole cluster
kill full <msgno> [<msgno] Remove a message from the entire cluster
Remove this message from the entire cluster system as well as your node.
-kill to <call> Remove all messages to a callsign
kill from <regex> Delete messages FROM a callsign or pattern
kill to <regex> Delete messages TO a callsign or pattern
leave <group> Leave a chat or conference group
LEAVE allows you to leave a network wide conference group. To leave agroup (called FOC in this case) type:- +
+
+ LEAVE FOC
+
+
+See also CHAT, JOIN, SHOW/CHAT
+links Show which nodes is physically connected
This is a quick listing that shows which links are connected andsome information about them. See WHO for a list of all connections.
-load/aliases Reload the command alias table
Reload the /spider/cmd/Aliases file after you have editted it. Youwill need to do this if you change this file whilst the cluster isrunning in order for the changes to take effect.
+load/badmsg Reload the bad msg table
Reload the /spider/msg/badmsg.pl file if you have changed it manually whilstthe 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.
+load/badwords Reload the bad words table
Reload the /spider/data/badwords file if you have changed it manually whilstthe cluster is running. This file contains a list of words which, if foundon certain text portions of PC protocol, will cause those protocol framesto be rejected. It will all put out a message if any of these words areused on the announce, dx and talk commands. The words can be one or more on a line, lines starting with '#' are ignored.
+load/bands Reload the band limits table
Reload the /spider/data/bands.pl file if you have changed it manually whilstthe cluster is running.
+load/cmd_cache Reload the automatic command cache
Normally, if you change a command file in the cmd or local_cmd tree itwill automatially be picked up by the cluster program. Sometimes itcan get confused if you are doing a lot of moving commands about ordelete a command in the local_cmd tree and want to use the normal oneagain. Execute this command to reset everything back to the state itwas just after a cluster restart.
+load/forward Reload the msg forwarding routing table
Reload the /spider/msg/forward.pl file if you have changed itmanually whilst the cluster is running.
+load/keps Load new keps data
load/keps [nn] Load new keps data from message
load/messages Reload the system messages file
If you change the /spider/perl/Messages file (usually whilstfiddling/writing new commands) you can have them take effect during acluster session by executing this command. You need to do this if getsomething like :-unknown message 'xxxx' in lang 'en'
+load/prefixes Reload the prefix table
Reload the /spider/data/prefix_data.pl file if you have changed itmanually whilst the cluster is running.
+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 defaultit will request the last 10 spots and 5 WWVs from the node you select. The node must be connected locally.You can request any number of spots or wwv and although they will be appendedto your databases they will not duplicate any that have recently been added (the last 2 days for spots and last month for WWV data).
-msg <cmd> <msgno> [data ... ] Alter various message parameters
Alter message parameters like To, From, Subject, whether private or bulletinor return receipt (RR) is required or whether to keep this message from timingout. +
+
+ 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
+
+
+You can look at the status of a message by using:-
+
+
+ STAT/MSG <msgno>
+
+
+This will display more information on the message than DIR does.
+pc <call> <text> Send arbitrary text to a connected callsign
ping <node call> Check the link quality between nodes
This command allows you to send a frame to another cluster node onthe network and get a return frame. The time it takes to do thisis a good indication of the quality of the link. The actual timeit takes is output to the console in seconds.Any visible cluster node can be PINGed.
-rcmd <node call> <cmd> Send a command to another DX Cluster
This command allows you to send nearly any command to another DX Clusternode that is connected to the system. Whether you get any output is dependant on a) whether the other system knowsthat the node callsign of this cluster is in fact a node b) whether theother system is allowing RCMDs from this node and c) whether you havepermission to send this command at all.
-read Read the next unread personal message addressed to you
read <msgno> Read the specified message
You can read any messages that are sent as 'non-personal' and also anymessage either sent by or sent to your callsign.
-read-
As a sysop you may read any message on the system
-reject Set a filter to reject something
Create a filter to reject somethingThere are 2 types of filter, accept and reject. See HELP FILTERING for moreinfo.
-reject/announce <call> [input] [0-9] <pattern> Announce filter sysop version
reject/announce [0-9] <pattern> Set a 'reject' filter line for announce
reject/route <call> [0-9] <pattern> Set an 'reject' filter line for routing
reject/spots <call> [input] [0-9] <pattern> Spot filter sysop version
reject/spots [0-9] <pattern> Set a 'reject' filter line for spots
reject/wcy <call> [input] [0-9] <pattern> WCY filter sysop version
reject/wcy [0-9] <pattern> set a 'reject' WCY filter
reject/wwv <call> [input] [0-9] <pattern> WWV filter sysop version
reject/wwv [0-9] <pattern> set a 'reject' WWV filter
reply Reply (privately) to the last message that you have read
reply <msgno> Reply (privately) to the specified message
reply b <msgno> Reply as a Bulletin to the specified message
reply noprivate <msgno> Reply as a Bulletin to the specified message
reply rr <msgno> Reply to the specified message with read receipt
You can reply to a message and the subject will automatically have"Re:" inserted in front of it, if it isn't already present.You can also use all the extra qualifiers such as RR, PRIVATE, NOPRIVATE, B that you can use with the SEND command (see SENDfor further details)
-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 morecommands 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 MUSTenclose 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 (whichis 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 mustenclose the entire save command in (') characters. Now in fact, this can be varied if you know what you are doing. See theadmin manual for more details.
+send <call> [<call> ...] Send a message to one or more callsigns
send copy <msgno> <call> Send a copy of a message to someone
send noprivate <call> Send a message to all stations
send private <call> Send a personal message
send rr <call> Send a message and ask for a read receipt
set/address <your address> Record your postal address
set/announce Allow announce messages to come out on your terminal
set/anntalk Allow talk like announce messages on your terminal
set/arcluster <call> [<call>..] Make the callsign an AR-Cluster node
set/baddx <call>.. Stop callsigns in a dx spot being propagated
set/badnode <call>.. Stop spots from this node being propagated
set/badspotter <call>.. Stop spots from this callsign being propagated
set/badword <word>.. Stop things with this word being propagated
set/bbs <call> [<call>..] Make the callsign a BBS
set/beep Add a beep to DX and other messages on your terminal
set/clx <call> [<call>..] Make the callsign an CLX node
set/debug <name> Add a debug level to the debug set
set/dx Allow DX messages to come out on your terminal
set/dxcq Show CQ Zones on the end of DX announcements
set/dxgrid Allow QRA Grid Squares on the end of DX announcements
set/dxnet <call> [<call>..] Make the callsign an DXNet node
set/dxitu Show ITU Zones on the end of DX announcements
set/dxstate Allow US State info on the end of DX announcements
set/dxnet <call> [<call>..] Make the callsign an DXNet node
set/echo Make the cluster echo your input
set/email <email> ... Set email address(es) and forward your personals
set/here Tell the system you are present at your terminal
set/homenode <node> Set your normal cluster callsign
set/hops <call> ann|spots|route|wwv|wcy <n> Set hop count
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 protocolmember of its network and can see all spots on it, but nothing either leaksout from it nor goes back into from the rest of the nodes connected to you.You can potentially connect several nodes in this way.
+set/language <lang> Set the language you want to use
You can select the language that you want the cluster to use. Currentlythe languages available are en (English), de (German), es (Spanish) and nl (Dutch).
-You can select the language that you want the cluster to use. Currentlythe languages available are en (English), de (German), es (Spanish),Czech (cz), French (fr), Portuguese (pt), Italian (it) and nl (Dutch).
+set/location <lat & long> Set your latitude and longitude
set/lockout <call> Stop a callsign connecting to the cluster
set/logininfo Inform when a station logs in locally
set/name <your name> Set your name
set/node <call> [<call>..] Make the callsign an AK1A cluster
Tell the system that the call(s) are to be treated as AK1A cluster andfed PC Protocol rather normal user commands.
-set/obscount <count> <call> Set the 'pump-up' obscelence PING counter
From 1.35 onwards neighbouring nodes are pinged at regular intervals (seeSET/PINGINTERVAL), usually 300 seconds or 5 minutes. There is a 'pump-up'counter which is decremented on every outgoing ping and then reset tothe 'obscount' value on every incoming ping. The default value of thisparameter is 2. What this means is that a neighbouring node will be pinged twice at (default) 300 second intervals and if no reply has been heard just beforewhat would be the third attempt, that node is disconnected.If a ping is heard then the obscount is reset to the full value. Usingdefault values, if a node has not responded to a ping within 15 minutes,it is disconnected.You can set this parameter between 1 and 9.It is STRONGLY recommended that you don't change the default.
-set/page <lines per page> Set the lines per page
set/password Set your own password
This command only works for a 'telnet' user (currently). It willonly work if you have a password already set. This initial passwordcan 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 youget it right). You may or may not see the data echoed on the screenas you type, depending on the type of telnet client you have.
-set/password <callsign> <string> Set a users password
The password for a user can only be set by a full sysop. The stringcan contain any characters. The way this field is used depends on context. If it is being used inthe SYSOP command context then you are offered 5 random numbers and youhave to supply the corresponding letters. This is now mainly for ax25connections.If it is being used on incoming telnet connections then, if a passwordis set or the: +
+
+ set/var $main::passwdreq = 1
+
+
+command is executed in the startup script, then a password prompt isgiven after the normal 'login: ' prompt.
+set/pinginterval <time> <nodecall> Set ping time to neighbouring nodes
As from release 1.35 all neighbouring nodes are pinged at regular intervalsin order to determine the rolling quality of the link and, in future, toaffect 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 secondsfor 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/OBSCOUNTfor more information.If you must change it (and it may be useful for internet connected nodeson dynamic IP addresses that go away after a set time of usage) the timecan be specified as:- +
+
+ 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
+
+
+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.
+set/privilege <n> <call> [<call..] Set privilege level on a call
Set the privilege level on a callsign. The privilege levels that pertainto commands are as default:- +
+
+ 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.
+
+
+If you are a sysop and you come in as a normal user on a remote connectionyour privilege will automatically be set to 0.
+set/prompt <string> Set your prompt to <string>
set/qra <locator> Set your QRA Grid locator
set/qth <your qth> Set your QTH
set/register <call> ... Mark a user as registered
set/spider <call> [<call>..] Make the callsign an DXSpider node
Tell the system that the call(s) are to be treated as DXSpider node andfed new style DX Protocol rather normal user commands.
-set/sys_location <lat & long> Set your cluster latitude and longitude
In order to get accurate headings and such like you must tell the systemwhat your latitude and longitude is. If you have not yet done a SET/QRAthen this command will set your QRA locator for you. For example:- +
+
+ SET/LOCATION 52 22 N 0 57 E
+
+
+
+set/sys_qra <locator> Set your cluster QRA Grid locator
set/talk Allow TALK messages to come out on your terminal
set/usdb <call> <state> <city> add/update a US DB callsign
This command allows you to add or alter a callsign in the US statedatabase. Use with extreme caution. Anything you do here will beoverwritten by any weekly updates that affect this callsign +
+
+ set/usdb g1tlh nh downtown rindge
+
+
+see also DELETE/USDB
+set/usstate Allow US State info on the end of DX announcements
set/wcy Allow WCY messages to come out on your terminal
set/wwv Allow WWV messages to come out on your terminal
set/wx Allow WX messages to come out on your terminal
show/baddx Show all the bad dx calls in the system
Display all the bad dx callsigns in the system, see SET/BADDXfor more information.
-show/badnode Show all the bad nodes in the system
Display all the bad node callsigns in the system, see SET/BADNODEfor more information.
-show/badspotter Show all the bad spotters in the system
Display all the bad spotter's callsigns in the system, see SET/BADSPOTTERfor more information.
-show/badword Show all the bad words in the system
Display all the bad words in the system, see SET/BADWORDfor more information.
-show/chat [<group>] [<lines>] Show any chat or conferencing
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 forall groups. If you use a group name then it will show only chat forthat group.
+show/configuration [<node>] Show all the nodes and users visible
show/configuration/node Show all the nodes connected locally
Show all the nodes connected to this node.
-show/connect Show all the active connections
This command shows information on all the active connections known tothe node. This command gives slightly more information than WHO.
-show/contest <year and month> Show all the contests for a month
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:- +
+
+ SH/CONTEST sep2003 SH/CONTEST 03 march
+
+
+
+show/date [<prefix>|<callsign>] Show the local time
This is very nearly the same as SHOW/TIME, the only difference the formatof the date string if no arguments are given.If no prefixes or callsigns are given then this command returns the localtime and UTC as the computer has it right now. If you give some prefixesthen it will show UTC and UTC + the local offset (not including DST) atthe prefixes or callsigns that you specify.
-show/db0sdx <callsign> Show QSL infomation from DB0SDX database
This command queries the DB0SDX QSL server on the internetand returns any information available for that callsign. This serviceis provided for users of this software by http://www.qslinfo.de.See also SHOW/QRZ, SHOW/WM7D.
-show/debug Show what levels of debug information you are logging
show/dx Interrogate the spot database
show/dxcc <prefix> Interrogate the spot database by country
show/dxqsl <callsign> Show any QSL info gathered from spots
The node collects information from the comment fields in spots (thingslike 'VIA EA7WA' or 'QSL-G1TLH') and stores these in a database.This command allows you to interrogate that database and if the callsignis found will display the manager(s) that people have spotted. This information is NOT reliable, but it is normally reasonably accurate ifit is spotted enough times.For example:- +
+
+ sh/dxqsl 4k9w
+
+
+You can check the raw input spots yourself with:-
+
+
+ sh/dx 4k9w qsl
+
+
+This gives you more background information.
+show/dxstats [days] [date] Show the DX Statistics
Show the total DX spots for the last <days> no of days (default is 31), starting from a <date> (default: today).
-show/files [<filearea> [<string>]] List the contents of a filearea
show/filter Show the contents of all the filters you have set
Show the contents of all the filters that are set. This command displaysall the filters set - for all the various categories.
-show/hfstats [days] [date] Show the HF DX Statistics
Show the HF DX spots breakdown by band for the last <days> no of days (default is 31), starting from a <date> (default: today).
-show/hftable [days] [date] [prefix ...] Show the HF DX Spotter Table
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 specifywhich category you want to see. If you leave the category out then all the categories will be listed.
-show/isolate Show list of ISOLATED nodes
show/lockout <prefix>|all Show the list of locked out or excluded callsigns
show/log [<callsign>] Show excerpts from the system log
This command outputs a short section of the system log. On its ownit will output a general logfile. With the optional callsign it willshow output from the log associated with that callsign.
-show/moon [ndays] [<prefix>|<callsign>] Show Moon rise and set times
show/muf <prefix> [<hours>][long] Show the likely propagation to a prefix
show/newconfiguration [<node>] Show all the nodes and users visible
This command allows you to see all the users that can be seenand the nodes to which they are connected. This command produces essentially the same information as SHOW/CONFIGURATION except that it shows all the duplication ofany routes that might be present It also uses a different formatwhich may not take up quite as much space if you don't have anyloops.BE WARNED: the list that is returned can be VERY long
-show/newconfiguration/node Show all the nodes connected locally
Show all the nodes connected to this node in the new format.
-show/node [<callsign> ...] Show the type and version number of nodes
Show the type and version (if connected) of the nodes specified on thecommand line. If no callsigns are specified then a sorted list of allthe non-user callsigns known to the system will be displayed.
-show/prefix <callsign> Interrogate the prefix database
This command takes the <callsign> (which can be a full or partial callsign or a prefix), looks up which internal country number it is and then displays all the relevant prefixes for that countrytogether with the internal country no, the CQ and ITU regions. See also SHOW/DXCC
-show/program Show the locations of all the included program modules
Show the name and location where every program module was load from. Thisis useful for checking where you think you have loaded a .pm file from.
-show/qra <lat> <long> Convert lat/long to a QRA Grid locator
show/qra <locator> [<locator>] Show distance between QRA Grid locators
show/qrz <callsign> Show any callbook details on a callsign
This command queries the QRZ callbook server on the internetand returns any information available for that callsign. This serviceis provided for users of this software by http://www.qrz.com See also SHOW/WM7D for an alternative.
-show/registered [<prefix>] Show the registered users
show/route <callsign> ... Show the route to the callsign
show/satellite <name> [<hours> <interval>] Show tracking data
show/station all [<regex>] Show list of users in the system
show/station [<callsign> ..] Show information about a callsign
show/sun [ndays] [<prefix>|<callsign>] Show sun rise and set times
show/time [<prefix>|<callsign>] Show the local time
If no prefixes or callsigns are given then this command returns the localtime and UTC as the computer has it right now. If you give some prefixesthen it will show UTC and UTC + the local offset (not including DST) atthe prefixes or callsigns that you specify.
-show/usdb [call ..] Show information held on the FCC Call database
show/vhfstats [days] [date] Show the VHF DX Statistics
Show the VHF DX spots breakdown by band for the last <days> no of days (default is 31), starting from a date (default: today).
-show/vhftable [days] [date] [prefix ...] Show the VHF DX Spotter Table
show/wcy Show last 10 WCY broadcasts
show/wcy <n> Show last <n> WCY broadcasts
Display the most recent WCY information that has been received by the system
-show/wm7d <callsign> Show callbook details on a US callsigns
This command queries the WM7D callbook server on the internetand returns any information available for that US callsign. This serviceis provided for users of this software by http://www.wm7d.net.See also SHOW/QRZ.
-show/wwv Show last 10 WWV broadcasts
show/wwv <n> Show last <n> WWV broadcasts
Display the most recent WWV information that has been received by the system
-shutdown Shutdown the cluster
Shutdown the cluster and disconnect all the users
-spoof <call> <command> Do a command as though you are another user
This command is provided so that sysops can set a user's parameters withoutme having to write a special 'sysop' version for every user command. Itallows you to pretend that you are doing the command as the user you specify.eg:- +
+
+ SPOOF G1TLH set/name Dirk SPOOF G1TLH set/qra JO02LQ
+
+
+
+stat/channel [<callsign>] Show the status of a channel on the cluster
Show the internal status of the channel object either for the channel that you are on or else for the callsign that you asked for.Only the fields that are defined (in perl term) will be displayed.
-stat/db <dbname> Show the status of a database
Show the internal status of a database descriptor.Depending on your privilege level you will see more or less information. This command is unlikely to be of much use to anyone other than a sysop.
-stat/msg Show the status of the message system
stat/msg <msgno> Show the status of a message
This command shows the internal status of a message and includes informationsuch as to whom it has been forwarded, its size, origin etc etc.If no message number is given then the status of the message system is displayed.
-stat/route_node <callsign> Show the data in a Route::Node object
stat/route_node all Show list of all Route::Node objects
stat/route_user <callsign> Show the data in a Route::User object
stat/route_user all Show list of all Route::User objects
stat/user [<callsign>] Show the full status of a user
Shows the full contents of a user record including all the secret flagsand stuff.Only the fields that are defined (in perl term) will be displayed.
-sysop Regain your privileges if you login remotely
talk <call> > <node> [<text>] Send a text message to another station via a node
talk <call> [<text>] Send a text message to another station
type <filearea>/<name> Look at the contents of a file in one of the fileareas
uncatchup <node call> all|[msgno> ...] Unmark a message as sent
unset/announce Stop announce messages coming out on your terminal
unset/anntalk Stop talk like announce messages on your terminal
unset/baddx <call>.. Propagate a dx spot with this callsign again
unset/badnode <call>.. Allow spots from this node again
unset/badspotter <call>.. Allow spots from this callsign again
unset/badword <word>.. Propagate things with this word again
unset/beep Stop beeps for DX and other messages on your terminal
unset/debug <name> Remove a debug level from the debug set
You can choose to log several different levels. The levels are +
+
+ chan state msg cron connect
+
+
+You can show what levels you are logging with SHOW/DEBUG
+unset/dx Stop DX messages coming out on your terminal
unset/dxcq Stop CQ Zones on the end of DX announcements
Display both the Spotter's and the Spotted's CQ Zone on the endof a DX announcement (there is just enough room). Some user programscannot 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/USSTATEDo a STAT/USER to see which flags you have set if you are confused.
+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 endof a DX announcement (there is just enough room). Some user programscannot cope with this. You can use this command to reset (or set)this feature.
-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 endof a DX announcement (there is just enough room). Some user programscannot cope with this. You can use this command to reset (or set)this feature.Conflicts with: SET/DXCQ, SET/DXITUDo a STAT/USER to see which flags you have set if you are confused.
+unset/dxstate Stop US State info on the end of DX announcements
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 thetime 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.
-unset/dxitu Stop ITU Zones on the end of DX announcements
Display both the Spotter's and the Spotted's ITU Zone on the endof a DX announcement (there is just enough room). Some user programscannot cope with this. The Spotter's ITU is on the RHS of the time, the Spotted's ITU is on the LHS.Conflicts with: SET/DXGRID, SET/DXCQ, SHOW/USSTATEDo a STAT/USER to see which flags you have set if you are confused.
+unset/echo Stop the cluster echoing your input
If you are connected via a telnet session, different implimentationsof telnet handle echo differently depending on whether you are connected via port 23 or some other port. You can use this commandto 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.
-unset/email Stop personal msgs being forwarded by email
unset/here Tell the system you are absent from your terminal
unset/hops <call> ann|spots|route|wwv|wcy Unset hop count
unset/isolate Stop Isolation of a node from the rest of the network
Remove isolation from a node - SET/ISOLATE
+unset/lockout <call> Allow a callsign to connect to the cluster
unset/logininfo Inform when a station logs out locally
unset/password <call> ... Delete (remove) a user's password
This command allows the sysop to completely delete and remove a password for a user.
+unset/privilege Remove any privilege for this session
You can use this command to 'protect' this session from unauthoriseduse. If you want to get your normal privilege back you will need toeither logout and login again (if you are on a console) or use theSYSOP command.
-unset/prompt Set your prompt back to default
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 normalmotd file (/spider/data/motd) being sent to the user at startup, theuser is sent the motd_nor file instead. Secondly, the non registereduser only has READ-ONLY access to the node. The non-registered usercannot use DX, ANN etc. The only exception to this is that a non-registered user can TALK orSEND messages to the sysop.
+unset/talk Stop TALK messages coming out on your terminal
unset/usstate Stop US State info on the end of DX announcements
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 thetime 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/DXITUDo a STAT/USER to see which flags you have set if you are confused.
+unset/wcy Stop WCY messages coming out on your terminal
unset/wwv Stop WWV messages coming out on your terminal
unset/wx Stop WX messages coming out on your terminal
who Show who is physically connected
This is a quick listing that shows which callsigns are connected andwhat sort of connection they have
-wx <text> Send a weather message to local users
wx full <text> Send a weather message to all cluster users
wx sysop <text> Send a weather message to other clusters only