Below is a complete list of commands available from the cluster prompt. -Most maintenance tasks are automatic but there are some commands that are useful -for a sysop. These are listed below in alphabetical order. The number in -brackets following the command name is the permissions level needed to use -the command. +
CVS stands for "Concurrent Versions System" and the CVS for DXSpider is held +at +Sourceforge. This means +that it is possible to update your DXSpider installation to the latest +sources by using a few simple commands.
-
accept/announce [0-9] <pattern> Set an accept filter
-line for announce
-
-
Create an 'accept this announce' line for a filter. -
An accept filter line means that if the announce matches this filter it is -passed onto the user. See HELP FILTERS for more info. Please read this -to understand how filters work - it will save a lot of grief later on. -
You can use any of the following things in this line:- -
-
-
- info <string> eg: iota or qsl
- by <prefixes> eg: G,M,2
- origin <prefixes>
- origin_dxcc <numbers> eg: 61,62 (from eg: sh/pre G)
- origin_itu <numbers>
- origin_zone <numbers>
- by_dxcc <numbers>
- by_itu <numbers>
- by_zone <numbers>
- channel <prefixes>
- wx 1 filter WX announces
- dest <prefixes> eg: 6MUK,WDX (distros)
-
-some examples:- -
-
-
- acc/ann dest 6MUK
- acc/ann 2 by_zone 14,15,16
- (this could be all on one line: acc/ann dest 6MUK or by_zone 14,15,16)
-
-or -
-
-
- acc/ann by G,M,2
-
-This filter would only allow announces that were posted buy UK stations. -You can use the tag 'all' to accept everything eg: -
-
-
- acc/ann all
-
-but this probably for advanced users... -
-
accept/announce <call> [input] [0-9]<pattern> Announce filter sysop version
-
-
This version allows a sysop to set a filter for a callsign as well as the -default for nodes and users eg:- -
-
-
- accept/ann by G,M,2
- accept/ann input node_default by G,M,2
- accept/ann user_default by G,M,2
-
--
accept/route <call> [0-9] <pattern> Set an 'accept' filter line for routing
-
-
Create an 'accept this routing PC Protocol' line for a filter. -
-
An accept filter line means that if a PC16/17/19/21/24/41/50 matches this filter -it is passed thru that interface. See HELP FILTERING for more info. Please read this -to understand how filters work - it will save a lot of grief later on. -
-
You can use any of the following things in this line:- -
-
-
- call <prefixes> the callsign of the thingy
- call_dxcc <numbers> eg: 61,62 (from eg: sh/pre G)
- call_itu <numbers>
- call_zone <numbers>
- origin <prefixes> really the interface it came in on
- origin_dxcc <numbers> eg: 61,62 (from eg: sh/pre G)
- origin_itu <numbers>
- origin_zone <numbers>
-
--
some examples:- -
-
-
- acc/route gb7djk call_dxcc 61,38 (send only UK+EIRE nodes)
- acc/route gb7djk call gb7djk (equiv to SET/ISOLATE)
-
--
You can use the tag 'all' to accept everything eg: -
-
-
- acc/route all
-
--
accept/announce [0-9] <pattern> Set an accept filter line for spots
-
-
Create an 'accept this spot' line for a filter. -
-
An accept filter line means that if the spot matches this filter it is -passed onto the user. See HELP FILTERS for more info. Please read this -to understand how filters work - it will save a lot of grief later on. -
You can use any of the following things in this line:- -
-
-
- freq <range> eg: 0/30000 or hf or hf/cw or 6m,4m,2m
- on <range> same as 'freq'
- call <prefixes> eg: G,PA,HB9
- info <string> eg: iota or qsl
- by <prefixes>
- call_dxcc <numbers> eg: 61,62 (from eg: sh/pre G)
- call_itu <numbers>
- call_zone <numbers>
- by_dxcc <numbers>
- by_itu <numbers>
- by_zone <numbers>
- origin <prefixes>
- channel <prefixes>
-
--
For frequencies, you can use any of the band names defined in -SHOW/BANDS and you can use a subband name like: cw, rtty, data, ssb - -thus: hf/ssb. You can also just have a simple range like: 0/30000 - -this is more efficient than saying simply: freq HF (but don't get -too hung up about that) -
some examples:- -
-
-
- acc/spot 1 on hf/cw
- acc/spot 2 on vhf and (by_zone 14,15,16 or call_zone 14,15,16)
-
-You can use the tag 'all' to accept everything, eg: -
-
-
- acc/spot 3 all
-
-but this probably for advanced users... -
-
accept/spots <call> [input] [0-9] <pattern> Spot filter sysop version
-
-
This version allows a sysop to set a filter for a callsign as well as the -default for nodes and users eg:- -
-
-
- accept/spot db0sue-7 1 by_zone 14,15,16
- accept/spot node_default all
- set/hops node_default 10
-
- accept/spot user_default by G,M,2
-
--
accept/wcy [0-9] <pattern> set an accept WCY filter
-
-
It is unlikely that you will want to do this, but if you do then you can -filter on the following fields:- -
-
-
- by <prefixes> eg: G,M,2
- origin <prefixes>
- origin_dxcc <numbers> eg: 61,62 (from eg: sh/pre G)
- origin_itu <numbers>
- origin_zone <numbers>
- by_dxcc <numbers>
- by_itu <numbers>
- by_zone <numbers>
- channel <prefixes>
-
--
There are no examples because WCY Broadcasts only come from one place and -you either want them or not (see UNSET/WCY if you don't want them). -
This command is really provided for future use. -
See HELP FILTER for information. -
-
accept/wcy <call> [input] [0-9] <pattern>
-WCY filter sysop version
-
-
This version allows a sysop to set a filter for a callsign as well as the -default for nodes and users eg:- -
-
-
- accept/wcy node_default all
- set/hops node_default 10
-
--
accept/wwv [0-9] <pattern> Set an accept WWV filter
-
-
It is unlikely that you will want to do this, but if you do then you can -filter on the following fields:- -
-
-
- by <prefixes> eg: G,M,2
- origin <prefixes>
- origin_dxcc <numbers> eg: 61,62 (from eg: sh/pre G)
- origin_itu <numbers>
- origin_zone <numbers>
- by_dxcc <numbers>
- by_itu <numbers>
- by_zone <numbers>
- channel <prefixes>
-
-for example -
-
-
- accept/wwv by_zone 4
-
-is probably the only useful thing to do (which will only show WWV broadcasts -by stations in the US). -
See HELP FILTER for information. -
-
accept/wwv <call> [input] [0-9] <pattern>
-WWV filter sysop version
-
-
This version allows a sysop to set a filter for a callsign as well as the -default for nodes and users eg:- -
-
-
- accept/wwv db0sue-7 1 by_zone 4
- accept/wwv node_default all
- set/hops node_default 10
-
- accept/wwv user_default by W,K
-
--
announce <text> Send an announcement to local users
-
-
Send an announcement to LOCAL users only, where <text> is the text -of the announcement you wish to broadcast. If you do not wish to receive -announces, use the set/noannounce command. Any announces made by -a sysop will override set/noannounce. -
-
announce full <text> Send an announcement cluster wide
-
-
This command will send your announcement across the whole cluster -network. -
-
-
announce sysop <text>
-
-
Send an announcement to Sysops only -
-
apropos <string> Search the help database
-
-
Search the help database for <string> (it isn't case sensitive), -and print the names of all the commands that may be relevant. -
-
bye Exit from the cluster
-
-
This will disconnect you from the cluster -
-
catchup <node_call> All|[<msgno> ...] Mark a message as sent
-
-
When you send messages the fact that you have forwarded it to another node -is remembered so that it isn't sent again. When you have a new partner -node and you add their callsign to your /spider/msg/forward.pl file, all -outstanding non-private messages will be forwarded to them. This may well -be ALL the non-private messages. You can prevent this by using these -commmands:- -
-
-
- catchup GB7DJK all
- catchup GB7DJK 300 301 302 303 500-510
-
-and to undo what you have just done:- -
-
-
- uncatchup GB7DJK all
- uncatchup GB7DJK 300 301 302 303 500-510
-
-which will arrange for them to be forward candidates again. -
Order is not important. -
-
clear/spots [1|all] Clear a spot filter line
-
-
This command allows you to clear (remove) a line in a spot filter or to -remove the whole filter. -
If you have a filter:- -
-
-
- acc/spot 1 on hf/cw
- acc/spot 2 on vhf and (by_zone 14,15,16 or call_zone 14,15,16)
-
-and you say:- -
-
-
- clear/spot 1
-
-you will be left with:- -
-
-
- acc/spot 2 on vhf and (by_zone 14,15,16 or call_zone 14,15,16)
-
-If you do: -
-
-
- clear/spot all
-
-the filter will be completely removed. -
-
-
connect <callsign> Start a connection to another DX Cluster
-
-
Start a connection process that will culminate in a new connection to the -DX cluster <callsign>. This process creates a new 'client' process which will -use the script in /spider/connect/<callsign> to effect the 'chat' exchange -necessary to traverse the network(s) to logon to the cluster <callsign>. -
-
dbavail Show a list of all the databases in the system
-
-
The title says it all really, this command lists all the databases defined -in 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> remote <node> Create a remote database
-entry
-
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: -
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, in -fact it is usually better to do the above statement first then do each of -the 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 file -to allow people to use the 'SHOW/<dbname>' style syntax. So you would -need 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. -
See DBIMPORT for the importing of existing AK1A format data to databases. -See DBSHOW for generic database enquiry -
-
dbimport <dbname> Import AK1A data into a database
-
-
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:- -
DBIMPORT oblast /tmp/OBLAST.FUL -
will import the standard OBLAST database that comes with AK1A into the -oblast database held locally. -
-
dbremove <dbname> Delete a database
-
-
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: -
DBREMOVE oblast -
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. -
-
dbshow <dbname> <key> Display an entry, if it exists, in a database
-
-
This is the generic user interface to the database to the database system. -It is expected that the sysop will add an entry to the local Aliases file -so that users can use the more familiar AK1A style of enquiry such as: -
-
-
- SH/BUCK G1TLH
-
-but if he hasn't and the database really does exist (use DBAVAIL or -SHOW/COMMAND to find out) you can do the same thing with: -
-
-
- DBSHOW buck G1TLH
-
--
-
debug Set the cluster program into debug mode
-
-
Executing this command will only have an effect if you are running the cluster -in debug mode i.e. -
-
-
- perl -d cluster.pl
-
-It will interrupt the cluster just after the debug command has finished. -
-
directory List messages
-
directory all List all messages
-directory own List your own messages
-directory new List all new messages
-directory to <call> List all messages to <call>
-directory from <call> List all messages from <call>
-directory subject <string> List all messages with <string> in subject
-directory <nn> List last <nn> messages
-directory <from>-<to> List messages <from> message <to> message
-
List the messages in the messages directory. -
If there is a 'p' one space after the message number then it is a -personal message. If there is a '-' between the message number and the -'p' then this indicates that the message has been read. -
You can use shell escape characters such as '*' and '?' in the <call> -fields. -
You can combine some of the various directory commands together eg:- -
-
-
- DIR TO G1TLH 5
-or
- DIR SUBJECT IOTA 200-250
-
-You can abbreviate all the commands to one letter and use ak1a syntax:- -
-
-
- DIR/T G1* 10
- DIR/S QSL 10-100 5
-
--
-
Works just like the user command except that sysops can see ALL messages. -
-
disconnect <call> [<call> ...] Disconnect a user or node
-
-
Disconnect any <call> connected locally -
-
dx [by <call>] <freq> <call> <remarks> Send a DX spot
-
-
This is how you send a DX Spot to other users. You can, in fact, now -enter the <freq> and the <call> either way round. -
-
-
- DX FR0G 144.600
- DX 144.600 FR0G
- DX 144600 FR0G
-
-will all give the same result. You can add some remarks to the end -of the command and they will be added to the spot. -
-
-
- DX FR0G 144600 this is a test
-
-You can credit someone else by saying:- -
-
-
- DX by G1TLH FR0G 144.600 he isn't on the cluster
-
-The <freq> is compared against the available bands set up in the -cluster. See SHOW/BANDS for more information. -
-
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 -
-
export_users [<filename>] Export the users database to ascii
-
-
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. -
-
forward/latlong <node_call> Send latitude and longitude information to another cluster
-
-
This command sends all the latitude and longitude information that your -cluster is holding against callsigns. One advantage of recieving this -information is that more locator information is held by you. This -means that more locators are given on the DX line assuming you have -set/dxgrid enabled. This could be a LOT of information though, so -it is not recommended on slow links. -
-
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 -and Homenode. PC41s are only sent for the information that is available. -
-
help <cmd> Get help on a command
-
-
All commands can be abbreviated, so SHOW/DX can be abbreviated -to SH/DX, ANNOUNCE can be shortened to AN and so on. -
Look at the APROPOS <string> command which will search the help database -for the <string> you specify and give you a list of likely commands -to look at with HELP. -
-
init <node call> 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. -
-
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). -
-
kill <msgno> [<msgno> ...] Remove or erase a message from the system
-
-kill from <call> Remove all messages from a callsign
-kill to <call> Remove all messages to a callsign
-
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. -
As a sysop you can kill any message on the system. -
-
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! -
-
links Show which nodes are 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. -
-
-
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. -
-
-
load/baddx Reload the bad DX table
-
-
Reload the /spider/data/baddx.pl file if you have changed it manually whilst -the cluster is running. This table contains the DX Calls that, if spotted, -will not be passed on. FR0G and TEST are classic examples. -
-
load/badmsg Reload the bad message table
-
-
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. -
-
load/badwords Reload the badwords file
-
-
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. -
-
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. -
-
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. -
-
load/forward Reload the msg forwarding routing table
-
Reload the /spider/msg/forward.pl file if you have changed it -manually whilst the cluster is running. -
-
load/messages Reload the system messages file
-
-
If you change the /spider/perl/Messages file (usually whilst fiddling/writing ne -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' -
-
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. -
-
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 -it 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 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). -
-
msg <cmd> <msgno> [data ...] Alter various message parameters
-
-
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. -
-
-
- 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 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:- -
pc gb7djk PC33^GB7TLH^GB7DJK^400^ -
You can also use in the same way as a talk command to a connected user but -without any processing, added of "from <blah> to <blah>" or whatever. -
pc G1TLH Try doing that properly!!! -
-
ping <node> Check the link quality between nodes
-
-
his command allows you to send a frame to another cluster node on -the network and get a return frame. The time it takes to do this -is a good indication of the quality of the link. The actual time -it 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 Cluster -node that is connected to the system. -
Whether you get any output is dependant on a) whether the other system knows -that the node callsign of this cluster is in fact a node b) whether the -other system is allowing RCMDs from this node and c) whether you have -permission 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 any -message either sent by or sent to your callsign. -
-
-
read <msgno> Read a message on the system
-
-
As a sysop you may read any message on the system -
-
reject/announce [0-9] <pattern> Set a reject filter
-for announce
-
-
Create an 'reject this announce' line for a filter. -
An reject filter line means that if the announce matches this filter it is -passed onto the user. See HELP FILTERS for more info. Please read this -to understand how filters work - it will save a lot of grief later on. -
You can use any of the following things in this line:- -
-
-
- info <string> eg: iota or qsl
- by <prefixes> eg: G,M,2
- origin <prefixes>
- origin_dxcc <numbers> eg: 61,62 (from eg: sh/pre G)
- origin_itu <numbers>
- origin_zone <numbers>
- by_dxcc <numbers>
- by_itu <numbers>
- by_zone <numbers>
- channel <prefixes>
- wx 1 filter WX announces
- dest <prefixes> eg: 6MUK,WDX (distros)
-
-some examples:- -
-
-
- rej/ann by_zone 14,15,16 and not by G,M,2
-
-You can use the tag 'all' to reject everything eg: -
-
-
- rej/ann all
-
-but this probably for advanced users... -
-
reject/announce <call> [input] [0-9] <pattern> Announce filter sysop version
-
-
This version allows a sysop to set a filter for a callsign as well as the -default for nodes and users eg:- -
-
-
- reject/ann by G,M,2
- reject/ann input node_default by G,M,2
- reject/ann user_default by G,M,2
-
--
reject/route <call> [0-9] <pattern> Set an 'reject' filter line for routing
-
-
Create an 'reject this routing PC Protocol' line for a filter. -
-
An reject filter line means that if a PC16/17/19/21/24/41/50 matches this filter -it is NOT passed thru that interface. See HELP FILTERING for more info. Please -read this to understand how filters work - it will save a lot of grief later on. -You can use any of the following things in this line:- -
-
-
- call <prefixes> the callsign of the thingy
- call_dxcc <numbers> eg: 61,62 (from eg: sh/pre G)
- call_itu <numbers>
- call_zone <numbers>
- origin <prefixes> really the interface it came in on
- origin_dxcc <numbers> eg: 61,62 (from eg: sh/pre G)
- origin_itu <numbers>
- origin_zone <numbers>
-
--
some examples:- -
-
-
- rej/route gb7djk call_dxcc 61,38 (everything except UK+EIRE nodes)
-
--
You can use the tag 'all' to reject everything eg: -
-
-
- rej/route all (equiv to [very] restricted mode)
-
--
reject/spots [0-9] <pattern> Set a reject filter line for spots
-
-
Create a 'reject this spot' line for a filter. -
A reject filter line means that if the spot matches this filter it is -dumped (not passed on). See HELP FILTERS for more info. Please read this -to understand how filters work - it will save a lot of grief later on. -
You can use any of the following things in this line:- -
-
-
- freq <range> eg: 0/30000 or hf or hf/cw or 6m,4m,2m
- on <range> same as 'freq'
- call <prefixes> eg: G,PA,HB9
- info <string> eg: iota or qsl
- by <prefixes>
- call_dxcc <numbers> eg: 61,62 (from eg: sh/pre G)
- call_itu <numbers>
- call_zone <numbers>
- by_dxcc <numbers>
- by_itu <numbers>
- by_zone <numbers>
- origin <prefixes>
- channel <prefixes>
-
-For frequencies, you can use any of the band names defined in -SHOW/BANDS and you can use a subband name like: cw, rtty, data, ssb - -thus: hf/ssb. You can also just have a simple range like: 0/30000 - -this is more efficient than saying simply: on HF (but don't get -too hung up about that) -
some examples:- -
-
-
- rej/spot 1 on hf
- rej/spot 2 on vhf and not (by_zone 14,15,16 or call_zone 14,15,16)
-
-You can use the tag 'all' to reject everything eg: -
-
-
- rej/spot 3 all
-
-but this probably for advanced users... -
-
reject/spots <call> [input] [0-9] <pattern>
-Reject spot filter sysop version
-
-
This version allows a sysop to set a filter for a callsign as well as the -default for nodes and users eg:- -
-
-
- reject/spot db0sue-7 1 by_zone 14,15,16
- reject/spot node_default all
- set/hops node_default 10
-
- reject/spot user_default by G,M,2
-
--
reject/wcy [0-9] <pattern> Set a reject WCY filter
-
-
It is unlikely that you will want to do this, but if you do then you can -filter on the following fields:- -
-
-
- by <prefixes> eg: G,M,2
- origin <prefixes>
- origin_dxcc <numbers> eg: 61,62 (from eg: sh/pre G)
- origin_itu <numbers>
- origin_zone <numbers>
- by_dxcc <numbers>
- by_itu <numbers>
- by_zone <numbers>
- channel <prefixes>
-
-There are no examples because WCY Broadcasts only come from one place and -you either want them or not (see UNSET/WCY if you don't want them). -
This command is really provided for future use. -
See HELP FILTER for information. -
-
reject/wcy <call> [input] [0-9] <pattern>
-WCY reject filter sysop version
-
-
This version allows a sysop to set a filter for a callsign as well as the -default for nodes and users eg:- -
reject/wcy gb7djk all -
-
reject/wwv [0-9] <pattern> Set a reject WWV filter
-
-
It is unlikely that you will want to do this, but if you do then you can -filter on the following fields:- -
-
-
- by <prefixes> eg: G,M,2
- origin <prefixes>
- origin_dxcc <numbers> eg: 61,62 (from eg: sh/pre G)
- origin_itu <numbers>
- origin_zone <numbers>
- by_dxcc <numbers>
- by_itu <numbers>
- by_zone <numbers>
- channel <prefixes>
-
-for example -
-
-
- reject/wwv by_zone 14,15,16
-
-is probably the only useful thing to do (which will only show WWV broadcasts -by stations in the US). -
See HELP FILTER for information. -
-
reject/wwv <call> [input] [0-9] <pattern>
-WWV reject filter sysop version
-
-
This version allows a sysop to set a filter for a callsign as well as the -default for nodes and users eg:- -
-
-
- reject/wwv db0sue-7 1 by_zone 4
- reject/wwv node_default all
-
- reject/wwv user_default by W
-
--
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 SEND -for further details) -
-
send <call> [<call> ...] Send a message to one or more callsigns
-
-send RR <call> Send a message and ask for a read receipt
-send COPY <msgno> <call> Send a copy of a message to someone
-send PRIVATE <call> Send a personal message
-send NOPRIVATE <call> Send a message to all stations
-
All the SEND commands will create a message which will be sent either to -an individual callsign or to one of the 'bulletin' addresses. -
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. -
You can have more than one callsign in all of the SEND commands. -
You can have multiple qualifiers so that you can have for example:- -
-
-
- SEND RR COPY 123 PRIVATE G1TLH G0RDI
-
-which should send a copy of message 123 to G1TLH and G0RDI and you will -receive a read receipt when they have read the message. -
SB is an alias for SEND NOPRIVATE (or send a bulletin in BBS speak) -SP is an alias for SEND PRIVATE -
-
set/address <your_address> Record your postal address
-
-
Literally, record your address details on the cluster. -
-
set/announce Allow announce messages
-
-
Allow announce messages to arrive at your terminal. -
-
set/arcluster <node_call> [<node_call> ...] Make
-the node_call an AR-Cluster type node
-
-
Set the node_call as an AR-Cluster type node -
-
set/baddx <call> Stop words we do not wish to see in the callsign field
-of a dx spot being propagated
-
-
Setting a word as 'baddx' will prevent spots with that word in the callsign -field of a DX spot from going any further. They will not be displayed and they -will not be sent onto other nodes. -
The word must be wriiten in full, no wild cards are allowed eg:- -
-
-
- set/baddx FORSALE VIDEO FR0G
-
-To allow a word again, use the following command ... -
-
-
- unset/baddx VIDEO
-
--
set/badnode <node_call> Stop spots from this node_call
-being propagated
-
-
Setting a callsign as a 'badnode' will prevent spots from that node -going any further. They will not be displayed and they will not be -sent onto other nodes. -
The call can be a full or partial call (or a prefix), eg:- -
-
-
- set/badnode K1TTT
-
-will stop anything from K1TTT (including any SSID's) -
-
-
- unset/badnode K1TTT
-
-will allow spots from him again. -
Use with extreme care. This command may well be superceded by FILTERing. -
-
set/badspotter <call> Stop spots from this callsign being propagated
-
-
Setting a callsign as a 'badspotter' will prevent spots from this callsign -going any further. They will not be displayed and they will not be -sent onto other nodes. -
The call must be written in full, no wild cards are allowed eg:- -
-
-
- set/badspotter VE2STN
-
-will stop anything from VE2STN. If you want SSIDs as well then you must -enter them specifically. -
-
-
- unset/badspotter VE2STN
-
-will allow spots from him again. -
Use with extreme care. This command may well be superceded by FILTERing. -
-
set/beep Add beeps to terminal messages
-
-
Add a beep to DX and other terminal messages. -
-
set/bbs <call> [<call>..]Make <call> a BBS
-
-
set/clx <node_call> [<node_call> ...] Make
-the node_call a CLX type node
-
-
Set the node_call as a CLX type node -
-
set/debug <name> Add a debug level to 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 the show/debug -command. -
You can remove a debug level with unset/debug <name> -
-
set/dxAllow DX messages to arrive at your terminal
-
-
You can stop DX messages with the unset/dx command -
-
set/dxgridAllow grid squares on the end of DX messages
-
-
Some logging programs do not like the additional information at -the end of a DX spot. If this is the case, use the unset/dxgrid -command to remove the grid squares. -
-
set/dxnet <node_call> [<node_call> ...] Make
-the node_call a DXNet type node
-
-
Set the node_call as a DXNet type node -
-
set/echo Make the cluster echo 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. -
You can remove the echo with the unset/echo command -
The setting is stored in your user profile. -
YOU DO NOT NEED TO USE THIS COMMAND IF YOU ARE CONNECTED VIA AX25. -
-
set/here Set the here flag
-
-
Let others on the cluster know you are here by only displaying your -callsign. If you are away from your terminal you can use the unset/here -command to let people know you are away. This simply puts brackets -around your callsign to indicate you are not available. -
-
set/homenode <node_call> Set your home cluster
-
-
Tell the cluster system where you normally connect to. Any Messages sent -to you will normally find their way there should you not be connected. -eg:- -
-
-
- SET/HOMENODE gb7djk
-
--
set/hops <node_call> ann|spots|wwv|wcy <n>
-Set 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 -for currently: announce, spots, wwv and wcy broadcasts. -
-
-
-eg:
- set/hops gb7djk ann 10
- set/hops gb7mbc spots 20
-
-Set SHOW/HOPS for information on what is already set. This command -creates a filter and works in conjunction with the filter system. -
-
set/isolate <node call> 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 -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. -
You can see which nodes are isolated with the show/isolate (1) command. -
You can remove the isolation with the command unset/isolate. -
-
set/language <language> Set the language you wish to use
-
-
You can select the language that you want the cluster to use. Currently -the languages available are en (English) and nl (Dutch). -
-
set/location <lat and long> Set your latitude and longitude
-
-
You can set your latitude and longitude manually or alternatively use the -set/qra command which will do the conversion for you. -
-
-
- set/location 54 04 N 2 02 E
-
--
-
set/sys_location <lat & long> Set your cluster latitude and longitude
-
-
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:- -
-
-
- SET/LOCATION 52 22 N 0 57 E
-
--
set/logininfo Show logins and logouts of nodes and users
-
-
Show users and nodes when they log in and out of the local cluster. You -can stop these messages by using the unset/logininfo command. -
-
-
set/lockout <call> Stop a callsign connecting to the cluster
-
-
You can show who is locked out with the show/lockout command. -To allow the user to connect again, use the unset/lockout command. -
-
set/name <your_name> Set your name
-
-
Tell the cluster what your name is, eg:- -
-
-
- set/name Dirk
-
--
set/node <call> [<call> ...] Make the callsign an AK1A cluster
-
-
Tell the system that the call(s) are to be treated as AK1A cluster and -fed PC Protocol rather normal user commands. -
From version 1.41 you can also set the following types of cluster -
-
-
- set/spider
- set/dxnet
- set/clx
- set/arcluster
-
-To see what your nodes are set to, use the show/nodes command. -
-
set/obscount <count> <node call> Set the 'pump-up' obsolescence counter
-
-
From version 1.35 onwards neighbouring nodes are pinged at regular intervals (see -SET/PINGINTERVAL), usually 300 seconds or 5 minutes. There is a 'pump-up' -counter which is decremented on every outgoing ping and then reset to -the 'obscount' value on every incoming ping. The default value of this -parameter 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 before -what would be the third attempt, that node is disconnected. -
If a ping is heard then the obscount is reset to the full value. Using -default values, if a node has not responded to a ping within 15 minutes, -it is disconnected. -
-
set/page <n> Set the number of lines per page
-
-
Tell the system how many lines you wish on a page when the number of lines -of output from a command is more than this. The default is 20. Setting it -explicitly to 0 will disable paging. -
-
-
- SET/PAGE 30
- SET/PAGE 0
-
-The setting is stored in your user profile. +
THIS IS NOT FOR THE FAINT HEARTED!!! ONLY DO THIS IF YOU HAVE A TEST +INSTALLATION OR ARE WILLING TO HAVE YOUR CLUSTER CRASH ON YOU!!! +THIS MUST BE CONSIDERED AT LEAST BETA TESTING AND MAYBE EVEN ALPHA!! +YOU HAVE BEEN WARNED!!!
+
DID I MENTION..... ONLY DO THIS IF YOU ARE WILLING TO ACCEPT THE +CONSEQUENCES!!!
-
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. The password is the usual 30 character baycom -type password. -
-
set/pinginterval <time> <node call> Set the ping time to neighbouring nodes
-
-
As from version 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 60 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. -
-
set/privilege <n> <call> [<call> ...] Set the privilege level on a call
-
-
Set the privilege level on a callsign. The privilege levels that pertain -to 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 connection -your privilege will automatically be set to 0. -
-
set/spider <node_call> [<node_call> ...] Make
-the node_call a DXSpider type node
-
-
Set the node_call as a DXSpider type node -
-
set/sys_qra <locator> Set your cluster QRA locator
-
-
set/qra <locator> Set your QRA 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:- -
-
-
- SET/QRA JO02LQ
-
--
set/qth <your QTH> Set your QTH
-
-
Tell the system where your are. For example:- -
-
-
- set/qth East Dereham, Norfolk
-
--
set/talk Allow talk messages to be seen at your console
-
-
Allow talk messages to arrive at your console. You can switch off -talks with the unset/talk command. -
-
set/wcy Allow WCY messages to be seen at your console
-
-
Allow WCY information to be seen at your console. You can switch off -WCY messages with the unset/wcy command. -
-
set/wwv Allow WWV messages to be seen at your console
-
-
Allow WWV information to be seen at your console. You can switch off -WWV messages with the unset/wwv command. -
-
set/wx Allow WX messages to be seen at your console
-
-
Allow WX information to be seen at your console. You can switch off -WX messages with the unset/wx command. -
-
show/baddxShow all the bad dx calls in the system
-
-
Display all the bad dx callsigns in the system, see SET/BADDX -for more information. -
-
show/badnode Show all the bad nodes in the system
-
-
Display all the bad node callsigns in the system, see SET/BADNODE -for more information. -
-
show/badspotter Show all the bad spotters in the system
-
-
Display all the bad spotter's callsigns in the system, see SET/BADSPOTTER -for more information. -
-
show/configuration [<node>] Show all visible nodes and their users
-
-
This command allows you to see all the users that can be seen -and the nodes to which they are connected. With the optional node, -you can specify a particular node to look at. -
This command is normally abbreviated to: sh/c -
BE WARNED: the list that is returned can be VERY long -
-
show/configuration/node Show all the nodes connected
-
-
Show all the nodes connected locally and the nodes they have connected. -
-
show/connect Show all the active connections
-
-
This command shows information on all the active connections known to -the node. This command gives slightly more information than WHO. -
-
show/date [<prefix>|<callsign>] Show
-the local time
-
-
This is very nearly the same as SHOW/TIME, the only difference the format -of the date string if no arguments are given. -
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 -then it will show UTC and UTC + the local offset (not including DST) at -the prefixes or callsigns that you specify. -
-
show/debug Show what levels of debug you are logging
-
-
The levels can be set with set/debug -
-
show/dx [options] interrogate the spot database
-
-
If you just type SHOW/DX you will get the last so many spots -(sysop configurable, but usually 10). -
In addition you can add any number of these options in very nearly -any order to the basic SHOW/DX command, they are:- -
-
-
-
-on <band> - eg 160m 20m 2m 23cm 6mm
-on <region> - eg hf vhf uhf shf (see SHOW/BANDS)
-
-<number> - the number of spots you want
-<from>-<to> - <from> spot no <to> spot no in
- the selected list
-
-<prefix> - for a spotted callsign beginning with <prefix>
-*<suffix> - for a spotted callsign ending in <suffix>
-*<string>* - for a spotted callsign containing <string>
-
-day <number> - starting <number> days ago
-day <from>-<to> - <from> days <to> days ago
-
-info <text> - any spots containing <text> in the info or remarks
-
-by <call> - any spots spotted by <call> (spotter <call>
- is the same).
-
-qsl - this automatically looks for any qsl info on the call
- held in the spot database.
-
-iota [<iota>] - If the iota island number is missing it will
- look for the string iota and anything which looks like
- an iota island number. If you specify then it will look
- for that island.
-
-qra [<locator>] - this will look for the specific locator if
- you specify one or else anything that looks like a locator.
-
-e.g. -
-
-
-
- SH/DX 9m0
- SH/DX on 20m info iota
- SH/DX 9a on vhf day 30
- SH/DX rf1p qsl
- SH/DX iota
- SH/DX iota eu-064
- SH/DX qra jn86
-
--
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. -
The options for SHOW/DX also apply to this command. -e.g. -
-
-
-
- SH/DXCC G
- SH/DXCC W on 20m info iota
-
--
show/files [<filearea> [<string>]] List
-the contents of a filearea
-
-
SHOW/FILES on its own will show you a list of the various fileareas -available on the system. To see the contents of a particular file -area type:- -
-
-
- SH/FILES <filearea>
-
-where <filearea> is the name of the filearea you want to see the -contents of. -
You can also use shell globbing characters like '*' and '?' in a -string to see a selection of files in a filearea eg:- -
-
-
- SH/FILES bulletins arld*
-
-See also TYPE - to see the contents of a file. -
-
show/filter Show the filters you have set
-
-
Show the contents of all the filters that are set by you. This command -displays all the filters set - for all the various categories. -
-
show/filter <callsign> Show the filters set by <callsign>
-
-
A sysop can look at any filters that have been set. -
-
show/hops <node_call> [ann|spots|wcy|wwv|] Show the hop counts for a node
-
-
This command shows the hop counts set up for a node. You can specify -which category you want to see. If you leave the category out then -all the categories will be listed. -
-
show/isolate Show a list of isolated nodes
-
-
Show which nodes are currently set to be isolated. -
-
show/lockout Show a list of excluded callsigns
-
-
Show a list of callsigns that have been excluded (locked out) of the -cluster locally with the set/lockout command -
-
show/log [<callsign>] Show excerpts from the system log
-
-
This command outputs a short section of the system log. On its own -it will output a general logfile. With the optional callsign it will -show output from the log associated with that callsign. -
-
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 -locations. -
If you don't specify any prefixes or callsigns, it will show the times for -your QTH (assuming you have set it with either SET/LOCATION or SET/QRA), -together with the current azimuth and elevation. -
In addition, it will show the gain or loss dB relative to the nominal -distance of 385,000Km due to the ellipsoidal nature of the orbit. -
If all else fails it will show the Moonrise and set times for the node -that you are connected to. -
For example:- +
I am of course assuming that you have a machine with both DXSpider and +Internet access running.
-
-
- SH/MOON
- SH/MOON G1TLH W5UN
-
--
show/muf <prefix> [<hours>][long] Show
-the likely propagation to <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 -power of 20dBW and receiver sensitivity of -123dBm (about 0.15muV/10dB SINAD) -
The result predicts the most likely operating frequencies and signal -levels for high frequency (shortwave) radio propagation paths on -specified days of the year and hours of the day. It is most useful for -paths between 250 km and 6000 km, but can be used with reduced accuracy -for paths shorter or longer than this. -
The command uses a routine MINIMUF 3.5 developed by the U.S. Navy and -used to predict the MUF given the predicted flux, day of the year, -hour of the day and geographic coordinates of the transmitter and -receiver. This routine is reasonably accurate for the purposes here, -with a claimed RMS error of 3.8 MHz, but much smaller and less complex -than the programs used by major shortwave broadcasting organizations, -such as the Voice of America. -
The command will display some header information detailing its -assumptions, together with the locations, latitude and longitudes and -bearings. It will then show UTC (UT), local time at the other end -(LT), calculate the MUFs, Sun zenith angle at the midpoint of the path -(Zen) and the likely signal strengths. Then for each frequency for which -the system thinks there is a likelihood of a circuit it prints a value. -
The value is currently a likely S meter reading based on the conventional -6dB / S point scale. If the value has a '+' appended it means that it is -1/2 an S point stronger. If the value is preceeded by an 'm' it means that -there is likely to be much fading and by an 's' that the signal is likely -to be noisy. -
By default SHOW/MUF will show the next two hours worth of data. You -can specify anything up to 24 hours worth of data by appending the no of -hours required after the prefix. For example:- -
-
-
- SH/MUF W
-
-produces: -
-
-
- RxSens: -123 dBM SFI: 159 R: 193 Month: 10 Day: 21
- Power : 20 dBW Distance: 6283 km Delay: 22.4 ms
- Location Lat / Long Azim
- East Dereham, Norfolk 52 41 N 0 57 E 47
- United-States-W 43 0 N 87 54 W 299
- UT LT MUF Zen 1.8 3.5 7.0 10.1 14.0 18.1 21.0 24.9 28.0 50.0
- 18 23 11.5 -35 mS0+ mS2 S3
- 19 0 11.2 -41 mS0+ mS2 S3
-
-indicating that you will have weak, fading circuits on top band and -80m but usable signals on 40m (about S3). -
inputing:- -
-
-
- SH/MUF W 24
-
-will get you the above display, but with the next 24 hours worth of -propagation data. -
-
-
- SH/MUF W L 24
- SH/MUF W 24 Long
-
-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. -
-
show/node [<node_call> ...] 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 -the 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 country -together 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. This -is useful for checking where you think you have loaded a .pm file from. -
-
show/qra <locator> [<locator>] Show the distance
-between locators
-
-show/qra <lat> <long> Convert latitude and longitude to a 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 -to the locator. For example:- -
-
-
-SH/QRA IO92QL
-SH/QRA JN06 IN73
-
-The first example will show the distance and bearing to the locator from -yourself, the second example will calculate the distance and bearing from -the first locator to the second. You can use 4 or 6 character locators. -
It is also possible to convert a latitude and longitude to a locator by -using this command with a latitude and longitude as an argument, for -example:- -
-
-
-SH/QRA 52 41 N 0 58 E
-
--
show/qrz <callsign> Show any callbook details on a callsign
-
-
This command queries the QRZ callbook server on the internet -and returns any information available for that callsign. This service -is provided for users of this software by http://www.qrz.com -
-
show/route <callsign> Show the route to <callsign>
-
-
This command allows you to see to which node the callsigns specified are -connected. It is a sort of inverse sh/config. -
-
-
- sh/route n2tly
-
--
show/satellite <name> [<hours> <interval>]
-Show satellite tracking data
-
-
Show the tracking data from your location to the satellite of your choice -from now on for the next few hours. -
If you use this command without a satellite name it will display a list -of all the satellites known currently to the system. -
If you give a name then you can obtain tracking data of all the passes -that start and finish 5 degrees below the horizon. As default it will -give information for the next three hours for every five minute period. -
You can alter the number of hours and the step size, within certain -limits. -
Each pass in a period is separated with a row of '-----' characters -
So for example:- +
BEFORE YOU EVEN CONSIDER STARTING WITH THIS MAKE A BACKUP OF YOUR +ENTIRE SPIDER TREE!!
-
-
-SH/SAT AO-10
-SH/SAT FENGYUN1 12 2
-
-Assuming you are connected to the Internet, you need to login to the +CVS repository and then update your Spider source. There are several +steps which are listed below ...
-
show/sun [<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. -
If you don't specify any prefixes or callsigns, it will show the times for -your QTH (assuming you have set it with either SET/LOCATION or SET/QRA), -together with the current azimuth and elevation. -
If all else fails it will show the sunrise and set times for the node -that you are connected to. -
For example:- +
First login as the user sysop. Next you need to connect to the CVS +repository. You do this with the command below ...
-
- SH/SUN
- SH/SUN G1TLH K9CW ZS
+cvs -d:pserver:anonymous@cvs.DXSpider.sourceforge.net:/cvsroot/dxspider login
--
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 -then it will show UTC and UTC + the local offset (not including DST) at -the prefixes or callsigns that you specify. -
-
show/wcy Show the last 10 WCY broadcasts
-
-show/wcy <n> Show the last <n> WCY broadcasts
-
Display the most recent WCY information that has been received by the system -
-
show/wwv Show the last 10 WWV broadcasts
-
-show/wwv <n> Show the 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. If you have Spider -set to respawn in /etc/inittab it will of course restart. -
-
spoof <callsign> <command> Run commands as another user
-
-
This is a very simple yet powerful command for the sysop. It allows you to -issue commands as if you were a different user. This is very useful for the -kind of things that users seem to always get wrong.. like home_node for -example. -
-
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/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/msg <msgno> Show the status of a message
+
You will get a password prompt. Simply hit return here and your machine should +return to a normal linux prompt.
-
This command shows the internal status of a message and includes information -such as to whom it has been forwarded, its size, origin etc etc. +
What happens next depends on whether you have an existing installation that +you want to update with the latest and greatest or whether you just want +to see what is there and/or run it on a new machine for testing. +
If you are installing Spider from CVS then change directory to /home/sysop +
If you are wanting to update Spider then cd to /tmp
-
If no message number is given then the status of the message system is -displayed. +
The next step will create a brand new 'spider' directory in your current +directory.
-
stat/route_node <callsign> Show the data in a Route::Node object
-
-
stat/route_user <callsign> Show the data in a Route::User object
-
-
stat/user <callsign> Show the full status of a user
-
-
Shows the full contents of a user record including all the secret flags -and stuff. -
Only the fields that are defined (in perl term) will be displayed. -
-
sysop Regain your privileges if you login remotely
-
-
The system automatically reduces your privilege level to that of a -normal user if you login in remotely. This command allows you to -regain your normal privilege level. It uses the normal system: five -numbers are returned that are indexes into the character array that is -your assigned password (see SET/PASSWORD). The indexes start from -zero. -
You are expected to return a string which contains the characters -required in the correct order. You may intersperse those characters -with others to obscure your reply for any watchers. For example (and -these values are for explanation :-): -
-
- password = 012345678901234567890123456789
- > sysop
- 22 10 15 17 3
+cvs -z3 -d:pserver:anonymous@cvs.DXSpider.sourceforge.net:/cvsroot/dxspider co spider
-you type:- +
This command is all on one line.
-
-
- aa2bbbb0ccc5ddd7xxx3n
- or 2 0 5 7 3
- or 20573
-
-They will all match. If there is no password you will still be offered -numbers but nothing will happen when you input a string. Any match is -case sensitive. +
Hopefully your screen should show you downloading files. The -z3 simply compresses +the download to improve speed. +When this has finished, you will have exactly the same as if you had untarred a full +tarball PLUS some extra directories and files that CVS needs to do the magic that +it does.
-
talk <callsign> Enter talk mode with <callsign>
+
-talk <callsign> <text> Send a text message to <callsign>
-talk <callsign> > <node_call> [<text>]
-Send a text message to <callsign> via <node_call>
Now if you are doing a new installation, that's it. Carry on as if you have +just downloaded and untarred the lastest tarball.
-
Send a short message to any other station that is visible on the cluster -system. You can send it to anyone you can see with a SHOW/CONFIGURATION -command, they don't have to be connected locally. -
The second form of TALK is used when other cluster nodes are connected -with restricted information. This usually means that they don't send -the user information usually associated with logging on and off the cluster. -
If you know that G3JNB is likely to be present on GB7TLH, but you can only -see GB7TLH in the SH/C list but with no users, then you would use the -second form of the talk message. -
If you want to have a ragchew with someone you can leave the text message -out and the system will go into 'Talk' mode. What this means is that a -short message is sent to the recipient telling them that you are in a 'Talking' -frame of mind and then you just type - everything you send will go to the -station that you asked for. -
All the usual announcements, spots and so on will still come out on your -terminal. -
If you want to do something (such as send a spot) you precede the normal -command with a '/' character, eg:- +
If you want to upgrade your current installation then do this ...
- /DX 14001 G1TLH What's a B class licensee doing on 20m CW?
- /HELP talk
+tar cvfz /tmp/s.tgz spider
+cd /
+tar xvfzp /tmp/s.tgz
To leave talk mode type: +
This is assuming you downloaded to the /tmp directory of course.
-
-
- /EX
-
-NOTE: the 'p' on the end of the 'xvfz' is IMPORTANT! It keeps the permissions +correct. YOU WERE LOGGED IN AS THE USER SYSOP WEREN'T YOU????? +
Remember to recompile the C client (cd /spider/src; make)
-
type <filearea>/<name> Look at a file in one of the fileareas
+
At this point the files have been upgraded. You can (usually) restart the cluster +in your own time. However, if you attempt to use any new commands or features +expect it to be fatal! At least your cluster will have been restarted then so it +will be too late to worry about it!
-
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 -enter:- +
Now the magic part! From now on when you want to update, simply connect to the +Internet and then, as the user sysop ...
- TYPE bulletins/arld051
+cd /spider
+cvs -z3 update -d
See also SHOW/FILES to see what fileareas are available and a -list of content. -
-
who Show who is physically connected locally
-
-
This is a quick listing that shows which callsigns are connected and -what 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
-
Weather messages can sometimes be useful if you are experiencing an extreme -that may indicate enhanced conditions -
-
wx sysop <text> Send a weather message to other clusters only
-
-
Send a weather message only to other cluster nodes and not to general users. -
+
and your files will be updated. As above, remember to recompile the "C" client +if it has been updated (CVS will tell you) and restart if any of the perl scripts +have been altered or added, again, CVS will tell you.
+
You will find any changes documented in the /spider/Changes file.