______________________________________________________________________
- 1. Routing and Filtering
+ \e[1m1. Routing and Filtering\e[0m
- 1.1. Introduction
+ \e[1m1.1. Introduction\e[0m
From DXSpider version 1.48, major changes were introduced to the way
node connections are treated. This is part of an ongoing process to
In fact DXSpider has had a simple system for some time which is called
- isolation. This is similar to what in other systems such as clx, is
- called passive mode. A more detailed explanation of isolation is given
+ \e[4misolation\e[24m. This is similar to what in other systems such as \e[1mclx\e[22m, is
+ called \e[4mpassive\e[24m \e[4mmode\e[24m. A more detailed explanation of \e[4misolation\e[24m is given
further below. This system is still available and, for simple
networks, is probably all that you need.
The new functionality introduced in version 1.48 allows filtering the
node and user protocol frames on a "per interface" basis. We call this
- route filtering. This is used instead of isolation.
+ \e[4mroute\e[24m \e[4mfiltering\e[24m. This is used \e[1minstead of \e[4m\e[22misolation\e[24m.
What this really means is that you can control more or less completely
partner nodes. You can also limit what comes into your node from your
partners. It is even possible to control the settings that your
partner node has for the routing information that it sends to you
- (using the rcmd command).
+ (using the \e[4mrcmd\e[24m command).
- 1.2. Route Filters
+ \e[1m1.2. Route Filters\e[0m
Initially when route filters were being tested we generated a
"default" filter. Unfortunately it quickly became apparent that this
The first thing that you must do is determine whether you need to use
- route filtering at all. If you are a "normal" node with two or three
+ route filtering \e[1mat all\e[22m. If you are a "normal" node with two or three
partners and you arranged in an "official" non-looping tree type
- network, then you do not need to do route filtering and you will feel
+ network, then \e[1myou do not need to do route filtering \e[22mand you will feel
a lot better for not getting involved. If you are successfully using
- isolation then you also probably don't need to use route filtering.
+ \e[4misolation\e[24m then you also probably don't need to use route filtering.
To put it simply, you should not mix Isolation and Route Filtering.
explanation.
- 1.3. The node_default filter
+ \e[1m1.3. The node_default filter\e[0m
All normal systems should have a default routing filter and it should
usually be set to send only the normal, unlooped, view of your
- Please be careful if you alter this setting, it will affect ALL your
- links! Remember, this is a default filter for node connections, not a
- per link default.
+ Please be careful if you alter this setting, it will affect \e[4mALL\e[24m your
+ links! Remember, this is a \e[4mdefault\e[24m filter for node connections, not a
+ \e[4mper\e[24m \e[4mlink\e[24m default.
For the default routing filter then you have two real choices: either
acc/route node_default call gb7djk
GB7DJK uses the first of these. The DXCC countries can be obtained
- from the show/prefix command.
+ from the \e[4mshow/prefix\e[24m command.
- The example filters shown control output TO all your partner nodes
+ The example filters shown control \e[4moutput\e[24m \e[1mTO \e[22mall your partner nodes
unless they have a specific filter applied to them (see next section).
- It is also possible to control the incoming routing information that
- you are prepared to accept FROM your partner nodes. The reason this is
+ It is also possible to control the \e[4mincoming\e[24m routing information that
+ you are prepared to accept \e[1mFROM \e[22myour partner nodes. The reason this is
necessary is to make sure that stuff like mail, pings and similar
commands a) go down the correct links and b) don't loop around
excessively. Again using GB7DJK as an example a typical default input
- 1.4. General route filtering
+ \e[1m1.4. General route filtering\e[0m
Exactly the same rules apply for general route filtering. You would
use either an accept filter or a reject filter like this ...
or restricting it quite a lot, in fact making it very nearly like an
- isolated node, like this:-
+ \e[4misolated\e[24m node, like this:-
PC16s for my local users).
- It is possible to write much more complex rules, there are up to 10
+ It is possible to write \e[1mmuch \e[22mmore complex rules, there are up to 10
accept/reject pairs per callsign per filter. For more information see
the next section.
- 1.5. General filter rules
+ \e[1m1.5. General filter rules\e[0m
Upto v1.44 it was not possible for the user to set their own filters.
From v1.45 though that has all changed. It is now possible to set
There are 3 basic commands involved in setting and manipulating
- filters. These are accept, reject and clear. First we will look
+ filters. These are \e[4maccept\e[24m, \e[4mreject\e[24m and \e[4mclear\e[24m. First we will look
generally at filtering. There are a number of things you can filter in
the DXSpider system. They all use the same general mechanism.
the same principles to all types of filter.
- 1.6. Types of filter
+ \e[1m1.6. Types of filter\e[0m
- There are two main types of filter, accept or reject. You can use
+ There are two main types of filter, \e[4maccept\e[24m or \e[4mreject\e[24m. You can use
either to achieve the result you want dependent on your own preference
and which is more simple to do. It is pointless writing 8 lines of
reject filters when 1 accept filter would do the same thing! Each
the filter will be dumped but all else will be accepted. If you use
an accept filter, then ONLY the lines in the filter will be accepted
and all else will be dumped. For example if you have a single line
- accept filter ...
+ \e[4maccept\e[24m filter ...
- then you will ONLY get VHF spots from or to CQ zones 14, 15 and 16.
+ then you will \e[4mONLY\e[24m get VHF spots \e[4mfrom\e[24m or \e[4mto\e[24m CQ zones 14, 15 and 16.
If you set a reject filter like this ...
- Then you will get everything EXCEPT HF CW spots. You could make this
+ Then you will get everything \e[4mEXCEPT\e[24m HF CW spots. You could make this
single filter even more flexible. For example, if you are interested
in IOTA and will work it even on CW even though normally you are not
interested in CW, then you could say ...
You will notice in the above example that the second line has
brackets. Look at the line logically. You can see there are 2
separate sections to it. We are saying reject spots that are VHF or
- above APART from those in zones 14, 15 and 16 (either spotted there or
+ above \e[4mAPART\e[24m from those in zones 14, 15 and 16 (either spotted there or
originated there). If you did not have the brackets to separate the 2
sections, then Spider would read it logically from the front and see a
different expression entirely ...
- 1.7. Filter options
+ \e[1m1.7. Filter options\e[0m
You can filter in several different ways. The options are listed in
the various helpfiles for accept, reject and filter.
- 1.8. Default filters
+ \e[1m1.8. Default filters\e[0m
Sometimes all that is needed is a general rule for node connects.
This can be done with a node_default filter. This rule will always be
to add a rule for the hops for spots also.
- 1.9. Advanced filtering
+ \e[1m1.9. Advanced filtering\e[0m
Once you are happy with the results you get, you may like to
experiment.
Note that the first filter has not been specified with a number. This
will automatically be assumed to be number 1. In this case, we have
- said reject all HF spots in the CW section of the bands but accept all
- others at HF. Also accept anything in VHF and above spotted in or by
- operators in the zones 14, 15 and 16. Each filter slot actually has a
+ said \e[4mreject\e[24m \e[4mall\e[24m \e[4mHF\e[24m \e[4mspots\e[24m \e[4min\e[24m \e[4mthe\e[24m \e[4mCW\e[24m \e[4msection\e[24m \e[4mof\e[24m \e[4mthe\e[24m \e[4mbands\e[24m \e[4mbut\e[24m \e[4maccept\e[24m \e[4mall\e[0m
+ \e[4mothers\e[24m \e[4mat\e[24m \e[4mHF.\e[24m \e[4mAlso\e[24m \e[4maccept\e[24m \e[4manything\e[24m \e[4min\e[24m \e[4mVHF\e[24m \e[4mand\e[24m \e[4mabove\e[24m \e[4mspotted\e[24m \e[4min\e[24m \e[4mor\e[24m \e[4mby\e[0m
+ \e[4moperators\e[24m \e[4min\e[24m \e[4mthe\e[24m \e[4mzones\e[24m \e[4m14,\e[24m \e[4m15\e[24m \e[4mand\e[24m \e[4m16\e[24m. Each filter slot actually has a
'reject' slot and an 'accept' slot. The reject slot is executed BEFORE
the accept slot.
VHF/UHF spots from EU.
- 1.10. Basic hop control
+ \e[1m1.10. Basic hop control\e[0m
In /spider/data you will find a file called hop_table.pl. This is the
file that controls your hop count settings. It has a set of default
You can alter this file at any time, including whilst the cluster is
- running. If you alter the file during runtime, the command load/hops
+ running. If you alter the file during runtime, the command \e[4mload/hops\e[0m
will bring your changes into effect.
- 1.11. Hop Control on Specific Nodes
+ \e[1m1.11. Hop Control on Specific Nodes\e[0m
You can set a callsign specific hop count for any of the standard
filter options so:-
all work on their specific area of the protocol.
- The set/hops command overrides any hops that you have set otherwise.
+ The \e[4mset/hops\e[24m command overrides any hops that you have set otherwise.
- You can show what hops have been set using the show/hops command.
+ You can show what hops have been set using the \e[4mshow/hops\e[24m command.
- 1.12. Isolating networks
+ \e[1m1.12. Isolating networks\e[0m
It is possible to isolate networks from each other on a "gateway" node
- using the set/isolate <node_call> command.
+ using the \e[4mset/isolate\e[24m \e[4m<node_call>\e[24m command.
The effect of this is to partition an isolated network completely from
any information back to the isolated node. There are times when you
would like to forward only spots across a link (maybe during a contest
for example). To do this, isolate the node in the normal way and use
- an acc/spot >call< all filter to override the isolate.
+ an \e[4macc/spot\e[24m \e[4m>call<\e[24m \e[4mall\e[24m filter to override the isolate.
- 1.13. A DXSpider Filtering Tutorial
+ \e[1m1.13. A DXSpider Filtering Tutorial\e[0m
There is now an excellent primer/tutorial on filtering written by Jim
Samuels, W3BG with an introduction by Dave Hawes N3RD that I strongly
Primer
- 2. Other filters
+ \e[1m2. Other filters\e[0m
- 2.1. Filtering Mail
+ \e[1m2.1. Filtering Mail\e[0m
In the /spider/msg directory you will find a file called
badmsg.pl.issue. Rename this to badmsg.pl and edit the file. The
- 2.2. Filtering words from text fields in Announce, Talk and DX spots
+ \e[1m2.2. Filtering words from text fields in Announce, Talk and DX spots\e[0m
From version 1.48 onwards the interface to this has changed. You can
- now use the commands set/badword to add words that you are not
- prepared to see on the cluster, unset/badword to allow that word again
- and show/badword to list the words that you have set.
+ now use the commands \e[4mset/badword\e[24m to add words that you are not
+ prepared to see on the cluster, \e[4munset/badword\e[24m to allow that word again
+ and \e[4mshow/badword\e[24m to list the words that you have set.
- If you have a previous /spider/data/badwords, the first time you start
+ If you have a previous \e[4m/spider/data/badwords\e[24m, the first time you start
the node, it will read and convert this file to the new commands. The
old style file will then be removed.
- 2.3. Stopping (possibly bad) DX Spots from Nodes or Spotters
+ \e[1m2.3. Stopping (possibly bad) DX Spots from Nodes or Spotters\e[0m
There are a number of commands that control whether a spot progresses
- These work in the same as the set/badword command, you can add any
+ These work in the same as the \e[4mset/badword\e[24m command, you can add any
words or callsigns or whatever to the appropriate database. For
example, to stop a spot from a particular node you do:
You can remove a word using the appropriate unset command
- (unset/baddx, unset/badspotter, unset/badnode) or list them using one
- of show/baddx, show/badspotter and show/badnode.
+ (\e[4munset/baddx,\e[24m \e[4munset/badspotter,\e[24m \e[4munset/badnode\e[24m) or list them using one
+ of \e[4mshow/baddx,\e[24m \e[4mshow/badspotter\e[24m and \e[4mshow/badnode\e[24m.
- 3. Mail
+ \e[1m3. Mail\e[0m
DXSpider deals seamlessly with standard AK1A type mail. It supports
both personal and bulletin mail and the sysop has additional commands
will be queued until it has finished.
The cluster mail is automatically deleted after 30 days unless the
- sysop sets the "keep" flag using the msg command.
+ sysop sets the "keep" flag using the \e[4mmsg\e[24m command.
- 3.1. Personal mail
+ \e[1m3.1. Personal mail\e[0m
- Personal mail is sent using the sp command. This is actually the
- default method of sending mail and so a simple s for send will do. A
- full list of the send commands and options is in the command set
+ Personal mail is sent using the \e[4msp\e[24m command. This is actually the
+ default method of sending mail and so a simple \e[4ms\e[24m for send will do. A
+ full list of the send commands and options is in the \e[4mcommand\e[24m \e[4mset\e[0m
section, so I will not duplicate them here.
- 3.2. Bulletin mail
+ \e[1m3.2. Bulletin mail\e[0m
- Bulletin mail is sent by using the sb command. This is one of the
+ Bulletin mail is sent by using the \e[4msb\e[24m command. This is one of the
most common mistakes users make when sending mail. They send a
- bulletin mail with s or sp instead of sb and of course the message
+ bulletin mail with \e[4ms\e[24m or \e[4msp\e[24m instead of \e[4msb\e[24m and of course the message
never leaves the cluster. This can be rectified by the sysop by using
- the msg command.
+ the \e[4mmsg\e[24m command.
Bulletin addresses can be set using the Forward.pl file.
- 3.3. Forward.pl
+ \e[1m3.3. Forward.pl\e[0m
DXSpider receives all and any mail sent to it without any alterations
needed in files. Because personal and bulletin mail are treated
exist in this file, they will get an error.
- 3.4. The msg command
+ \e[1m3.4. The msg command\e[0m
- The msg command is a very powerful and flexible tool for the sysop.
+ The \e[4mmsg\e[24m command is a very powerful and flexible tool for the sysop.
It allows the sysop to alter to and from fields and make other changes
to manage the cluster mail.
user.
- 3.5. Message status
+ \e[1m3.5. Message status\e[0m
You can check on a message from within the cluster by using the
- command stat/msg. This will give you additional information on the
+ command \e[4mstat/msg\e[24m. This will give you additional information on the
message number including which nodes have received it, which node it
was received from and when etc. Here is an example of the output of
the command ...
- 3.6. Filtering mail
+ \e[1m3.6. Filtering mail\e[0m
- This is described in the section on Other filters so I will not
+ This is described in the section on \e[4mOther\e[24m \e[4mfilters\e[24m so I will not
duplicate it here.
- 3.7. Distribution lists
+ \e[1m3.7. Distribution lists\e[0m
Distribution lists are simply a list of users to send certain types of
mail to. An example of this is mail you only wish to send to other
- sysops. In /spider/msg there is a directory called distro. You put
+ sysops. In /spider/msg there is a directory called \e[4mdistro\e[24m. You put
any distibution lists in here. For example, here is a file called
SYSOP.pl that caters for the UK sysops.
list.
- 3.8. BBS interface
+ \e[1m3.8. BBS interface\e[0m
Spider provides a simple BBS interface. No input is required from the
sysop of the cluster at all. The BBS simply sets the cluster as a BBS
using the Forward.pl file very carefully.
- 4. Scripts
+ \e[1m4. Scripts\e[0m
From 1.48 onwards it will become increasingly possible to control
DXSpider's operation with scripts of various kinds.
As usual, any text behind a # is treated as a comment and not read.
To use this file, simply rename it from startup.issue to startup. In
our example above there are three options. The first option is the
- amount of spots that a user can request with the sh/dx command.
+ amount of spots that a user can request with the \e[4msh/dx\e[24m command.
Normally the default is to give 10 spots unless the user specifies
more. Without this line enabled, the maximum a user can request is
100 spots. Depending on your link quality you may wish to enable more
Thirdly, there are 2 default scripts for users and nodes who do not
- have a specifically defined script. These are user_default and
- node_default
+ have a specifically defined script. These are \e[4muser_default\e[24m and
+ \e[4mnode_default\e[0m
- 5. Databases
+ \e[1m5. Databases\e[0m
Spider allows the creation of local or remote databases. It supports
chained databases, allowing several different databases to be scanned
database but will expand with time.
- 5.1. Creating databases
+ \e[1m5.1. Creating databases\e[0m
Creating a database could not be more simple. All the commands are
- sent from the cluster prompt as the sysop user.
+ sent from the cluster prompt as the \e[4msysop\e[24m user.
- To create a database you use the command dbcreate. It can be used in
+ To create a database you use the command \e[4mdbcreate\e[24m. It can be used in
3 different ways like so ..
chain can be a remote database.
- 5.2. Importing databases
+ \e[1m5.2. Importing databases\e[0m
The only databases that Spider can currently import are the standard
AK1A databases such as OBLAST or the DB0SDX qsl and address database.
does not exist.
- 5.3. Checking available databases
+ \e[1m5.3. Checking available databases\e[0m
Once a database is created, you will want to check that it has been
- added. To do this use the dbavail command. This will output the
+ added. To do this use the \e[4mdbavail\e[24m command. This will output the
available databases. For example ...
- 5.4. Looking up databases
+ \e[1m5.4. Looking up databases\e[0m
- To look for information in a defined database, simply use the dbshow
+ To look for information in a defined database, simply use the \e[4mdbshow\e[0m
command, for example ...
will show the information for the callsign G0YLM from the buckmaster
database if it exists. To make things more standard for the users you
can add an entry in the Aliases file so that it looks like a standard
- show command like this ...
+ \e[4mshow\e[24m command like this ...
Now you can simply use show/buckmaster or an abreviation.
- 5.5. Removing databases
+ \e[1m5.5. Removing databases\e[0m
- To delete an existing database you use the dbremove command. For
+ To delete an existing database you use the \e[4mdbremove\e[24m command. For
example ...
created from scratch if you still required it.
- 6. Information, files and useful programs
+ \e[1m6. Information, files and useful programs\e[0m
- 6.1. MOTD
+ \e[1m6.1. MOTD\e[0m
One of the more important things a cluster sysop needs to do is to get
information to his users. The simplest way to do this is to have a
/spider/data called motd and edit it to say whatever you want. It is
purely a text file and will be sent automatically to anyone logging in
to the cluster.
- 6.2. MOTD_NOR
+ \e[1m6.2. MOTD_NOR\e[0m
This message of the day file lives in the same directory as the
standard motd file but is only sent to non-registered users. Once
registered they will receive the same message as any other user.
- 6.3. Downtime message
+ \e[1m6.3. Downtime message\e[0m
If for any reason the cluster is down, maybe for upgrade or
maintenance but the machine is still running, a message can be sent to
actually running.
- 6.4. Other text messages
+ \e[1m6.4. Other text messages\e[0m
You can set other text messages to be read by the user if they input
the file name. This could be for news items or maybe information for
new users. To set this up, make a directory under /spider called
- packclus. Under this directory you can create files called news or
- newuser for example. In fact you can create files with any names you
+ \e[4mpackclus\e[24m. Under this directory you can create files called \e[4mnews\e[24m or
+ \e[4mnewuser\e[24m for example. In fact you can create files with any names you
like. These can be listed by the user with the command ....
- If the file they want to read is called news. You could also set an
- alias for this in the Alias file to allow them just to type news
+ If the file they want to read is called \e[4mnews\e[24m. You could also set an
+ alias for this in the Alias file to allow them just to type \e[4mnews\e[0m
You can also store other information in this directory, either
directly or nested under directories. One use for this would be to
store DX bulletins such as the OPDX bulletins. These can be listed
and read by the user. To keep things tidy, make a directory under
- /spider/packclus called bulletin. Now copy any OPDX or similar
+ /spider/packclus called \e[4mbulletin\e[24m. Now copy any OPDX or similar
bulletins into it. These can be listed by the user in the same way as
- above using the show/files command with an extension for the bulletin
+ above using the \e[4mshow/files\e[24m command with an extension for the bulletin
directory you have just created, like this ....
You can see that in the files area (basically the packclus directory)
- there is a file called news and a directory called bulletin. You can
- also see that dates they were created. In the case of the file news,
+ there is a file called \e[4mnews\e[24m and a directory called \e[4mbulletin\e[24m. You can
+ also see that dates they were created. In the case of the file \e[4mnews\e[24m,
you can also see the time it was last modified, a good clue as to
whether the file has been updated since you last read it. To read the
- file called news you would simply issue the command ....
+ file called \e[4mnews\e[24m you would simply issue the command ....
The page length will of course depend on what you have it set to!
- 6.5. The Aliases file
+ \e[1m6.5. The Aliases file\e[0m
You will find a file in /spider/cmd/ called Aliases. This is the file
that controls what a user gets when issuing a command. It is also
alias for 'news'. This is a file I have created in the
/spider/packclus/ directory where I can inform users of new
developments or points of interest. In it's initial form a user would
- have to use the command type news. The alias allows them to simply
- type news to get the info. Second is an alias for the show/qrz
- command so that those users used to the original show/buck command in
+ have to use the command \e[4mtype\e[24m \e[4mnews\e[24m. The alias allows them to simply
+ type \e[4mnews\e[24m to get the info. Second is an alias for the \e[4mshow/qrz\e[0m
+ command so that those users used to the original \e[4mshow/buck\e[24m command in
AK1A will not get an error, and the rest of the lines are for locally
- created databases so that a user can type show/hftest instead of
- having to use the command dbshow hftest which is not as intuitive.
+ created databases so that a user can type \e[4mshow/hftest\e[24m instead of
+ having to use the command \e[4mdbshow\e[24m \e[4mhftest\e[24m which is not as intuitive.
This file is just an example and you should edit it to your own
- requirements. Once created, simply issue the command load/alias at
+ requirements. Once created, simply issue the command \e[4mload/alias\e[24m at
the cluster prompt as the sysop user and the aliases should be
available.
- 6.6. Console.pl
+ \e[1m6.6. Console.pl\e[0m
In later versions of Spider a simple console program is provided for
the sysop. This has a type ahead buffer with line editing facilities
edit the file with your favourite editor.
- 6.7. Updating kepler data
+ \e[1m6.7. Updating kepler data\e[0m
Spider has a powerful and flexible show/satellite command. In order
for this to be accurate, the kepler data has to be updated regularly.
In general, this data is available as an email or via cluster mail.
Updating it is simple. First you need to export the mail message as a
- file. You do this with the export command from the cluster prompt as
+ file. You do this with the \e[4mexport\e[24m command from the cluster prompt as
the sysop. For example ...
Now login to a VT as sysop and cd /spider/perl. There is a command in
- the perl directory called convkeps.pl. All we need to do now is
+ the perl directory called \e[4mconvkeps.pl\e[24m. All we need to do now is
convert the file like so ...
That is it! the kepler data has been updated.
- 6.8. The QRZ callbook
+ \e[1m6.8. The QRZ callbook\e[0m
- The command sh/qrz will only work once you have followed a few simple
+ The command \e[4msh/qrz\e[24m will only work once you have followed a few simple
steps. First you need to get a user ID and password from qrz.com.
Simply go to the site and create one. Secondly you need to copy the
file /spider/perl/Internet.pm to /spider/local and alter it to match
proprieter of qrz.com for allowing this access.
- 6.9. Connecting logging programs
+ \e[1m6.9. Connecting logging programs\e[0m
There appear to be very few logging programs out there that support
telnet especially the popular ones like LogEQF, Turbolog etc. This
can make it difficult to connect to your own cluster! The way to do
it is to make the logging program think it has a TNC attached to a com
port on the logging PC and 'push' a linux login out to it. This is
- achieved very simply by the use of agetty.
+ achieved very simply by the use of \e[4magetty\e[24m.
All that is required is to add a line in /etc/inittab to have the
Add this after the standard runlevel lines in /etc/inittab. The above
- line works on ttyS1 (com2). Now as root, issue the command telinit q
+ line works on ttyS1 (com2). Now as root, issue the command \e[4mtelinit\e[24m \e[4mq\e[0m
and it should be ready for connection. All that is required is a 3
wire serial lead (tx, rx and signal ground). Tell you logging program
to use 8n1 at 9600 baud and you should see a Linux login prompt.
Login as normal and then telnet from there to the cluster.
- 7. Java Web applet
+ \e[1m7. Java Web applet\e[0m
- In the spider tree will be a directory spider-web. This is a neat
+ In the spider tree will be a directory \e[4mspider-web\e[24m. This is a neat
little java web applet that can be run from a website. The applet
must run on the same machine as the cluster. The included README file
is shown below.
- 8. Web based statistics
+ \e[1m8. Web based statistics\e[0m
From version 1.50, you can use the freeware software MRTG to produce
really nice graphical statistics on your web site. For an example try
Now you are nearly there! Login as the sysop user and change to the
- /spider/html/mrtg/ directory. Now run the command indexmaker as shown
+ /spider/html/mrtg/ directory. Now run the command \e[4mindexmaker\e[24m as shown
below...
This will update the site every 5 minutes.
- 9. Security
+ \e[1m9. Security\e[0m
From version 1.49 DXSpider has some additional security features.
These are not by any means meant to be exhaustive, however they do
security.
- 9.1. Registration
+ \e[1m9.1. Registration\e[0m
The basic principle of registration is simple. If a user is not
registered by the sysop, then they have read-only access to the
cluster. The only thing they can actually send is a talk or a message
to the sysop. In order for them to be able to spot, send announces or
- talks etc the sysop must register them with the set/register command,
+ talks etc the sysop must register them with the \e[4mset/register\e[24m command,
like this ...
section on Information, files and useful programs.
- To unregister a user use unset/register and to show the list of
- registered users, use the command show/register.
+ To unregister a user use \e[4munset/register\e[24m and to show the list of
+ registered users, use the command \e[4mshow/register\e[24m.
- 9.2. Passwords
+ \e[1m9.2. Passwords\e[0m
At the moment, passwords only affect users who login to a DXSpider
cluster node via telnet. If a user requires a password, they can
either set it themselves or have the sysop enter it for them by using
- the set/password command. Any users who already have passwords, such
+ the \e[4mset/password\e[24m command. Any users who already have passwords, such
as remote sysops, will be asked for their passwords automatically by
the cluster. Using passwords in this way means that the user has a
choice on whether to have a password or not. To force the use of
- 10. CVS
+ \e[1m10. CVS\e[0m
- 10.1. CVS from a Linux platform
+ \e[1m10.1. CVS from a Linux platform\e[0m
CVS stands for "Concurrent Versions System" and the CVS for DXSpider
is held at Sourceforge. This means that it is possible to update your
steps which are listed below ...
- First login as the user sysop. Next you need to connect to the CVS
+ First login as the user \e[4msysop\e[24m. Next you need to connect to the CVS
repository. You do this with the command below ...
Now the magic part! From now on when you want to update, simply
- connect to the Internet and then, as the user sysop ...
+ connect to the Internet and then, as the user \e[4msysop\e[24m ...
You will find any changes documented in the /spider/Changes file.
- 10.2. CVS from a Windows platform
+ \e[1m10.2. CVS from a Windows platform\e[0m
After the initial setup, an update to your DXSpider software is no
more than a couple of clicks away. This section is intended to
- 11. The DXSpider Command Reference
+ \e[1m11. The DXSpider Command Reference\e[0m
- 11.1. accept (0)
+ \e[1m11.1. accept (0)\e[0m
- accept Set a filter to accept something
+ \e[1maccept \e[22mSet a filter to accept something
Create a filter to accept somethingThere are 2 types of filter, accept
and reject. See HELP FILTERING for moreinfo.
- 11.2. accept/announce <call> [input] [0-9] <pattern> (8)
+
\e[1m11.2. accept/announce <call> [input] [0-9] <pattern> (8)
\e[0m
- accept/announce <call> [input] [0-9] <pattern> Announce filter sysop
+ \e[1maccept/announce <call> [input] [0-9] <pattern> \e[22mAnnounce filter sysop
version
This version allows a sysop to set a filter for a callsign as well as
- 11.3. accept/announce [0-9] <pattern> (0)
+
\e[1m11.3. accept/announce [0-9] <pattern> (0)
\e[0m
- accept/announce [0-9] <pattern> Set an 'accept' filter line for
+ \e[1maccept/announce [0-9] <pattern> \e[22mSet an 'accept' filter line for
announce
Create an 'accept this announce' line for a filter. An accept filter
but this probably for advanced users...
- 11.4. accept/route <call> [0-9] <pattern> (8)
+
\e[1m11.4. accept/route <call> [0-9] <pattern> (8)
\e[0m
- accept/route <call> [0-9] <pattern> Set an 'accept' filter line for
+ \e[1maccept/route <call> [0-9] <pattern> \e[22mSet an 'accept' filter line for
routing
Create an 'accept this routing PC Protocol' line for a filter. An
- 11.5. accept/spots <call> [input] [0-9] <pattern> (8)
+
\e[1m11.5. accept/spots <call> [input] [0-9] <pattern> (8)
\e[0m
- accept/spots <call> [input] [0-9] <pattern> Spot filter sysop version
+ \e[1maccept/spots <call> [input] [0-9] <pattern> \e[22mSpot filter sysop version
This version allows a sysop to set a filter for a callsign as well as
thedefault for nodes and users eg:-
- 11.6. accept/spots [0-9] <pattern> (0)
+
\e[1m11.6. accept/spots [0-9] <pattern> (0)
\e[0m
- accept/spots [0-9] <pattern> Set an 'accept' filter line for spots
+ \e[1maccept/spots [0-9] <pattern> \e[22mSet 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 ispassed onto the user.
but this probably for advanced users...
- 11.7. accept/wcy <call> [input] [0-9] <pattern> (8)
+
\e[1m11.7. accept/wcy <call> [input] [0-9] <pattern> (8)
\e[0m
- accept/wcy <call> [input] [0-9] <pattern> WCY filter sysop version
+ \e[1maccept/wcy <call> [input] [0-9] <pattern> \e[22mWCY filter sysop version
This version allows a sysop to set a filter for a callsign as well as
thedefault for nodes and users eg:-
- 11.8. accept/wcy [0-9] <pattern> (0)
+
\e[1m11.8. accept/wcy [0-9] <pattern> (0)
\e[0m
- accept/wcy [0-9] <pattern> set an 'accept' WCY filter
+ \e[1maccept/wcy [0-9] <pattern> \e[22mset an 'accept' WCY filter
It is unlikely that you will want to do this, but if you do then you
canfilter on the following fields:-
them).This command is really provided for future use.See HELP FILTER
for information.
- 11.9. accept/wwv <call> [input] [0-9] <pattern> (8)
+
\e[1m11.9. accept/wwv <call> [input] [0-9] <pattern> (8)
\e[0m
- accept/wwv <call> [input] [0-9] <pattern> WWV filter sysop version
+ \e[1maccept/wwv <call> [input] [0-9] <pattern> \e[22mWWV filter sysop version
This version allows a sysop to set a filter for a callsign as well as
thedefault for nodes and users eg:-
- 11.10. accept/wwv [0-9] <pattern> (0)
+
\e[1m11.10. accept/wwv [0-9] <pattern> (0)
\e[0m
- accept/wwv [0-9] <pattern> set an 'accept' WWV filter
+ \e[1maccept/wwv [0-9] <pattern> \e[22mset an 'accept' WWV filter
It is unlikely that you will want to do this, but if you do then you
canfilter on the following fields:-
is probably the only useful thing to do (which will only show WWV
broadcastsby stations in the US).See HELP FILTER for information.
- 11.11. announce <text> (0)
+ \e[1m11.11. announce <text> (0)\e[0m
- announce <text> Send an announcement to LOCAL users only
+ \e[1mannounce <text> \e[22mSend an announcement to LOCAL users only
<text> is the text of the announcement you wish to broadcast
- 11.12. announce full <text> (0)
+ \e[1m11.12. announce full <text> (0)\e[0m
- announce full <text> Send an announcement cluster wide
+ \e[1mannounce full <text> \e[22mSend an announcement cluster wide
This will send your announcement cluster wide
- 11.13. announce sysop <text> (5)
+ \e[1m11.13. announce sysop <text> (5)\e[0m
- announce sysop <text> Send an announcement to Sysops only
+ \e[1mannounce sysop <text> \e[22mSend an announcement to Sysops only
- 11.14. apropos <string> (0)
+ \e[1m11.14. apropos <string> (0)\e[0m
- apropos <string> Search help database for <string>
+ \e[1mapropos <string> \e[22mSearch help database for <string>
Search the help database for <string> (it isn't case sensitive), and
printthe names of all the commands that may be relevant.
- 11.15. blank [<string>] [<nn>] (0)
+ \e[1m11.15. blank [<string>] [<nn>] (0)\e[0m
- blank [<string>] [<nn>] Print nn (default 1) blank lines (or strings)
+ \e[1mblank [<string>] [<nn>] \e[22mPrint nn (default 1) blank lines (or strings)
In its basic form this command prints one or more blank lines. However
ifyou pass it a string it will replicate the string for the width of
prints 'abcabcabcabcabcabc....'This is really only of any use in a
script file and you can print a maximumof 9 lines.
- 11.16. bye (0)
+ \e[1m11.16. bye (0)\e[0m
- bye Exit from the cluster
+ \e[1mbye \e[22mExit from the cluster
This will disconnect you from the cluster
- 11.17. catchup <node call> all|[<msgno> ...] (5)
+ \e[1m11.17. catchup <node call> all|[<msgno> ...] (5)\e[0m
- catchup <node call> all|[<msgno> ...] Mark a message as sent
+ \e[1mcatchup <node call> all|[<msgno> ...] \e[22mMark a message as sent
- 11.18. chat <group> <text> (0)
+ \e[1m11.18. chat <group> <text> (0)\e[0m
- chat <group> <text> Chat or Conference to a group
+ \e[1mchat <group> <text> \e[22mChat 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
See also JOIN, LEAVE, SHOW/CHAT
- 11.19. clear/announce <callsign> [input] [0-9|all] (8)
+ \e[1m11.19. clear/announce <callsign> [input] [0-9|all] (8)\e[0m
- clear/announce <callsign> [input] [0-9|all] Clear a announce filter
+ \e[1mclear/announce <callsign> [input] [0-9|all] \e[22mClear a announce filter
line
A sysop can clear an input or normal output filter for a user or
thenode_default or user_default.
- 11.20. clear/announce [1|all] (0)
+ \e[1m11.20. clear/announce [1|all] (0)\e[0m
- clear/announce [1|all] Clear a announce filter line
+ \e[1mclear/announce [1|all] \e[22mClear 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.
- 11.21. clear/route <callsign> [input] [0-9|all] (8)
+ \e[1m11.21. clear/route <callsign> [input] [0-9|all] (8)\e[0m
- clear/route <callsign> [input] [0-9|all] Clear a route filter line
+ \e[1mclear/route <callsign> [input] [0-9|all] \e[22mClear a route filter line
A sysop can clear an input or normal output filter for a user or
thenode_default or user_default.
- 11.22. clear/route [1|all] (0)
+ \e[1m11.22. clear/route [1|all] (0)\e[0m
- clear/route [1|all] Clear a route filter line
+ \e[1mclear/route [1|all] \e[22mClear 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.
- 11.23. clear/spots <callsign> [input] [0-9|all] (8)
+ \e[1m11.23. clear/spots <callsign> [input] [0-9|all] (8)\e[0m
- clear/spots <callsign> [input] [0-9|all] Clear a spot filter line
+ \e[1mclear/spots <callsign> [input] [0-9|all] \e[22mClear a spot filter line
A sysop can clear an input or normal output filter for a user or
thenode_default or user_default.
- 11.24. clear/spots [0-9|all] (0)
+ \e[1m11.24. clear/spots [0-9|all] (0)\e[0m
- clear/spots [0-9|all] Clear a spot filter line
+ \e[1mclear/spots [0-9|all] \e[22mClear 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:-
the filter will be completely removed.
- 11.25. clear/wcy <callsign> [input] [0-9|all] (8)
+ \e[1m11.25. clear/wcy <callsign> [input] [0-9|all] (8)\e[0m
- clear/wcy <callsign> [input] [0-9|all] Clear a WCY filter line
+ \e[1mclear/wcy <callsign> [input] [0-9|all] \e[22mClear a WCY filter line
A sysop can clear an input or normal output filter for a user or
thenode_default or user_default.
- 11.26. clear/wcy [1|all] (0)
+ \e[1m11.26. clear/wcy [1|all] (0)\e[0m
- clear/wcy [1|all] Clear a WCY filter line
+ \e[1mclear/wcy [1|all] \e[22mClear 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.
- 11.27. clear/wwv <callsign> [input] [0-9|all] (8)
+ \e[1m11.27. clear/wwv <callsign> [input] [0-9|all] (8)\e[0m
- clear/wwv <callsign> [input] [0-9|all] Clear a WWV filter line
+ \e[1mclear/wwv <callsign> [input] [0-9|all] \e[22mClear a WWV filter line
A sysop can clear an input or normal output filter for a user or
thenode_default or user_default.
- 11.28. clear/wwv [1|all] (0)
+ \e[1m11.28. clear/wwv [1|all] (0)\e[0m
- clear/wwv [1|all] Clear a WWV filter line
+ \e[1mclear/wwv [1|all] \e[22mClear 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.
- 11.29. connect <callsign> (5)
+ \e[1m11.29. connect <callsign> (5)\e[0m
- connect <callsign> Start a connection to another DX Cluster
+ \e[1mconnect <callsign> \e[22mStart 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
'chat' exchangenecessary to traverse the network(s) to logon to the
cluster <callsign>.
- 11.30. dbavail (0)
+ \e[1m11.30. dbavail (0)\e[0m
- dbavail Show a list of all the Databases in the system
+ \e[1mdbavail \e[22mShow 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.
- 11.31. dbcreate <name> (9)
+ \e[1m11.31. dbcreate <name> (9)\e[0m
- dbcreate <name> Create a database entry
+ \e[1mdbcreate <name> \e[22mCreate a database entry
- 11.32. dbcreate <name> chain <name> [<name>..] (9)
+ \e[1m11.32. dbcreate <name> chain <name> [<name>..] (9)\e[0m
- dbcreate <name> chain <name> [<name>..] Create a chained database
+ \e[1mdbcreate <name> chain <name> [<name>..] \e[22mCreate a chained database
entry
- 11.33. dbcreate <name> cmd <dxspider command> (9)
+ \e[1m11.33. dbcreate <name> cmd <dxspider command> (9)\e[0m
- dbcreate <name> cmd <dxspider command> make a local command available
+ \e[1mdbcreate <name> cmd <dxspider command> \e[22mmake a local command available
as a DB
DBCREATE allows you to define a database in the system. It doesn't
locally. See DBIMPORT for the importing of existing AK1A format data
to databases.See DBSHOW for generic database enquiry
- 11.34. dbcreate <name> remote <node> (9)
+ \e[1m11.34. dbcreate <name> remote <node> (9)\e[0m
- dbcreate <name> remote <node> Create a remote database entry
+ \e[1mdbcreate <name> remote <node> \e[22mCreate a remote database entry
- 11.35. dbimport <dbname> <filename> (9)
+ \e[1m11.35. dbimport <dbname> <filename> (9)\e[0m
- dbimport <dbname> <filename> Import AK1A data into a database
+ \e[1mdbimport <dbname> <filename> \e[22mImport 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
will import the standard OBLAST database that comes with AK1A into
theoblast database held locally.
- 11.36. dbremove <dbname> (9)
+ \e[1m11.36. dbremove <dbname> (9)\e[0m
- dbremove <dbname> Delete a database
+ \e[1mdbremove <dbname> \e[22mDelete 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,
removethe associated datafile.I repeat:There is no warning, no come-
back, no safety net.You have been warned.
- 11.37. dbshow <dbname> <key> (0)
+ \e[1m11.37. dbshow <dbname> <key> (0)\e[0m
- dbshow <dbname> <key> Display an entry, if it exists, in a database
+ \e[1mdbshow <dbname> <key> \e[22mDisplay 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
- 11.38. debug (9)
+ \e[1m11.38. debug (9)\e[0m
- debug Set the cluster program into debug mode
+ \e[1mdebug \e[22mSet the cluster program into debug mode
Executing this command will only have an effect if you are running the
clusterin debug mode i.e.
It will interrupt the cluster just after the debug command has fin-
ished.
- 11.39. delete/usdb <callsign> ... (9)
+ \e[1m11.39. delete/usdb <callsign> ... (9)\e[0m
- delete/usdb <callsign> ... Delete this user from the US State Database
+ \e[1mdelete/usdb <callsign> ... \e[22mDelete 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.
- 11.40. delete/user <callsign> ... (9)
+ \e[1m11.40. delete/user <callsign> ... (9)\e[0m
- delete/user <callsign> ... Delete this user from the User Database
+ \e[1mdelete/user <callsign> ... \e[22mDelete 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!
- 11.41. demonstrate <call> <command> (9)
+ \e[1m11.41. demonstrate <call> <command> (9)\e[0m
- demonstrate <call> <command> Demonstrate a command to another user
+ \e[1mdemonstrate <call> <command> \e[22mDemonstrate 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
sideeffects. Commands are run at the privilege of the user which is
beingdemonstrated to.
- 11.42. directory (0)
+ \e[1m11.42. directory (0)\e[0m
- directory List messages
+ \e[1mdirectory \e[22mList messages
- 11.43. directory <from>-<to> (0)
+ \e[1m11.43. directory <from>-<to> (0)\e[0m
- directory <from>-<to> List messages <from> message <to> message
+ \e[1mdirectory <from>-<to> \e[22mList 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
- 11.44. directory <nn> (0)
+ \e[1m11.44. directory <nn> (0)\e[0m
- directory <nn> List last <nn> messages
+ \e[1mdirectory <nn> \e[22mList last <nn> messages
- 11.45. directory all (0)
+ \e[1m11.45. directory all (0)\e[0m
- directory all List all messages
+ \e[1mdirectory all \e[22mList all messages
- 11.46. directory from <call> (0)
+ \e[1m11.46. directory from <call> (0)\e[0m
- directory from <call> List all messages from <call>
+ \e[1mdirectory from <call> \e[22mList all messages from <call>
- 11.47. directory new (0)
+ \e[1m11.47. directory new (0)\e[0m
- directory new List all new messages
+ \e[1mdirectory new \e[22mList all new messages
- 11.48. directory own (0)
+ \e[1m11.48. directory own (0)\e[0m
- directory own List your own messages
+ \e[1mdirectory own \e[22mList your own messages
- 11.49. directory subject <string> (0)
+ \e[1m11.49. directory subject <string> (0)\e[0m
- directory subject <string> List all messages with <string> in subject
+ \e[1mdirectory subject <string> \e[22mList all messages with <string> in subject
- 11.50. directory to <call> (0)
+ \e[1m11.50. directory to <call> (0)\e[0m
- directory to <call> List all messages to <call>
+ \e[1mdirectory to <call> \e[22mList all messages to <call>
- 11.51. directory- (5)
+ \e[1m11.51. directory- (5)\e[0m
- directory-
+ \e[1mdirectory-\e[0m
Sysops can see all users' messages.
- 11.52. disconnect <call> [<call> ...] (8)
+ \e[1m11.52. disconnect <call> [<call> ...] (8)\e[0m
- disconnect <call> [<call> ...] Disconnect a user or cluster
+ \e[1mdisconnect <call> [<call> ...] \e[22mDisconnect a user or cluster
Disconnect any <call> connected locally
- 11.53. dx [by <call>] <freq> <call> <remarks> (0)
+ \e[1m11.53. dx [by <call>] <freq> <call> <remarks> (0)\e[0m
- dx [by <call>] <freq> <call> <remarks> Send a DX spot
+ \e[1mdx [by <call>] <freq> <call> <remarks> \e[22mSend a DX spot
This is how you send a DX Spot to other users. You can, in fact,
nowenter the <freq> and the <call> either way round.
The <freq> is compared against the available bands set up in the clus-
ter. See SHOW/BANDS for more information.
- 11.54. echo <line> (0)
+ \e[1m11.54. echo <line> (0)\e[0m
- echo <line> Echo the line to the output
+ \e[1mecho <line> \e[22mEcho the line to the output
This command is useful in scripts and so forth for printing theline
that you give to the command to the output. You can use thisin
on the output.
- 11.55. export <msgno> <filename> (9)
+ \e[1m11.55. export <msgno> <filename> (9)\e[0m
- export <msgno> <filename> Export a message to a file
+ \e[1mexport <msgno> <filename> \e[22mExport 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
- 11.56. export_users [<filename>] (9)
+ \e[1m11.56. export_users [<filename>] (9)\e[0m
- export_users [<filename>] Export the users database to ascii
+ \e[1mexport_users [<filename>] \e[22mExport 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
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.
- 11.57. filtering... (0)
+ \e[1m11.57. filtering... (0)\e[0m
- filtering... Filtering things in DXSpider
+ \e[1mfiltering... \e[22mFiltering things in DXSpider
There are a number of things you can filter in the DXSpider system.
Theyall use the same general mechanism.In general terms you can create
else on HF.The next filter line lets through just VHF/UHF spots from
EU.
- 11.58. forward/latlong <node_call> (8)
+ \e[1m11.58. forward/latlong <node_call> (8)\e[0m
- forward/latlong <node_call> Send latitude and longitude information to
+ \e[1mforward/latlong <node_call> \e[22mSend latitude and longitude information to
another cluster
This command sends all the latitude and longitude information that
haveSET/DXGRID enabled. This could be a LOT of information though,
soit is not recommended on slow links.
- 11.59. forward/opernam <call> (1)
+ \e[1m11.59. forward/opernam <call> (1)\e[0m
- forward/opernam <call> Send out information on this <call> to all
+ \e[1mforward/opernam <call> \e[22mSend out information on this <call> to all
clusters
This command sends out any information held in the user file which can
Locationand Homenode. PC41s are only sent for the information that is
available.
- 11.60. help (0)
+ \e[1m11.60. help (0)\e[0m
- help The HELP Command
+ \e[1mhelp \e[22mThe HELP Command
HELP is available for a number of commands. The syntax is:-
which will search the help databasefor the <string> you specify and
give you a list of likely commandsto look at with HELP.
- 11.61. init <node> (5)
+ \e[1m11.61. init <node> (5)\e[0m
- init <node> Re-initialise a link to an AK1A compatible node
+ \e[1minit <node> \e[22mRe-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
(orbetter, if it is a real AK1A node, doing an RCMD <node> DISC/F
<yournode>).Best of luck - you will need it.
- 11.62. join <group> (0)
+ \e[1m11.62. join <group> (0)\e[0m
- join <group> Join a chat or conference group
+ \e[1mjoin <group> \e[22mJoin a chat or conference group
JOIN allows you to join a network wide conference group. To join
agroup (called FOC in this case) type:-
See also CHAT, LEAVE, SHOW/CHAT
- 11.63. kill (5)
+ \e[1m11.63. kill (5)\e[0m
- kill
+ \e[1mkill\e[0m
As a sysop you can kill any message on the system.
- 11.64. kill <from msgno>-<to msgno> (0)
+ \e[1m11.64. kill <from msgno>-<to msgno> (0)\e[0m
- kill <from msgno>-<to msgno> Delete a range of messages
+ \e[1mkill <from msgno>-<to msgno> \e[22mDelete a range of messages
- 11.65. kill <from>-<to> (5)
+ \e[1m11.65. kill <from>-<to> (5)\e[0m
- kill <from>-<to> Remove a range of messages from the system
+ \e[1mkill <from>-<to> \e[22mRemove a range of messages from the system
- 11.66. kill <msgno> [<msgno..] (0)
+ \e[1m11.66. kill <msgno> [<msgno..] (0)\e[0m
- kill <msgno> [<msgno..] Delete a message from the local system
+ \e[1mkill <msgno> [<msgno..] \e[22mDelete a message from the local system
- 11.67. kill <msgno> [<msgno> ...] (0)
+ \e[1m11.67. kill <msgno> [<msgno> ...] (0)\e[0m
- kill <msgno> [<msgno> ...] Remove or erase a message from the system
+ \e[1mkill <msgno> [<msgno> ...] \e[22mRemove 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.
- 11.68. kill expunge <msgno> [<msgno..] (6)
+ \e[1m11.68. kill expunge <msgno> [<msgno..] (6)\e[0m
- kill expunge <msgno> [<msgno..] Expunge a message
+ \e[1mkill expunge <msgno> [<msgno..] \e[22mExpunge a message
Deleting a message using the normal KILL commands only marks that
messagefor deletion. The actual deletion only happens later (usually
truly deleted more or lessimmediately.It otherwise is used in the same
way as the KILL command.
- 11.69. kill from <call> (5)
+ \e[1m11.69. kill from <call> (5)\e[0m
- kill from <call> Remove all messages from a callsign
+ \e[1mkill from <call> \e[22mRemove all messages from a callsign
- 11.70. kill full <msgno> [<msgno..] (5)
+ \e[1m11.70. kill full <msgno> [<msgno..] (5)\e[0m
- kill full <msgno> [<msgno..] Delete a message from the whole cluster
+ \e[1mkill full <msgno> [<msgno..] \e[22mDelete a message from the whole cluster
Delete a message from the local system. You will only be able todelete
messages that you have originated or been sent (unless you arethe
system. This uses the subject field, so any messages that have exactly
thesame subject will be deleted. Beware!
- 11.71. kill full <msgno> [<msgno] (5)
+ \e[1m11.71. kill full <msgno> [<msgno] (5)\e[0m
- kill full <msgno> [<msgno] Remove a message from the entire cluster
+ \e[1mkill full <msgno> [<msgno] \e[22mRemove a message from the entire cluster
Remove this message from the entire cluster system as well as your
node.
- 11.72. kill to <call> (5)
+ \e[1m11.72. kill to <call> (5)\e[0m
- kill to <call> Remove all messages to a callsign
+ \e[1mkill to <call> \e[22mRemove all messages to a callsign
- 11.73. kill from <regex> (0)
+ \e[1m11.73. kill from <regex> (0)\e[0m
- kill from <regex> Delete messages FROM a callsign or pattern
+ \e[1mkill from <regex> \e[22mDelete messages FROM a callsign or pattern
- 11.74. kill to <regex> (0)
+ \e[1m11.74. kill to <regex> (0)\e[0m
- kill to <regex> Delete messages TO a callsign or pattern
+ \e[1mkill to <regex> \e[22mDelete messages TO a callsign or pattern
- 11.75. leave <group> (0)
+ \e[1m11.75. leave <group> (0)\e[0m
- leave <group> Leave a chat or conference group
+ \e[1mleave <group> \e[22mLeave a chat or conference group
LEAVE allows you to leave a network wide conference group. To leave
agroup (called FOC in this case) type:-
See also CHAT, JOIN, SHOW/CHAT
- 11.76. links (0)
+ \e[1m11.76. links (0)\e[0m
- links Show which nodes is physically connected
+ \e[1mlinks \e[22mShow 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.
- 11.77. load/aliases (9)
+ \e[1m11.77. load/aliases (9)\e[0m
- load/aliases Reload the command alias table
+ \e[1mload/aliases \e[22mReload 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.
- 11.78. load/badmsg (9)
+ \e[1m11.78. load/badmsg (9)\e[0m
- load/badmsg Reload the bad msg table
+ \e[1mload/badmsg \e[22mReload 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
each message. If any of them match then that message is immediately
deleted on receipt.
- 11.79. load/badwords (9)
+ \e[1m11.79. load/badwords (9)\e[0m
- load/badwords Reload the bad words table
+ \e[1mload/badwords \e[22mReload 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
words can be one or more on a line, lines starting with '#' are
ignored.
- 11.80. load/bands (9)
+ \e[1m11.80. load/bands (9)\e[0m
- load/bands Reload the band limits table
+ \e[1mload/bands \e[22mReload the band limits table
Reload the /spider/data/bands.pl file if you have changed it manually
whilstthe cluster is running.
- 11.81. load/cmd_cache (9)
+ \e[1m11.81. load/cmd_cache (9)\e[0m
- load/cmd_cache Reload the automatic command cache
+ \e[1mload/cmd_cache \e[22mReload 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
oneagain. Execute this command to reset everything back to the state
itwas just after a cluster restart.
- 11.82. load/forward (9)
+ \e[1m11.82. load/forward (9)\e[0m
- load/forward Reload the msg forwarding routing table
+ \e[1mload/forward \e[22mReload the msg forwarding routing table
Reload the /spider/msg/forward.pl file if you have changed itmanually
whilst the cluster is running.
- 11.83. load/keps (5)
+ \e[1m11.83. load/keps (5)\e[0m
- load/keps Load new keps data
+ \e[1mload/keps \e[22mLoad new keps data
- 11.84. load/keps [nn] (5)
+ \e[1m11.84. load/keps [nn] (5)\e[0m
- load/keps [nn] Load new keps data from message
+ \e[1mload/keps [nn] \e[22mLoad new keps data from message
If there is no message number then reload the current Keps data
fromthe Keps.pm data file. You create this file by running
vkeps.pl on it and then load the data, all in one step.These messages
are sent to ALL by GB7DJK (and others) from time to time.
- 11.85. load/messages (9)
+ \e[1m11.85. load/messages (9)\e[0m
- load/messages Reload the system messages file
+ \e[1mload/messages \e[22mReload 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'
- 11.86. load/prefixes (9)
+ \e[1m11.86. load/prefixes (9)\e[0m
- load/prefixes Reload the prefix table
+ \e[1mload/prefixes \e[22mReload the prefix table
Reload the /spider/data/prefix_data.pl file if you have changed
itmanually whilst the cluster is running.
- 11.87. merge <node> [<no spots>/<no wwv>] (5)
+ \e[1m11.87. merge <node> [<no spots>/<no wwv>] (5)\e[0m
- merge <node> [<no spots>/<no wwv>] Ask for the latest spots and WWV
+ \e[1mmerge <node> [<no spots>/<no wwv>] \e[22mAsk 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
they will not duplicate any that have recently been added (the last 2
days for spots and last month for WWV data).
- 11.88. msg <cmd> <msgno> [data ... ] (9)
+ \e[1m11.88. msg <cmd> <msgno> [data ... ] (9)\e[0m
- msg <cmd> <msgno> [data ... ] Alter various message parameters
+ \e[1mmsg <cmd> <msgno> [data ... ] \e[22mAlter various message parameters
Alter message parameters like To, From, Subject, whether private or
bulletinor return receipt (RR) is required or whether to keep this
This will display more information on the message than DIR does.
- 11.89. pc <call> <text> (8)
+ \e[1m11.89. pc <call> <text> (8)\e[0m
- pc <call> <text> Send arbitrary text to a connected callsign
+ \e[1mpc <call> <text> \e[22mSend arbitrary text to a connected callsign
Send some arbitrary text to a locally connected callsign. Noprocessing
is done on the text. This command allows you to send PCProtocol to
nected user butwithout any processing, added of "from <blah> to <blah"
or whatever.
- 11.90. ping <node call> (1)
+ \e[1m11.90. ping <node call> (1)\e[0m
- ping <node call> Check the link quality between nodes
+ \e[1mping <node call> \e[22mCheck 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
output to the console in seconds.Any visible cluster node can be
PINGed.
- 11.91. rcmd <node call> <cmd> (1)
+ \e[1m11.91. rcmd <node call> <cmd> (1)\e[0m
- rcmd <node call> <cmd> Send a command to another DX Cluster
+ \e[1mrcmd <node call> <cmd> \e[22mSend 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
is allowing RCMDs from this node and c) whether you havepermission to
send this command at all.
- 11.92. read (0)
+ \e[1m11.92. read (0)\e[0m
- read Read the next unread personal message addressed to you
+ \e[1mread \e[22mRead the next unread personal message addressed to you
- 11.93. read <msgno> (0)
+ \e[1m11.93. read <msgno> (0)\e[0m
- read <msgno> Read the specified message
+ \e[1mread <msgno> \e[22mRead 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.
- 11.94. read- (5)
+ \e[1m11.94. read- (5)\e[0m
- read-
+ \e[1mread-\e[0m
As a sysop you may read any message on the system
- 11.95. reject (0)
+ \e[1m11.95. reject (0)\e[0m
- reject Set a filter to reject something
+ \e[1mreject \e[22mSet a filter to reject something
Create a filter to reject somethingThere are 2 types of filter, accept
and reject. See HELP FILTERING for moreinfo.
- 11.96. reject/announce <call> [input] [0-9] <pattern> (8)
+
\e[1m11.96. reject/announce <call> [input] [0-9] <pattern> (8)
\e[0m
- reject/announce <call> [input] [0-9] <pattern> Announce filter sysop
+ \e[1mreject/announce <call> [input] [0-9] <pattern> \e[22mAnnounce filter sysop
version
This version allows a sysop to set a filter for a callsign as well as
- 11.97. reject/announce [0-9] <pattern> (0)
+
\e[1m11.97. reject/announce [0-9] <pattern> (0)
\e[0m
- reject/announce [0-9] <pattern> Set a 'reject' filter line for
+ \e[1mreject/announce [0-9] <pattern> \e[22mSet a 'reject' filter line for
announce
Create an 'reject this announce' line for a filter. A reject filter
but this probably for advanced users...
- 11.98. reject/route <call> [0-9] <pattern> (8)
+
\e[1m11.98. reject/route <call> [0-9] <pattern> (8)
\e[0m
- reject/route <call> [0-9] <pattern> Set an 'reject' filter line for
+ \e[1mreject/route <call> [0-9] <pattern> \e[22mSet an 'reject' filter line for
routing
Create an 'reject this routing PC Protocol' line for a filter. An
as with ACCEPT/ROUTE 'by' is now a synonym for 'call'.
- 11.99. reject/spots <call> [input] [0-9] <pattern> (8)
+
\e[1m11.99. reject/spots <call> [input] [0-9] <pattern> (8)
\e[0m
- reject/spots <call> [input] [0-9] <pattern> Spot filter sysop version
+ \e[1mreject/spots <call> [input] [0-9] <pattern> \e[22mSpot filter sysop version
This version allows a sysop to set a filter for a callsign as well as
thedefault for nodes and users eg:-
- 11.100. reject/spots [0-9] <pattern> (0)
+
\e[1m11.100. reject/spots [0-9] <pattern> (0)
\e[0m
- reject/spots [0-9] <pattern> Set a 'reject' filter line for spots
+ \e[1mreject/spots [0-9] <pattern> \e[22mSet 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 isdumped (not passed
but this probably for advanced users...
- 11.101. reject/wcy <call> [input] [0-9] <pattern> (8)
+
\e[1m11.101. reject/wcy <call> [input] [0-9] <pattern> (8)
\e[0m
- reject/wcy <call> [input] [0-9] <pattern> WCY filter sysop version
+ \e[1mreject/wcy <call> [input] [0-9] <pattern> \e[22mWCY filter sysop version
This version allows a sysop to set a filter for a callsign as well as
thedefault for nodes and users eg:-
- 11.102. reject/wcy [0-9] <pattern> (0)
+
\e[1m11.102. reject/wcy [0-9] <pattern> (0)
\e[0m
- reject/wcy [0-9] <pattern> set a 'reject' WCY filter
+ \e[1mreject/wcy [0-9] <pattern> \e[22mset a 'reject' WCY filter
It is unlikely that you will want to do this, but if you do then you
canfilter on the following fields:-
them).This command is really provided for future use.See HELP FILTER
for information.
- 11.103. reject/wwv <call> [input] [0-9] <pattern> (8)
+
\e[1m11.103. reject/wwv <call> [input] [0-9] <pattern> (8)
\e[0m
- reject/wwv <call> [input] [0-9] <pattern> WWV filter sysop version
+ \e[1mreject/wwv <call> [input] [0-9] <pattern> \e[22mWWV filter sysop version
This version allows a sysop to set a filter for a callsign as well as
thedefault for nodes and users eg:-
- 11.104. reject/wwv [0-9] <pattern> (0)
+
\e[1m11.104. reject/wwv [0-9] <pattern> (0)
\e[0m
- reject/wwv [0-9] <pattern> set a 'reject' WWV filter
+ \e[1mreject/wwv [0-9] <pattern> \e[22mset a 'reject' WWV filter
It is unlikely that you will want to do this, but if you do then you
canfilter on the following fields:-
is probably the only useful thing to do (which will only show WWV
broadcastsby stations in the US).See HELP FILTER for information.
- 11.105. reply (0)
+ \e[1m11.105. reply (0)\e[0m
- reply Reply (privately) to the last message that you have read
+ \e[1mreply \e[22mReply (privately) to the last message that you have read
- 11.106. reply <msgno> (0)
+ \e[1m11.106. reply <msgno> (0)\e[0m
- reply <msgno> Reply (privately) to the specified message
+ \e[1mreply <msgno> \e[22mReply (privately) to the specified message
- 11.107. reply b <msgno> (0)
+ \e[1m11.107. reply b <msgno> (0)\e[0m
- reply b <msgno> Reply as a Bulletin to the specified message
+ \e[1mreply b <msgno> \e[22mReply as a Bulletin to the specified message
- 11.108. reply noprivate <msgno> (0)
+ \e[1m11.108. reply noprivate <msgno> (0)\e[0m
- reply noprivate <msgno> Reply as a Bulletin to the specified message
+ \e[1mreply noprivate <msgno> \e[22mReply as a Bulletin to the specified message
- 11.109. reply rr <msgno> (0)
+ \e[1m11.109. reply rr <msgno> (0)\e[0m
- reply rr <msgno> Reply to the specified message with read receipt
+ \e[1mreply rr <msgno> \e[22mReply 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)
- 11.110. save [-d -t -a] <filename> "<cmd>" [...] (9)
+ \e[1m11.110. save [-d -t -a] <filename> "<cmd>" [...] (9)\e[0m
- save [-d -t -a] <filename> "<cmd>" [...] Save command output to a file
+ \e[1msave [-d -t -a] <filename> "<cmd>" [...] \e[22mSave command output to a file
This sysop only cammand allows you to save the output of one or
morecommands to a file. For example:-
this can be varied if you know what you are doing. See theadmin manual
for more details.
- 11.111. send <call> [<call> ...] (0)
+ \e[1m11.111. send <call> [<call> ...] (0)\e[0m
- send <call> [<call> ...] Send a message to one or more callsigns
+ \e[1msend <call> [<call> ...] \e[22mSend a message to one or more callsigns
- 11.112. send copy <msgno> <call> (0)
+ \e[1m11.112. send copy <msgno> <call> (0)\e[0m
- send copy <msgno> <call> Send a copy of a message to someone
+ \e[1msend copy <msgno> <call> \e[22mSend a copy of a message to someone
- 11.113. send noprivate <call> (0)
+ \e[1m11.113. send noprivate <call> (0)\e[0m
- send noprivate <call> Send a message to all stations
+ \e[1msend noprivate <call> \e[22mSend a message to all stations
All the SEND commands will create a message which will be sent either
toan individual callsign or to one of the 'bulletin' addresses. SEND
themessage. You can carry on with the message until you are ready to
send it.
- 11.114. send private <call> (0)
+ \e[1m11.114. send private <call> (0)\e[0m
- send private <call> Send a personal message
+ \e[1msend private <call> \e[22mSend a personal message
- 11.115. send rr <call> (0)
+ \e[1m11.115. send rr <call> (0)\e[0m
- send rr <call> Send a message and ask for a read receipt
+ \e[1msend rr <call> \e[22mSend a message and ask for a read receipt
- 11.116. set/address <your address> (0)
+ \e[1m11.116. set/address <your address> (0)\e[0m
- set/address <your address> Record your postal address
+ \e[1mset/address <your address> \e[22mRecord your postal address
- 11.117. set/announce (0)
+ \e[1m11.117. set/announce (0)\e[0m
- set/announce Allow announce messages to come out on your terminal
+ \e[1mset/announce \e[22mAllow announce messages to come out on your terminal
- 11.118. set/anntalk (0)
+ \e[1m11.118. set/anntalk (0)\e[0m
- set/anntalk Allow talk like announce messages on your terminal
+ \e[1mset/anntalk \e[22mAllow talk like announce messages on your terminal
- 11.119. set/arcluster <call> [<call>..] (5)
+ \e[1m11.119. set/arcluster <call> [<call>..] (5)\e[0m
- set/arcluster <call> [<call>..] Make the callsign an AR-Cluster node
+ \e[1mset/arcluster <call> [<call>..] \e[22mMake the callsign an AR-Cluster node
- 11.120. set/baddx <call>.. (8)
+ \e[1m11.120. set/baddx <call>.. (8)\e[0m
- set/baddx <call>.. Stop callsigns in a dx spot being propagated
+ \e[1mset/baddx <call>.. \e[22mStop callsigns in a dx spot being propagated
- 11.121. set/badnode <call>.. (8)
+ \e[1m11.121. set/badnode <call>.. (8)\e[0m
- set/badnode <call>.. Stop spots from this node being propagated
+ \e[1mset/badnode <call>.. \e[22mStop spots from this node being propagated
- 11.122. set/badspotter <call>.. (8)
+ \e[1m11.122. set/badspotter <call>.. (8)\e[0m
- set/badspotter <call>.. Stop spots from this callsign being propagated
+ \e[1mset/badspotter <call>.. \e[22mStop spots from this callsign being propagated
- 11.123. set/badword <word>.. (8)
+ \e[1m11.123. set/badword <word>.. (8)\e[0m
- set/badword <word>.. Stop things with this word being propagated
+ \e[1mset/badword <word>.. \e[22mStop things with this word being propagated
- 11.124. set/bbs <call> [<call>..] (5)
+ \e[1m11.124. set/bbs <call> [<call>..] (5)\e[0m
- set/bbs <call> [<call>..] Make the callsign a BBS
+ \e[1mset/bbs <call> [<call>..] \e[22mMake the callsign a BBS
- 11.125. set/beep (0)
+ \e[1m11.125. set/beep (0)\e[0m
- set/beep Add a beep to DX and other messages on your terminal
+ \e[1mset/beep \e[22mAdd a beep to DX and other messages on your terminal
- 11.126. set/clx <call> [<call>..] (5)
+ \e[1m11.126. set/clx <call> [<call>..] (5)\e[0m
- set/clx <call> [<call>..] Make the callsign an CLX node
+ \e[1mset/clx <call> [<call>..] \e[22mMake the callsign an CLX node
- 11.127. set/debug <name> (9)
+ \e[1m11.127. set/debug <name> (9)\e[0m
- set/debug <name> Add a debug level to the debug set
+ \e[1mset/debug <name> \e[22mAdd a debug level to the debug set
- 11.128. set/dx (0)
+ \e[1m11.128. set/dx (0)\e[0m
- set/dx Allow DX messages to come out on your terminal
+ \e[1mset/dx \e[22mAllow DX messages to come out on your terminal
- 11.129. set/dxcq (0)
+ \e[1m11.129. set/dxcq (0)\e[0m
- set/dxcq Show CQ Zones on the end of DX announcements
+ \e[1mset/dxcq \e[22mShow CQ Zones on the end of DX announcements
- 11.130. set/dxgrid (0)
+ \e[1m11.130. set/dxgrid (0)\e[0m
- set/dxgrid Allow QRA Grid Squares on the end of DX announcements
+ \e[1mset/dxgrid \e[22mAllow QRA Grid Squares on the end of DX announcements
- 11.131. set/dxitu (0)
+ \e[1m11.131. set/dxitu (0)\e[0m
- set/dxitu Show ITU Zones on the end of DX announcements
+ \e[1mset/dxitu \e[22mShow ITU Zones on the end of DX announcements
- 11.132. set/dxnet <call> [<call>..] (5)
+ \e[1m11.132. set/dxnet <call> [<call>..] (5)\e[0m
- set/dxnet <call> [<call>..] Make the callsign an DXNet node
+ \e[1mset/dxnet <call> [<call>..] \e[22mMake the callsign an DXNet node
- 11.133. set/echo (0)
+ \e[1m11.133. set/echo (0)\e[0m
- set/echo Make the cluster echo your input
+ \e[1mset/echo \e[22mMake the cluster echo your input
- 11.134. set/email <email> ... (0)
+ \e[1m11.134. set/email <email> ... (0)\e[0m
- set/email <email> ... Set email address(es) and forward your personals
+ \e[1mset/email <email> ... \e[22mSet email address(es) and forward your personals
- 11.135. set/here (0)
+ \e[1m11.135. set/here (0)\e[0m
- set/here Tell the system you are present at your terminal
+ \e[1mset/here \e[22mTell the system you are present at your terminal
- 11.136. set/homenode <node> (0)
+ \e[1m11.136. set/homenode <node> (0)\e[0m
- set/homenode <node> Set your normal cluster callsign
+ \e[1mset/homenode <node> \e[22mSet your normal cluster callsign
Tell the cluster system where you normally connect to. Any Messages
sentto you will normally find their way there should you not be
- 11.137. set/hops <call> ann|spots|route|wwv|wcy <n> (8)
+ \e[1m11.137. set/hops <call> ann|spots|route|wwv|wcy <n> (8)\e[0m
- set/hops <call> ann|spots|route|wwv|wcy <n> Set hop count
+ \e[1mset/hops <call> ann|spots|route|wwv|wcy <n> \e[22mSet hop count
- 11.138. set/isolate (9)
+ \e[1m11.138. set/isolate (9)\e[0m
- set/isolate Isolate a node from the rest of the network
+ \e[1mset/isolate \e[22mIsolate 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
connected to you.You can potentially connect several nodes in this
way.
- 11.139. set/language <lang> (0)
+ \e[1m11.139. set/language <lang> (0)\e[0m
- set/language <lang> Set the language you want to use
+ \e[1mset/language <lang> \e[22mSet 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),Czech (cz), French (fr), Portuguese (pt), Italian (it) and
nl (Dutch).
- 11.140. set/location <lat & long> (0)
+ \e[1m11.140. set/location <lat & long> (0)\e[0m
- set/location <lat & long> Set your latitude and longitude
+ \e[1mset/location <lat & long> \e[22mSet your latitude and longitude
- 11.141. set/lockout <call> (9)
+ \e[1m11.141. set/lockout <call> (9)\e[0m
- set/lockout <call> Stop a callsign connecting to the cluster
+ \e[1mset/lockout <call> \e[22mStop a callsign connecting to the cluster
- 11.142. set/logininfo (0)
+ \e[1m11.142. set/logininfo (0)\e[0m
- set/logininfo Inform when a station logs in locally
+ \e[1mset/logininfo \e[22mInform when a station logs in locally
- 11.143. set/name <your name> (0)
+ \e[1m11.143. set/name <your name> (0)\e[0m
- set/name <your name> Set your name
+ \e[1mset/name <your name> \e[22mSet your name
Tell the system what your name is eg:-
- 11.144. set/node <call> [<call>..] (5)
+ \e[1m11.144. set/node <call> [<call>..] (5)\e[0m
- set/node <call> [<call>..] Make the callsign an AK1A cluster
+ \e[1mset/node <call> [<call>..] \e[22mMake 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.
- 11.145. set/obscount <count> <call> (8)
+ \e[1m11.145. set/obscount <count> <call> (8)\e[0m
- set/obscount <count> <call> Set the 'pump-up' obscelence PING counter
+ \e[1mset/obscount <count> <call> \e[22mSet 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
between 1 and 9.It is STRONGLY recommended that you don't change the
default.
- 11.146. set/page <lines per page> (0)
+ \e[1m11.146. set/page <lines per page> (0)\e[0m
- set/page <lines per page> Set the lines per page
+ \e[1mset/page <lines per page> \e[22mSet the lines per page
Tell the system how many lines you wish on a page when the number of
lineof output from a command is more than this. The default is 20.
The setting is stored in your user profile.
- 11.147. set/password (0)
+ \e[1m11.147. set/password (0)\e[0m
- set/password Set your own password
+ \e[1mset/password \e[22mSet 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
the screenas you type, depending on the type of telnet client you
have.
- 11.148. set/password <callsign> <string> (9)
+ \e[1m11.148. set/password <callsign> <string> (9)\e[0m
- set/password <callsign> <string> Set a users password
+ \e[1mset/password <callsign> <string> \e[22mSet 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.
command is executed in the startup script, then a password prompt
isgiven after the normal 'login: ' prompt.
- 11.149. set/pinginterval <time> <nodecall> (9)
+ \e[1m11.149. set/pinginterval <time> <nodecall> (9)\e[0m
- set/pinginterval <time> <nodecall> Set ping time to neighbouring nodes
+ \e[1mset/pinginterval <time> <nodecall> \e[22mSet 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
this value too low may annoy your neighbours beyond the point of
endurance!You can switch this off by setting it to 0.
- 11.150. set/privilege <n> <call> [<call..] (9)
+ \e[1m11.150. set/privilege <n> <call> [<call..] (9)\e[0m
- set/privilege <n> <call> [<call..] Set privilege level on a call
+ \e[1mset/privilege <n> <call> [<call..] \e[22mSet privilege level on a call
Set the privilege level on a callsign. The privilege levels that
pertainto commands are as default:-
If you are a sysop and you come in as a normal user on a remote con-
nectionyour privilege will automatically be set to 0.
- 11.151. set/prompt <string> (0)
+ \e[1m11.151. set/prompt <string> (0)\e[0m
- set/prompt <string> Set your prompt to <string>
+ \e[1mset/prompt <string> \e[22mSet your prompt to <string>
- 11.152. set/qra <locator> (0)
+ \e[1m11.152. set/qra <locator> (0)\e[0m
- set/qra <locator> Set your QRA Grid locator
+ \e[1mset/qra <locator> \e[22mSet your QRA Grid locator
Tell the system what your QRA (or Maidenhead) locator is. If you have
notdone a SET/LOCATION then your latitude and longitude will be set
- 11.153. set/qth <your qth> (0)
+ \e[1m11.153. set/qth <your qth> (0)\e[0m
- set/qth <your qth> Set your QTH
+ \e[1mset/qth <your qth> \e[22mSet your QTH
Tell the system where you are. For example:-
- 11.154. set/register <call> ... (9)
+ \e[1m11.154. set/register <call> ... (9)\e[0m
- set/register <call> ... Mark a user as registered
+ \e[1mset/register <call> ... \e[22mMark a user as registered
- 11.155. set/spider <call> [<call>..] (5)
+ \e[1m11.155. set/spider <call> [<call>..] (5)\e[0m
- set/spider <call> [<call>..] Make the callsign an DXSpider node
+ \e[1mset/spider <call> [<call>..] \e[22mMake 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.
- 11.156. set/sys_location <lat & long> (9)
+ \e[1m11.156. set/sys_location <lat & long> (9)\e[0m
- set/sys_location <lat & long> Set your cluster latitude and longitude
+ \e[1mset/sys_location <lat & long> \e[22mSet 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
- 11.157. set/sys_qra <locator> (9)
+ \e[1m11.157. set/sys_qra <locator> (9)\e[0m
- set/sys_qra <locator> Set your cluster QRA Grid locator
+ \e[1mset/sys_qra <locator> \e[22mSet your cluster QRA Grid locator
- 11.158. set/talk (0)
+ \e[1m11.158. set/talk (0)\e[0m
- set/talk Allow TALK messages to come out on your terminal
+ \e[1mset/talk \e[22mAllow TALK messages to come out on your terminal
- 11.159. set/usdb <call> <state> <city> (9)
+ \e[1m11.159. set/usdb <call> <state> <city> (9)\e[0m
- set/usdb <call> <state> <city> add/update a US DB callsign
+ \e[1mset/usdb <call> <state> <city> \e[22madd/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
see also DELETE/USDB
- 11.160. set/usstate (0)
+ \e[1m11.160. set/usstate (0)\e[0m
- set/usstate Allow US State info on the end of DX announcements
+ \e[1mset/usstate \e[22mAllow US State info on the end of DX announcements
- 11.161. set/wcy (0)
+ \e[1m11.161. set/wcy (0)\e[0m
- set/wcy Allow WCY messages to come out on your terminal
+ \e[1mset/wcy \e[22mAllow WCY messages to come out on your terminal
- 11.162. set/wwv (0)
+ \e[1m11.162. set/wwv (0)\e[0m
- set/wwv Allow WWV messages to come out on your terminal
+ \e[1mset/wwv \e[22mAllow WWV messages to come out on your terminal
- 11.163. set/wx (0)
+ \e[1m11.163. set/wx (0)\e[0m
- set/wx Allow WX messages to come out on your terminal
+ \e[1mset/wx \e[22mAllow WX messages to come out on your terminal
- 11.164. show/baddx (1)
+ \e[1m11.164. show/baddx (1)\e[0m
- show/baddx Show all the bad dx calls in the system
+ \e[1mshow/baddx \e[22mShow all the bad dx calls in the system
Display all the bad dx callsigns in the system, see SET/BADDXfor more
information.
- 11.165. show/badnode (1)
+ \e[1m11.165. show/badnode (1)\e[0m
- show/badnode Show all the bad nodes in the system
+ \e[1mshow/badnode \e[22mShow all the bad nodes in the system
Display all the bad node callsigns in the system, see SET/BADNODEfor
more information.
- 11.166. show/badspotter (1)
+ \e[1m11.166. show/badspotter (1)\e[0m
- show/badspotter Show all the bad spotters in the system
+ \e[1mshow/badspotter \e[22mShow all the bad spotters in the system
Display all the bad spotter's callsigns in the system, see
SET/BADSPOTTERfor more information.
- 11.167. show/badword (1)
+ \e[1m11.167. show/badword (1)\e[0m
- show/badword Show all the bad words in the system
+ \e[1mshow/badword \e[22mShow all the bad words in the system
Display all the bad words in the system, see SET/BADWORDfor more
information.
- 11.168. show/chat [<group>] [<lines>] (0)
+ \e[1m11.168. show/chat [<group>] [<lines>] (0)\e[0m
- show/chat [<group>] [<lines>] Show any chat or conferencing
+ \e[1mshow/chat [<group>] [<lines>] \e[22mShow 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.
- 11.169. show/configuration [<node>] (0)
+ \e[1m11.169. show/configuration [<node>] (0)\e[0m
- show/configuration [<node>] Show all the nodes and users visible
+ \e[1mshow/configuration [<node>] \e[22mShow 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 is normally abbreviated
- 11.170. show/configuration/node (0)
+ \e[1m11.170. show/configuration/node (0)\e[0m
- show/configuration/node Show all the nodes connected locally
+ \e[1mshow/configuration/node \e[22mShow all the nodes connected locally
Show all the nodes connected to this node.
- 11.171. show/connect (1)
+ \e[1m11.171. show/connect (1)\e[0m
- show/connect Show all the active connections
+ \e[1mshow/connect \e[22mShow all the active connections
This command shows information on all the active connections known
tothe node. This command gives slightly more information than WHO.
- 11.172. show/contest <year and month> (0)
+ \e[1m11.172. show/contest <year and month> (0)\e[0m
- show/contest <year and month> Show all the contests for a month
+ \e[1mshow/contest <year and month> \e[22mShow 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
- 11.173. show/date [<prefix>|<callsign>] (0)
+
\e[1m11.173. show/date [<prefix>|<callsign>] (0)
\e[0m
- show/date [<prefix>|<callsign>] Show the local time
+ \e[1mshow/date [<prefix>|<callsign>] \e[22mShow 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
show UTC and UTC + the local offset (not including DST) atthe prefixes
or callsigns that you specify.
- 11.174. show/db0sdx <callsign> (0)
+ \e[1m11.174. show/db0sdx <callsign> (0)\e[0m
- show/db0sdx <callsign> Show QSL infomation from DB0SDX database
+ \e[1mshow/db0sdx <callsign> \e[22mShow 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.
- 11.175. show/debug (9)
+ \e[1m11.175. show/debug (9)\e[0m
- show/debug Show what levels of debug information you are logging
+ \e[1mshow/debug \e[22mShow what levels of debug information you are logging
- 11.176. show/dx (0)
+ \e[1m11.176. show/dx (0)\e[0m
- show/dx Interrogate the spot database
+ \e[1mshow/dx \e[22mInterrogate 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
- 11.177. show/dxcc <prefix> (0)
+
\e[1m11.177. show/dxcc <prefix> (0)
\e[0m
- show/dxcc <prefix> Interrogate the spot database by country
+ \e[1mshow/dxcc <prefix> \e[22mInterrogate 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 isand
- 11.178. show/dxqsl <callsign> (0)
+ \e[1m11.178. show/dxqsl <callsign> (0)\e[0m
- show/dxqsl <callsign> Show any QSL info gathered from spots
+ \e[1mshow/dxqsl <callsign> \e[22mShow 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
This gives you more background information.
- 11.179. show/dxstats [days] [date] (0)
+ \e[1m11.179. show/dxstats [days] [date] (0)\e[0m
- show/dxstats [days] [date] Show the DX Statistics
+ \e[1mshow/dxstats [days] [date] \e[22mShow the DX Statistics
Show the total DX spots for the last <days> no of days (default is
31), starting from a <date> (default: today).
- 11.180. show/files [<filearea> [<string>]] (0)
+ \e[1m11.180. show/files [<filearea> [<string>]] (0)\e[0m
- show/files [<filearea> [<string>]] List the contents of a filearea
+ \e[1mshow/files [<filearea> [<string>]] \e[22mList the contents of a filearea
SHOW/FILES on its own will show you a list of the various
fileareasavailable on the system. To see the contents of a particular
See also TYPE - to see the contents of a file.
- 11.181. show/filter (0)
+ \e[1m11.181. show/filter (0)\e[0m
- show/filter Show the contents of all the filters you have set
+ \e[1mshow/filter \e[22mShow 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.
- 11.182. show/hfstats [days] [date] (0)
+ \e[1m11.182. show/hfstats [days] [date] (0)\e[0m
- show/hfstats [days] [date] Show the HF DX Statistics
+ \e[1mshow/hfstats [days] [date] \e[22mShow 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).
- 11.183. show/hftable [days] [date] [prefix ...] (0)
+ \e[1m11.183. show/hftable [days] [date] [prefix ...] (0)\e[0m
- show/hftable [days] [date] [prefix ...] Show the HF DX Spotter Table
+ \e[1mshow/hftable [days] [date] [prefix ...] \e[22mShow the HF DX Spotter Table
Show the HF DX Spotter table for the list of prefixes for the last
<days> no of days (default is 31), starting from a <date> (default:
- 11.184. show/hops <call> [ann|spots|route|wcy|wwv] (8)
+ \e[1m11.184. show/hops <call> [ann|spots|route|wcy|wwv] (8)\e[0m
- show/hops <call> [ann|spots|route|wcy|wwv] Show the hop counts for a
+ \e[1mshow/hops <call> [ann|spots|route|wcy|wwv] \e[22mShow the hop counts for a
node
This command shows the hop counts set up for a node. You can
- 11.185. show/isolate (1)
+ \e[1m11.185. show/isolate (1)\e[0m
- show/isolate Show list of ISOLATED nodes
+ \e[1mshow/isolate \e[22mShow list of ISOLATED nodes
- 11.186. show/lockout <prefix>|all (9)
+
\e[1m11.186. show/lockout <prefix>|all (9)
\e[0m
- show/lockout <prefix>|all Show the list of locked out or excluded
+ \e[1mshow/lockout <prefix>|all \e[22mShow the list of locked out or excluded
callsigns
- 11.187. show/log [<callsign>] (8)
+ \e[1m11.187. show/log [<callsign>] (8)\e[0m
- show/log [<callsign>] Show excerpts from the system log
+ \e[1mshow/log [<callsign>] \e[22mShow 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.
- 11.188. show/moon [ndays] [<prefix>|<callsign>] (0)
+
\e[1m11.188. show/moon [ndays] [<prefix>|<callsign>] (0)
\e[0m
- show/moon [ndays] [<prefix>|<callsign>] Show Moon rise and set times
+ \e[1mshow/moon [ndays] [<prefix>|<callsign>] \e[22mShow 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
note that the rise and set times are given as the UT times of rise and
set on the requested UT day.
- 11.189. show/muf <prefix> [<hours>][long] (0)
+
\e[1m11.189. show/muf <prefix> [<hours>][long] (0)
\e[0m
- show/muf <prefix> [<hours>][long] Show the likely propagation to a
+ \e[1mshow/muf <prefix> [<hours>][long] \e[22mShow the likely propagation to a
prefix
This command allow you to estimate the likelihood of you contactinga
Itshould be noted that the figures will probably not be very useful,
norterrible accurate, but it is included for completeness.
- 11.190. show/newconfiguration [<node>] (0)
+ \e[1m11.190. show/newconfiguration [<node>] (0)\e[0m
- show/newconfiguration [<node>] Show all the nodes and users visible
+ \e[1mshow/newconfiguration [<node>] \e[22mShow 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 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
- 11.191. show/newconfiguration/node (0)
+ \e[1m11.191. show/newconfiguration/node (0)\e[0m
- show/newconfiguration/node Show all the nodes connected locally
+ \e[1mshow/newconfiguration/node \e[22mShow all the nodes connected locally
Show all the nodes connected to this node in the new format.
- 11.192. show/node [<callsign> ...] (1)
+ \e[1m11.192. show/node [<callsign> ...] (1)\e[0m
- show/node [<callsign> ...] Show the type and version number of nodes
+ \e[1mshow/node [<callsign> ...] \e[22mShow 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.
- 11.193. show/prefix <callsign> (0)
+ \e[1m11.193. show/prefix <callsign> (0)\e[0m
- show/prefix <callsign> Interrogate the prefix database
+ \e[1mshow/prefix <callsign> \e[22mInterrogate 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
with the internal country no, the CQ and ITU regions. See also
SHOW/DXCC
- 11.194. show/program (5)
+ \e[1m11.194. show/program (5)\e[0m
- show/program Show the locations of all the included program modules
+ \e[1mshow/program \e[22mShow 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.
- 11.195. show/qra <lat> <long> (0)
+ \e[1m11.195. show/qra <lat> <long> (0)\e[0m
- show/qra <lat> <long> Convert lat/long to a QRA Grid locator
+ \e[1mshow/qra <lat> <long> \e[22mConvert lat/long to a QRA Grid locator
This is a multipurpose command that allows you either to calculate
thedistance and bearing between two locators or (if only one locator
- 11.196. show/qra <locator> [<locator>] (0)
+ \e[1m11.196. show/qra <locator> [<locator>] (0)\e[0m
- show/qra <locator> [<locator>] Show distance between QRA Grid locators
+ \e[1mshow/qra <locator> [<locator>] \e[22mShow distance between QRA Grid locators
- 11.197. show/qrz <callsign> (0)
+ \e[1m11.197. show/qrz <callsign> (0)\e[0m
- show/qrz <callsign> Show any callbook details on a callsign
+ \e[1mshow/qrz <callsign> \e[22mShow 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.
- 11.198. show/registered [<prefix>] (9)
+
\e[1m11.198. show/registered [<prefix>] (9)
\e[0m
- show/registered [<prefix>] Show the registered users
+ \e[1mshow/registered [<prefix>] \e[22mShow the registered users
- 11.199. show/route <callsign> ... (0)
+ \e[1m11.199. show/route <callsign> ... (0)\e[0m
- show/route <callsign> ... Show the route to the callsign
+ \e[1mshow/route <callsign> ... \e[22mShow the route to the callsign
This command allows you to see to which node the callsigns specified
areconnected. It is a sort of inverse sh/config.
- 11.200. show/satellite <name> [<hours> <interval>] (0)
+ \e[1m11.200. show/satellite <name> [<hours> <interval>] (0)\e[0m
- show/satellite <name> [<hours> <interval>] Show tracking data
+ \e[1mshow/satellite <name> [<hours> <interval>] \e[22mShow tracking data
Show the tracking data from your location to the satellite of your
choicefrom now on for the next few hours.If you use this command
- 11.201. show/station all [<regex>] (6)
+ \e[1m11.201. show/station all [<regex>] (6)\e[0m
- show/station all [<regex>] Show list of users in the system
+ \e[1mshow/station all [<regex>] \e[22mShow list of users in the system
- 11.202. show/station [<callsign> ..] (0)
+ \e[1m11.202. show/station [<callsign> ..] (0)\e[0m
- show/station [<callsign> ..] Show information about a callsign
+ \e[1mshow/station [<callsign> ..] \e[22mShow information about a callsign
Show the information known about a callsign and whether (and
where)that callsign is connected to the cluster.
If no callsign is given then show the information for yourself.
- 11.203. show/sun [ndays] [<prefix>|<callsign>] (0)
+
\e[1m11.203. show/sun [ndays] [<prefix>|<callsign>] (0)
\e[0m
- show/sun [ndays] [<prefix>|<callsign>] Show sun rise and set times
+ \e[1mshow/sun [ndays] [<prefix>|<callsign>] \e[22mShow 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
note that the rise and set times are given as the UT times of rise and
set on the requested UT day.
- 11.204. show/time [<prefix>|<callsign>] (0)
+
\e[1m11.204. show/time [<prefix>|<callsign>] (0)
\e[0m
- show/time [<prefix>|<callsign>] Show the local time
+ \e[1mshow/time [<prefix>|<callsign>] \e[22mShow 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.
- 11.205. show/usdb [call ..] (0)
+ \e[1m11.205. show/usdb [call ..] (0)\e[0m
- show/usdb [call ..] Show information held on the FCC Call database
+ \e[1mshow/usdb [call ..] \e[22mShow information held on the FCC Call database
Show the City and State of a Callsign held on the FCC database ifhis
is being run on this system, eg:-
- 11.206. show/vhfstats [days] [date] (0)
+ \e[1m11.206. show/vhfstats [days] [date] (0)\e[0m
- show/vhfstats [days] [date] Show the VHF DX Statistics
+ \e[1mshow/vhfstats [days] [date] \e[22mShow 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).
- 11.207. show/vhftable [days] [date] [prefix ...] (0)
+ \e[1m11.207. show/vhftable [days] [date] [prefix ...] (0)\e[0m
- show/vhftable [days] [date] [prefix ...] Show the VHF DX Spotter Table
+ \e[1mshow/vhftable [days] [date] [prefix ...] \e[22mShow the VHF DX Spotter Table
Show the VHF DX Spotter table for the list of prefixes for the last
<days> no of days (default is 31), starting from a date (default:
- 11.208. show/wcy (0)
+ \e[1m11.208. show/wcy (0)\e[0m
- show/wcy Show last 10 WCY broadcasts
+ \e[1mshow/wcy \e[22mShow last 10 WCY broadcasts
- 11.209. show/wcy <n> (0)
+ \e[1m11.209. show/wcy <n> (0)\e[0m
- show/wcy <n> Show last <n> WCY broadcasts
+ \e[1mshow/wcy <n> \e[22mShow last <n> WCY broadcasts
Display the most recent WCY information that has been received by the
system
- 11.210. show/wm7d <callsign> (0)
+ \e[1m11.210. show/wm7d <callsign> (0)\e[0m
- show/wm7d <callsign> Show callbook details on a US callsigns
+ \e[1mshow/wm7d <callsign> \e[22mShow 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.
- 11.211. show/wwv (0)
+ \e[1m11.211. show/wwv (0)\e[0m
- show/wwv Show last 10 WWV broadcasts
+ \e[1mshow/wwv \e[22mShow last 10 WWV broadcasts
- 11.212. show/wwv <n> (0)
+ \e[1m11.212. show/wwv <n> (0)\e[0m
- show/wwv <n> Show last <n> WWV broadcasts
+ \e[1mshow/wwv <n> \e[22mShow last <n> WWV broadcasts
Display the most recent WWV information that has been received by the
system
- 11.213. shutdown (5)
+ \e[1m11.213. shutdown (5)\e[0m
- shutdown Shutdown the cluster
+ \e[1mshutdown \e[22mShutdown the cluster
Shutdown the cluster and disconnect all the users
- 11.214. spoof <call> <command> (9)
+ \e[1m11.214. spoof <call> <command> (9)\e[0m
- spoof <call> <command> Do a command as though you are another user
+ \e[1mspoof <call> <command> \e[22mDo 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
- 11.215. stat/channel [<callsign>] (5)
+ \e[1m11.215. stat/channel [<callsign>] (5)\e[0m
- stat/channel [<callsign>] Show the status of a channel on the cluster
+ \e[1mstat/channel [<callsign>] \e[22mShow 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.
- 11.216. stat/db <dbname> (5)
+ \e[1m11.216. stat/db <dbname> (5)\e[0m
- stat/db <dbname> Show the status of a database
+ \e[1mstat/db <dbname> \e[22mShow 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.
- 11.217. stat/msg (1)
+ \e[1m11.217. stat/msg (1)\e[0m
- stat/msg Show the status of the message system
+ \e[1mstat/msg \e[22mShow the status of the message system
- 11.218. stat/msg <msgno> (1)
+ \e[1m11.218. stat/msg <msgno> (1)\e[0m
- stat/msg <msgno> Show the status of a message
+ \e[1mstat/msg <msgno> \e[22mShow 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
- 11.219. stat/route_node <callsign> (5)
+ \e[1m11.219. stat/route_node <callsign> (5)\e[0m
- stat/route_node <callsign> Show the data in a Route::Node object
+ \e[1mstat/route_node <callsign> \e[22mShow the data in a Route::Node object
- 11.220. stat/route_node all (5)
+ \e[1m11.220. stat/route_node all (5)\e[0m
- stat/route_node all Show list of all Route::Node objects
+ \e[1mstat/route_node all \e[22mShow list of all Route::Node objects
- 11.221. stat/route_user <callsign> (5)
+ \e[1m11.221. stat/route_user <callsign> (5)\e[0m
- stat/route_user <callsign> Show the data in a Route::User object
+ \e[1mstat/route_user <callsign> \e[22mShow the data in a Route::User object
- 11.222. stat/route_user all (5)
+ \e[1m11.222. stat/route_user all (5)\e[0m
- stat/route_user all Show list of all Route::User objects
+ \e[1mstat/route_user all \e[22mShow list of all Route::User objects
- 11.223. stat/user [<callsign>] (5)
+ \e[1m11.223. stat/user [<callsign>] (5)\e[0m
- stat/user [<callsign>] Show the full status of a user
+ \e[1mstat/user [<callsign>] \e[22mShow 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.
- 11.224. sysop (0)
+ \e[1m11.224. sysop (0)\e[0m
- sysop Regain your privileges if you login remotely
+ \e[1msysop \e[22mRegain your privileges if you login remotely
The system automatically reduces your privilege level to that of
anormal user if you login in remotely. This command allows you
offerednumbers but nothing will happen when you input a string. Any
match iscase sensitive.
- 11.225. talk <call> > <node> [<text>] (0)
+ \e[1m11.225. talk <call> > <node> [<text>] (0)\e[0m
- talk <call> > <node> [<text>] Send a text message to another station
+ \e[1mtalk <call> > <node> [<text>] \e[22mSend a text message to another station
via a node
Send a short message to any other station that is visible on the
will send the hftable as you have it to all the people you are cur-
rently talking to.
- 11.226. talk <call> [<text>] (0)
+ \e[1m11.226. talk <call> [<text>] (0)\e[0m
- talk <call> [<text>] Send a text message to another station
+ \e[1mtalk <call> [<text>] \e[22mSend a text message to another station
- 11.227. type <filearea>/<name> (0)
+ \e[1m11.227. type <filearea>/<name> (0)\e[0m
- type <filearea>/<name> Look at the contents of a file in one of the
+ \e[1mtype <filearea>/<name> \e[22mLook at the contents of a file in one of the
fileareas
Type out the contents of a file in a filearea. So, for example, in
See also SHOW/FILES to see what fileareas are available and a list of
content.
- 11.228. uncatchup <node call> all|[msgno> ...] (5)
+ \e[1m11.228. uncatchup <node call> all|[msgno> ...] (5)\e[0m
- uncatchup <node call> all|[msgno> ...] Unmark a message as sent
+ \e[1muncatchup <node call> all|[msgno> ...] \e[22mUnmark a message as sent
When you send messages the fact that you have forwarded it to another
which will arrange for them to be forward candidates again.Order is
not important.
- 11.229. unset/announce (0)
+ \e[1m11.229. unset/announce (0)\e[0m
- unset/announce Stop announce messages coming out on your terminal
+ \e[1munset/announce \e[22mStop announce messages coming out on your terminal
- 11.230. unset/anntalk (0)
+ \e[1m11.230. unset/anntalk (0)\e[0m
- unset/anntalk Stop talk like announce messages on your terminal
+ \e[1munset/anntalk \e[22mStop talk like announce messages on your terminal
The announce system on legacy cluster nodes is used as a talk
substitute because the network is so poorly connected. If you:
allows you to see them again. This is the default.
- 11.231. unset/baddx <call>.. (8)
+ \e[1m11.231. unset/baddx <call>.. (8)\e[0m
- unset/baddx <call>.. Propagate a dx spot with this callsign again
+ \e[1munset/baddx <call>.. \e[22mPropagate a dx spot with this callsign again
Setting a word as 'baddx' will prevent spots with that word in
the'spotted' field (as in: DX 14001.1 FR0G)of a DX spot from going
- 11.232. unset/badnode <call>.. (8)
+ \e[1m11.232. unset/badnode <call>.. (8)\e[0m
- unset/badnode <call>.. Allow spots from this node again
+ \e[1munset/badnode <call>.. \e[22mAllow spots from this node again
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
will allow spots from him again.Use with extreme care. This command
may well be superceeded by FILTERing.
- 11.233. unset/badspotter <call>.. (8)
+ \e[1m11.233. unset/badspotter <call>.. (8)\e[0m
- unset/badspotter <call>.. Allow spots from this callsign again
+ \e[1munset/badspotter <call>.. \e[22mAllow spots from this callsign again
Setting a callsign as a 'badspotter' will prevent spots from this
callsign going any further. They will not be displayed and they will
will allow spots from him again.Use with extreme care. This command
may well be superceded by FILTERing.
- 11.234. unset/badword <word>.. (8)
+ \e[1m11.234. unset/badword <word>.. (8)\e[0m
- unset/badword <word>.. Propagate things with this word again
+ \e[1munset/badword <word>.. \e[22mPropagate things with this word again
Setting a word as a 'badword' will prevent things like spots,announces
or talks with this word in the the text part from going anyfurther.
will allow text with this word again.
- 11.235. unset/beep (0)
+ \e[1m11.235. unset/beep (0)\e[0m
- unset/beep Stop beeps for DX and other messages on your terminal
+ \e[1munset/beep \e[22mStop beeps for DX and other messages on your terminal
- 11.236. unset/debug <name> (9)
+ \e[1m11.236. unset/debug <name> (9)\e[0m
- unset/debug <name> Remove a debug level from the debug set
+ \e[1munset/debug <name> \e[22mRemove a debug level from the debug set
You can choose to log several different levels. The levels are
You can show what levels you are logging with SHOW/DEBUG
- 11.237. unset/dx (0)
+ \e[1m11.237. unset/dx (0)\e[0m
- unset/dx Stop DX messages coming out on your terminal
+ \e[1munset/dx \e[22mStop DX messages coming out on your terminal
- 11.238. unset/dxcq (0)
+ \e[1m11.238. unset/dxcq (0)\e[0m
- unset/dxcq Stop CQ Zones on the end of DX announcements
+ \e[1munset/dxcq \e[22mStop 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
SHOW/USSTATEDo a STAT/USER to see which flags you have set if you are
confused.
- 11.239. unset/dxgrid (0)
+ \e[1m11.239. unset/dxgrid (0)\e[0m
- unset/dxgrid Stop QRA Grid Squares on the end of DX announcements
+ \e[1munset/dxgrid \e[22mStop 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
feature.Conflicts with: SET/DXCQ, SET/DXITUDo a STAT/USER to see which
flags you have set if you are confused.
- 11.240. unset/dxitu (0)
+ \e[1m11.240. unset/dxitu (0)\e[0m
- unset/dxitu Stop ITU Zones on the end of DX announcements
+ \e[1munset/dxitu \e[22mStop 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
SHOW/USSTATEDo a STAT/USER to see which flags you have set if you are
confused.
- 11.241. unset/echo (0)
+ \e[1m11.241. unset/echo (0)\e[0m
- unset/echo Stop the cluster echoing your input
+ \e[1munset/echo \e[22mStop 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
setting appropriately. The setting is stored in your user profile.YOU
DO NOT NEED TO USE THIS COMMAND IF YOU ARE CONNECTED VIA AX25.
- 11.242. unset/email (0)
+ \e[1m11.242. unset/email (0)\e[0m
- unset/email Stop personal msgs being forwarded by email
+ \e[1munset/email \e[22mStop personal msgs being forwarded by email
If any personal messages come in for your callsign then you can
usethese commands to control whether they are forwarded onto your
- 11.243. unset/here (0)
+ \e[1m11.243. unset/here (0)\e[0m
- unset/here Tell the system you are absent from your terminal
+ \e[1munset/here \e[22mTell the system you are absent from your terminal
- 11.244. unset/hops <call> ann|spots|route|wwv|wcy (8)
+ \e[1m11.244. unset/hops <call> ann|spots|route|wwv|wcy (8)\e[0m
- unset/hops <call> ann|spots|route|wwv|wcy Unset hop count
+ \e[1munset/hops <call> ann|spots|route|wwv|wcy \e[22mUnset 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
- 11.245. unset/isolate (9)
+ \e[1m11.245. unset/isolate (9)\e[0m
- unset/isolate Stop Isolation of a node from the rest of the network
+ \e[1munset/isolate \e[22mStop Isolation of a node from the rest of the network
Remove isolation from a node - SET/ISOLATE
- 11.246. unset/lockout <call> (9)
+ \e[1m11.246. unset/lockout <call> (9)\e[0m
- unset/lockout <call> Allow a callsign to connect to the cluster
+ \e[1munset/lockout <call> \e[22mAllow a callsign to connect to the cluster
- 11.247. unset/logininfo (0)
+ \e[1m11.247. unset/logininfo (0)\e[0m
- unset/logininfo Inform when a station logs out locally
+ \e[1munset/logininfo \e[22mInform when a station logs out locally
- 11.248. unset/password <call> ... (9)
+ \e[1m11.248. unset/password <call> ... (9)\e[0m
- unset/password <call> ... Delete (remove) a user's password
+ \e[1munset/password <call> ... \e[22mDelete (remove) a user's password
This command allows the sysop to completely delete and remove a
password for a user.
- 11.249. unset/privilege (0)
+ \e[1m11.249. unset/privilege (0)\e[0m
- unset/privilege Remove any privilege for this session
+ \e[1munset/privilege \e[22mRemove 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.
- 11.250. unset/prompt (0)
+ \e[1m11.250. unset/prompt (0)\e[0m
- unset/prompt Set your prompt back to default
+ \e[1munset/prompt \e[22mSet your prompt back to default
This command will set your user prompt to exactly the string that you
say. The point of this command to enable a user to interface to
UNSET/PROMPT will undo the SET/PROMPT command and set you prompt back
tonormal.
- 11.251. unset/register <call> ... (9)
+ \e[1m11.251. unset/register <call> ... (9)\e[0m
- unset/register <call> ... Mark a user as not registered
+ \e[1munset/register <call> ... \e[22mMark a user as not registered
Registration is a concept that you can switch on by executing the
exception to this is that a non-registered user can TALK orSEND
messages to the sysop.
- 11.252. unset/talk (0)
+ \e[1m11.252. unset/talk (0)\e[0m
- unset/talk Stop TALK messages coming out on your terminal
+ \e[1munset/talk \e[22mStop TALK messages coming out on your terminal
- 11.253. unset/usstate (0)
+ \e[1m11.253. unset/usstate (0)\e[0m
- unset/usstate Stop US State info on the end of DX announcements
+ \e[1munset/usstate \e[22mStop 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
SET/DXITUDo a STAT/USER to see which flags you have set if you are
confused.
- 11.254. unset/wcy (0)
+ \e[1m11.254. unset/wcy (0)\e[0m
- unset/wcy Stop WCY messages coming out on your terminal
+ \e[1munset/wcy \e[22mStop WCY messages coming out on your terminal
- 11.255. unset/wwv (0)
+ \e[1m11.255. unset/wwv (0)\e[0m
- unset/wwv Stop WWV messages coming out on your terminal
+ \e[1munset/wwv \e[22mStop WWV messages coming out on your terminal
- 11.256. unset/wx (0)
+ \e[1m11.256. unset/wx (0)\e[0m
- unset/wx Stop WX messages coming out on your terminal
+ \e[1munset/wx \e[22mStop WX messages coming out on your terminal
- 11.257. who (0)
+ \e[1m11.257. who (0)\e[0m
- who Show who is physically connected
+ \e[1mwho \e[22mShow who is physically connected
This is a quick listing that shows which callsigns are connected
andwhat sort of connection they have
- 11.258. wx <text> (0)
+ \e[1m11.258. wx <text> (0)\e[0m
- wx <text> Send a weather message to local users
+ \e[1mwx <text> \e[22mSend a weather message to local users
- 11.259. wx full <text> (0)
+ \e[1m11.259. wx full <text> (0)\e[0m
- wx full <text> Send a weather message to all cluster users
+ \e[1mwx full <text> \e[22mSend a weather message to all cluster users
- 11.260. wx sysop <text> (5)
+ \e[1m11.260. wx sysop <text> (5)\e[0m
- wx sysop <text> Send a weather message to other clusters only
+ \e[1mwx sysop <text> \e[22mSend a weather message to other clusters only
Weather messages can sometimes be useful if you are experiencing an
extremethat may indicate enhanced conditions
______________________________________________________________________
- 1. Introduction
+ \e[1m1. Introduction\e[0m
- 1.1. What is a DX Cluster?
+ \e[1m1.1. What is a DX Cluster?\e[0m
A DX Cluster is a packet node where DX chasers on any band or mode can
post rare or interesting stations that they have worked or heard. Of
Of course, the DX is still posted to you all the while!
- 1.2. So what is DXSpider?
+ \e[1m1.2. So what is DXSpider?\e[0m
PacketCluster nodes have been around since roughly 1985. The original
PacketCluster idea came from Dick Newell, AK1A, and ran under DOS. In
- 2. Logins and logouts.
+ \e[1m2. Logins and logouts.\e[0m
You might not think that there is a lot of point of including a
section on how to log in and out of DXSpider. However, you would be
variations but here are the basic ones.
- 2.1. AX25 logins.
+ \e[1m2.1. AX25 logins.\e[0m
- Simplicity itself. The usual CONNECT command will log you straight
+ Simplicity itself. The usual \e[1mCONNECT \e[22mcommand will log you straight
into the cluster and you will not have to do anything else.
Obviously, you will have to connect to the correct callsign. Some
nodes use an SSID with their call so you would have to add that.
- Examples:
+ \e[1mExamples:\e[0m
- 2.2. Netrom logins.
+ \e[1m2.2. Netrom logins.\e[0m
There are several possibilities here, dependant on how the sysop has
configured his system. If you are connecting via netrom then you are
most probably connecting from another station. Listing the nodes in
- that station with the NODES command will tell you what callsign or
+ that station with the \e[1mNODES \e[22mcommand will tell you what callsign or
netrom alias to connect to. Then just issue the connect command from
there. It is possible that the netrom alias may connect you to a node
with an alias for the cluster, such as DXC. Just type this and you
will be connected.
- Example:
+ \e[1mExample:\e[0m
connect MBCDX
- 2.3. Telnet logins.
+ \e[1m2.3. Telnet logins.\e[0m
With telnet connections, the source callsign is not seen by DXSpider,
so you will be asked to login with your callsign. To telnet to
at the moment for a cluster telnet port but ask the sysop if you are
unsure.
- Example:
+ \e[1mExample:\e[0m
you. However I am sure you get the idea.
- 2.4. Logouts.
+ \e[1m2.4. Logouts.\e[0m
- Logging out can be done by simply issuing the standard BYE command.
+ Logging out can be done by simply issuing the standard \e[1mBYE \e[22mcommand.
- You could also send a disconnect if you are using AX25, or a CLOSE
+ You could also send a disconnect if you are using AX25, or a \e[1mCLOSE\e[0m
command if you are connected via telnet. If you do not log out
gracefully using one of the above commands, you may find you are
unable to get a full connect next time. This may also happen if a
the TNC or by altering your program configuration.
- 3. Setting your personal details.
+ \e[1m3. Setting your personal details.\e[0m
Once logged in to the cluster, you should set your details so that
anybody who wishes to contact you can find out who and where you are.
latitude/longitude or as a locator. Setting your home node will tell
the program where you wish mail to be sent to you.
- Examples:
+ \e[1mExamples:\e[0m
- 4. Getting and posting DX.
+ \e[1m4. Getting and posting DX.\e[0m
When all is said and done, this is the main function of a DX cluster.
In its simplest form you can just connect to the node and you will
people did not post DX and you get the added thrill of the hunt!
- 4.1. Receiving DX.
+ \e[1m4.1. Receiving DX.\e[0m
As we have already said, it is possible just to connect to the cluster
and you will receive spots automatically. However, you may wish to
check on spots just posted. Maybe you wish to see if a particular
band is open or if a certain callsign is active, perhaps a DXpedition.
- The command to do this is SHOW/DX. Without any other arguments, this
+ The command to do this is \e[1mSHOW/DX\e[22m. Without any other arguments, this
command will output the last 10 spots posted. It is possible to look
at more than this, for example the last 20 or 50 spots, by adding the
number to the command. You can make it even more specific by adding a
band in either wavelength or frequency, and/or any additional
information such as QSL details.
- Examples:
+ \e[1mExamples:\e[0m
will show the last 10, 5 and 20 spots received by the cluster
respectively.
- Examples
+ \e[1mExamples\e[0m
It is also possible to check for certain callsigns, or fragments of
callsigns in the same way.
- Examples:
+ \e[1mExamples:\e[0m
You can check for DX by offset and also by specifying a comment to
search for.
- Examples:
+ \e[1mExamples:\e[0m
would show the spots that arrived between 30 and 40 spots ago and any
- spots with the word iota in the comment field. The case of the
+ spots with the word \e[4miota\e[24m in the comment field. The case of the
comment is not important.
Checking DX posted on a certain day is possible too. All you have to
do here is to specify how many days ago it was like this ...
- Example:
+ \e[1mExample:\e[0m
It is of course possible to specify multiple arguments.
- Example:
+ \e[1mExample:\e[0m
show/dx 20 prefix 9a on vhf day 30
This would show the last 20 spots posted by or about calls with the
prefix 9a on vhf 30 days ago.
- As you can see the SHOW/DX command is very flexible, so if you are not
+ As you can see the \e[1mSHOW/DX \e[22mcommand is very flexible, so if you are not
sure whether something will work or not, try it and see! More
information can be found in the Command Set section.
- 4.2. Posting DX.
+ \e[1m4.2. Posting DX.\e[0m
- To post DX you use the DX command. The syntax is shown below.
+ To post DX you use the \e[1mDX \e[22mcommand. The syntax is shown below.
- Example:
+ \e[1mExample:\e[0m
name or perhaps a location. Actually DXSpider will allow the
frequency and callsign fields to be entered in any order.
- Example:
+ \e[1mExample:\e[0m
to you as proof of receipt.
- 5. Headings and propagation
+ \e[1m5. Headings and propagation\e[0m
There are three commands in DXSpider to help you get the best DX
- possible. These are SHOW/SUN, SHOW/MOON and SHOW/HEADING. These
+ possible. These are \e[1mSHOW/SUN\e[22m, \e[1mSHOW/MOON \e[22mand \e[1mSHOW/HEADING\e[22m. These
commands will only work for you if you have entered your personal
details. They use your entered location as a reference, so if you
have not entered it or have entered it incorrectly they will not
return the correct information.
- 5.1. Sun
+ \e[1m5.1. Sun\e[0m
- The SHOW/SUN command can be used in three different ways. It can be
+ The \e[1mSHOW/SUN \e[22mcommand can be used in three different ways. It can be
used to show sunrise and sunset times for your own station, a
particular callsign or a prefix.
- Example:
+ \e[1mExample:\e[0m
ZS So-Africa-ZS6-ZS 03:59Z 16:42Z 277.6 35.0
- 5.2. Moon
+ \e[1m5.2. Moon\e[0m
- The SHOW/MOON command works in the same way as the SHOW/SUN command.
+ The \e[1mSHOW/MOON \e[22mcommand works in the same way as the \e[1mSHOW/SUN \e[22mcommand.
This program however, calculates the rise and set times of the moon
for a prefix or callsign, together with the current azimuth and
elevation of the sun at these locations.
- Example:
+ \e[1mExample:\e[0m
- You can see that the output is similar to the SHOW/SUN command, with
+ You can see that the output is similar to the \e[1mSHOW/SUN \e[22mcommand, with
slightly different fields.
- 5.3. Heading
+ \e[1m5.3. Heading\e[0m
- The SHOW/HEADING command works in the same way as the SHOW/SUN and
- SHOW/MOON commands but outputs beam headings for a specified callsign
+ The \e[1mSHOW/HEADING \e[22mcommand works in the same way as the \e[1mSHOW/SUN \e[22mand
+ \e[1mSHOW/MOON \e[22mcommands but outputs beam headings for a specified callsign
or prefix. Reciprocal beam headings are also calculated.
- Example
+ \e[1mExample\e[0m
- 6. Announcements.
+ \e[1m6. Announcements.\e[0m
- 6.1. Making announcements.
+ \e[1m6.1. Making announcements.\e[0m
Occasionally, you may wish to post something that does not fall into
the normal parameters for a DX callout. You may wish to tell
everybody connected that 10 FM is open for example, or ask if anyone
knows the QSL manager for a certain callsign etc. You can do this
- using the ANNOUNCE command.
+ using the \e[1mANNOUNCE \e[22mcommand.
- Example:
+ \e[1mExample:\e[0m
That would let everyone know locally that this was the case, however
it would not be forwarded to other nodes connected. To send
- announcements to other connected nodes as well, you would use the FULL
+ announcements to other connected nodes as well, you would use the \e[1mFULL\e[0m
extension.
- Example:
+ \e[1mExample:\e[0m
across the network.
- 6.2. Listing announcements.
+ \e[1m6.2. Listing announcements.\e[0m
You can list previous announcements in the standard format with the
- SHOW command. As before you can list just the last 5 or as many as
+ \e[1mSHOW \e[22mcommand. As before you can list just the last 5 or as many as
you wish.
- Example:
+ \e[1mExample:\e[0m
- 7. Nodes and users.
+ \e[1m7. Nodes and users.\e[0m
You can check which nodes are connected in the network, who is logged
on locally, who is logged on at all the nodes or even just one node in
particular. This is handy if you wish to see whether a friend is
connected at the node they use. To see who is connected to the nodes,
- the SHOW/CONFIGURATION command is used.
+ the \e[1mSHOW/CONFIGURATION \e[22mcommand is used.
- Example:
+ \e[1mExample:\e[0m
- To show the locally connected users, the SHOW/USERS command is used
+ To show the locally connected users, the \e[1mSHOW/USERS \e[22mcommand is used
- Example:
+ \e[1mExample:\e[0m
- 8. Talk mode.
+ \e[1m8. Talk mode.\e[0m
You can send a single comment or start a dedicated talk session to
- another user by using the TALK command.
+ another user by using the \e[1mTALK \e[22mcommand.
Talk mode is used to send a one line comment or greeting to a specific
also enter into a dedicated talk session with another user. Talks
will be automatically forwarded to other nodes if the station you are
talking to is not connected locally. You can find out who is
- connected by using the SHOW/CONFIGURATION command, (described
+ connected by using the \e[1mSHOW/CONFIGURATION \e[22mcommand, (described
earlier).
- Examples:
+ \e[1mExamples:\e[0m
As you can see, you can still run commands whilst in talk mode.
Simply prefix the command with a / like /sh/dx and you will get the
expected output. If the user is connected to another node, you may
- have to use a slightly extended version of the TALK command.
+ have to use a slightly extended version of the \e[1mTALK \e[22mcommand.
- To exit talk mode, you issue the command /ex.
+ To exit talk mode, you issue the command \e[1m/ex\e[22m.
Whilst in talk mode you will still receive DX spots. This means that
you can chat to a friend whilst working DX.
- 9. Mail.
+ \e[1m9. Mail.\e[0m
You can send and receive both personal mail and bulletins with
DXSpider quite easily.
- 9.1. The "directory" command.
+ \e[1m9.1. The "directory" command.\e[0m
- To list mail you would use the DIRECTORY command. On its own, this
+ To list mail you would use the \e[1mDIRECTORY \e[22mcommand. On its own, this
command will output the last ten messages received by the node, either
to or from yourself or bulletins such as "DX" and "ALL". As with
other commands you can display more by specifying a number with the
command. You should be aware that Spider will accept these commands
- by separating with either a slash or a space, so dir new and dir/new
+ by separating with either a slash or a space, so \e[4mdir\e[24m \e[4mnew\e[24m and \e[4mdir/new\e[0m
work in the same way.
- Example:
+ \e[1mExample:\e[0m
to subjects like "all" or "local" or "dx" etc. You can treat these
bulletins in the same way as personal mail with the directory command.
- Examples:
+ \e[1mExamples:\e[0m
section.
- 9.2. Reading mail.
+ \e[1m9.2. Reading mail.\e[0m
- The output of the DIRECTORY command could be something like this.
+ The output of the \e[1mDIRECTORY \e[22mcommand could be something like this.
Reading a message is as simple as typing read, followed by the message
number that you wish to read.
- Example:
+ \e[1mExample:\e[0m
it's entirety unless you specify a page length. You can set your page
length to any number you like and when the message reaches that number
of lines you will get a prompt giving you options.
- Example:
+ \e[1mExample:\e[0m
- 9.3. Sending mail.
+ \e[1m9.3. Sending mail.\e[0m
Sending mail is done in the time honoured way. First you specify a
recipient for the message, then you will be prompted for a subject.
are using a client that wraps lines automatically, remember to hit
return at the end of each line.
- Example:
+ \e[1mExample:\e[0m
- 9.4. Replying to mail.
+ \e[1m9.4. Replying to mail.\e[0m
If mail is addressed to you or to a bulletin address, you can use the
- REPLY command to reply to it. Using this command, the subject will be
+ \e[1mREPLY \e[22mcommand to reply to it. Using this command, the subject will be
automatically set for you as "Re: subject", whatever the subject was.
- Example:
+ \e[1mExample:\e[0m
- 9.5. Deleting mail
+ \e[1m9.5. Deleting mail\e[0m
- To delete a message, you use the delete command. You can only delete
+ To delete a message, you use the \e[4mdelete\e[24m command. You can only delete
messages sent to or received by yourself. Bulletins are dealt with
automatically or by the sysop.
- 10. Filtering (From version 1.45)
+ \e[1m10. Filtering (From version 1.45)\e[0m
- 10.1. General filter rules
+ \e[1m10.1. General filter rules\e[0m
Upto v1.44 it was not possible for the user to set their own filters.
From v1.45 though that has all changed. It is now possible to set
There are 3 basic commands involved in setting and manipulating
- filters. These are accept, reject and clear. First we will look
+ filters. These are \e[4maccept\e[24m, \e[4mreject\e[24m and \e[4mclear\e[24m. First we will look
generally at filtering. There are a number of things you can filter in
the DXSpider system. They all use the same general mechanism.
- 10.2. Types of filter
+ \e[1m10.2. Types of filter\e[0m
- There are two main types of filter, accept or reject. You can use
+ There are two main types of filter, \e[4maccept\e[24m or \e[4mreject\e[24m. You can use
either to achieve the result you want dependent on your own preference
and which is more simple to do. It is pointless writing 8 lines of
reject filters when 1 accept filter would do the same thing! Each
the filter will be dumped but all else will be accepted. If you use
an accept filter, then ONLY the lines in the filter will be accepted
and all else will be dumped. For example if you have a single line
- accept filter ...
+ \e[4maccept\e[24m filter ...
- then you will ONLY get VHF spots from or to CQ zones 14, 15 and 16.
+ then you will \e[4mONLY\e[24m get VHF spots \e[4mfrom\e[24m or \e[4mto\e[24m CQ zones 14, 15 and 16.
If you set a reject filter like this ...
- Then you will get everything EXCEPT HF CW spots. You could make this
+ Then you will get everything \e[4mEXCEPT\e[24m HF CW spots. You could make this
single filter even more flexible. For example, if you are interested
in IOTA and will work it even on CW even though normally you are not
interested in CW, then you could say ...
You will notice in the above example that the second line has
brackets. Look at the line logically. You can see there are 2
separate sections to it. We are saying reject spots that are VHF or
- above APART from those in zones 14, 15 and 16 (either spotted there or
+ above \e[4mAPART\e[24m from those in zones 14, 15 and 16 (either spotted there or
originated there). If you did not have the brackets to separate the 2
sections, then Spider would read it logically from the front and see a
different expression entirely ...
- 10.3. Filter options
+ \e[1m10.3. Filter options\e[0m
You can filter in several different ways. The options are listed in
the various helpfiles for accept, reject and filter.
- 10.4. Advanced filtering
+ \e[1m10.4. Advanced filtering\e[0m
Once you are happy with the results you get, you may like to
experiment.
Note that the first filter has not been specified with a number. This
will automatically be assumed to be number 1. In this case, we have
- said reject all HF spots in the CW section of the bands but accept all
- others at HF. Also accept anything in VHF and above spotted in or by
- operators in the zones 14, 15 and 16. Each filter slot actually has a
+ said \e[4mreject\e[24m \e[4mall\e[24m \e[4mHF\e[24m \e[4mspots\e[24m \e[4min\e[24m \e[4mthe\e[24m \e[4mCW\e[24m \e[4msection\e[24m \e[4mof\e[24m \e[4mthe\e[24m \e[4mbands\e[24m \e[4mbut\e[24m \e[4maccept\e[24m \e[4mall\e[0m
+ \e[4mothers\e[24m \e[4mat\e[24m \e[4mHF.\e[24m \e[4mAlso\e[24m \e[4maccept\e[24m \e[4manything\e[24m \e[4min\e[24m \e[4mVHF\e[24m \e[4mand\e[24m \e[4mabove\e[24m \e[4mspotted\e[24m \e[4min\e[24m \e[4mor\e[24m \e[4mby\e[0m
+ \e[4moperators\e[24m \e[4min\e[24m \e[4mthe\e[24m \e[4mzones\e[24m \e[4m14,\e[24m \e[4m15\e[24m \e[4mand\e[24m \e[4m16\e[24m. Each filter slot actually has a
'reject' slot and an 'accept' slot. The reject slot is executed BEFORE
the accept slot.
VHF/UHF spots from EU.
- 10.5. A Filtering Tutorial
+ \e[1m10.5. A Filtering Tutorial\e[0m
There is now an excellent primer/tutorial on filtering written by Jim
Samuels, W3BG with an introduction by Dave Hawes N3RD that I strongly
Primer
- 11. Hints, tips and common questions.
+ \e[1m11. Hints, tips and common questions.\e[0m
- Q.These commands seem very long! Can I shorten them?
+ \e[1mQ.\e[22mThese commands seem very long! Can I shorten them?
- A.Of course you can and the usual abbreviations work. If you are
+ \e[1mA.\e[22mOf course you can and the usual abbreviations work. If you are
unsure, try it.
- Q.I am not sure if this command is correct. Can I cause any harm if I
+ \e[1mQ.\e[22mI am not sure if this command is correct. Can I cause any harm if I
try it?
- A.Do not be afraid to try a command to see if it will work, at the
+ \e[1mA.\e[22mDo not be afraid to try a command to see if it will work, at the
worst you will get an error message. If you require any help on a
command, just type help followed by the command you want help on.
Look at the "DXSpider Command Reference" section to see what help can
be found.
- Q.How should I use the announce command?
+ \e[1mQ.\e[22mHow should I use the announce command?
- A.With respect. Use the command by all means, but please only use the
+ \e[1mA.\e[22mWith respect. Use the command by all means, but please only use the
"full" extension if absolutely necessary. It can create a LOT of
messages passing between clusters.
- Q.I like to be working in the shack while logged into the cluster but
+ \e[1mQ.\e[22mI like to be working in the shack while logged into the cluster but
I can't be looking at the screen all the time. How can I be alerted
when anything happens?
- A.Use the SET/BEEP command. You can find information on this in the
+ \e[1mA.\e[22mUse the \e[1mSET/BEEP \e[22mcommand. You can find information on this in the
"DXSpider Command Reference" section.
- Q.I got disconnected from the cluster and now I can't log back in
+ \e[1mQ.\e[22mI got disconnected from the cluster and now I can't log back in
again. What is wrong?
- A.Probably the cluster thinks you are still logged on and will not let
+ \e[1mA.\e[22mProbably the cluster thinks you are still logged on and will not let
you reconnect using the same call to prevent loops. Try logging on
again adding an ssid to your callsign as DXSpider treats G0YLM and
G0YLM-1 as different users.
- Q.How do I know if I have got the latest version of this user manual?
+ \e[1mQ.\e[22mHow do I know if I have got the latest version of this user manual?
- A.The latest and greatest will always be on the Website. It will also
+ \e[1mA.\e[22mThe latest and greatest will always be on the Website. It will also
be included with every release of DXSpider. As always, if unsure, ask
your sysop what version number is the latest.
- 12. The DXSpider Command Reference
+ \e[1m12. The DXSpider Command Reference\e[0m
- 12.1. accept
+ \e[1m12.1. accept\e[0m
- accept Set a filter to accept something
+ \e[1maccept \e[22mSet a filter to accept something
Create a filter to accept something
There are 2 types of filter, accept and reject. See HELP FILTERING
for more info.
- 12.2. accept/announce [0-9] <pattern>
+
\e[1m12.2. accept/announce [0-9] <pattern>
\e[0m
- accept/announce [0-9] <pattern> Set an 'accept' filter line for
+ \e[1maccept/announce [0-9] <pattern> \e[22mSet an 'accept' filter line for
announce
but this probably for advanced users...
- 12.3. accept/spots [0-9] <pattern>
+
\e[1m12.3. accept/spots [0-9] <pattern>
\e[0m
- accept/spots [0-9] <pattern> Set an 'accept' filter line for spots
+ \e[1maccept/spots [0-9] <pattern> \e[22mSet an 'accept' filter line for spots
Create an 'accept this spot' line for a filter.
- 12.4. accept/wcy [0-9] <pattern>
+
\e[1m12.4. accept/wcy [0-9] <pattern>
\e[0m
- accept/wcy [0-9] <pattern> set an 'accept' WCY filter
+ \e[1maccept/wcy [0-9] <pattern> \e[22mset an 'accept' WCY filter
It is unlikely that you will want to do this, but if you do then you
See HELP FILTER for information.
- 12.5. accept/wwv [0-9] <pattern>
+
\e[1m12.5. accept/wwv [0-9] <pattern>
\e[0m
- accept/wwv [0-9] <pattern> set an 'accept' WWV filter
+ \e[1maccept/wwv [0-9] <pattern> \e[22mset an 'accept' WWV filter
It is unlikely that you will want to do this, but if you do then you
See HELP FILTER for information.
- 12.6. announce <text>
+ \e[1m12.6. announce <text>\e[0m
- announce <text> Send an announcement to LOCAL users only
+ \e[1mannounce <text> \e[22mSend an announcement to LOCAL users only
<text> is the text of the announcement you wish to broadcast
- 12.7. announce full <text>
+ \e[1m12.7. announce full <text>\e[0m
- announce full <text> Send an announcement cluster wide
+ \e[1mannounce full <text> \e[22mSend an announcement cluster wide
This will send your announcement cluster wide
- 12.8. apropos <string>
+ \e[1m12.8. apropos <string>\e[0m
- apropos <string> Search help database for <string>
+ \e[1mapropos <string> \e[22mSearch help database for <string>
Search the help database for <string> (it isn't case sensitive), and
print the names of all the commands that may be relevant.
- 12.9. blank [<string>] [<nn>]
+ \e[1m12.9. blank [<string>] [<nn>]\e[0m
- blank [<string>] [<nn>] Print nn (default 1) blank lines (or strings)
+ \e[1mblank [<string>] [<nn>] \e[22mPrint nn (default 1) blank lines (or strings)
In its basic form this command prints one or more blank lines. However
- 12.10. bye
+ \e[1m12.10. bye\e[0m
- bye Exit from the cluster
+ \e[1mbye \e[22mExit from the cluster
This will disconnect you from the cluster
- 12.11. chat <group> <text>
+ \e[1m12.11. chat <group> <text>\e[0m
- chat <group> <text> Chat or Conference to a group
+ \e[1mchat <group> <text> \e[22mChat or Conference to a group
It is now possible to JOIN a group and have network wide conferencing
See also JOIN, LEAVE, SHOW/CHAT
- 12.12. clear/announce [1|all]
+ \e[1m12.12. clear/announce [1|all]\e[0m
- clear/announce [1|all] Clear a announce filter line
+ \e[1mclear/announce [1|all] \e[22mClear a announce filter line
This command allows you to clear (remove) a line in a annouce filter
see CLEAR/SPOTS for a more detailed explanation.
- 12.13. clear/route [1|all]
+ \e[1m12.13. clear/route [1|all]\e[0m
- clear/route [1|all] Clear a route filter line
+ \e[1mclear/route [1|all] \e[22mClear a route filter line
This command allows you to clear (remove) a line in a route filter or
see CLEAR/SPOTS for a more detailed explanation.
- 12.14. clear/spots [0-9|all]
+ \e[1m12.14. clear/spots [0-9|all]\e[0m
- clear/spots [0-9|all] Clear a spot filter line
+ \e[1mclear/spots [0-9|all] \e[22mClear a spot filter line
This command allows you to clear (remove) a line in a spot filter or
the filter will be completely removed.
- 12.15. clear/wcy [1|all]
+ \e[1m12.15. clear/wcy [1|all]\e[0m
- clear/wcy [1|all] Clear a WCY filter line
+ \e[1mclear/wcy [1|all] \e[22mClear a WCY filter line
This command allows you to clear (remove) a line in a WCY filter or to
see CLEAR/SPOTS for a more detailed explanation.
- 12.16. clear/wwv [1|all]
+ \e[1m12.16. clear/wwv [1|all]\e[0m
- clear/wwv [1|all] Clear a WWV filter line
+ \e[1mclear/wwv [1|all] \e[22mClear a WWV filter line
This command allows you to clear (remove) a line in a WWV filter or to
see CLEAR/SPOTS for a more detailed explanation.
- 12.17. dbavail
+ \e[1m12.17. dbavail\e[0m
- dbavail Show a list of all the Databases in the system
+ \e[1mdbavail \e[22mShow a list of all the Databases in the system
Title says it all really, this command lists all the databases defined
in the system. It is also aliased to SHOW/COMMAND.
- 12.18. dbshow <dbname> <key>
+ \e[1m12.18. dbshow <dbname> <key>\e[0m
- dbshow <dbname> <key> Display an entry, if it exists, in a database
+ \e[1mdbshow <dbname> <key> \e[22mDisplay an entry, if it exists, in a database
This is the generic user interface to the database to the database
- 12.19. directory
+ \e[1m12.19. directory\e[0m
- directory List messages
+ \e[1mdirectory \e[22mList messages
- 12.20. directory <from>-<to>
+ \e[1m12.20. directory <from>-<to>\e[0m
- directory <from>-<to> List messages <from> message <to> message
+ \e[1mdirectory <from>-<to> \e[22mList messages <from> message <to> message
List the messages in the messages directory.
- 12.21. directory <nn>
+ \e[1m12.21. directory <nn>\e[0m
- directory <nn> List last <nn> messages
+ \e[1mdirectory <nn> \e[22mList last <nn> messages
- 12.22. directory all
+ \e[1m12.22. directory all\e[0m
- directory all List all messages
+ \e[1mdirectory all \e[22mList all messages
- 12.23. directory from <call>
+ \e[1m12.23. directory from <call>\e[0m
- directory from <call> List all messages from <call>
+ \e[1mdirectory from <call> \e[22mList all messages from <call>
- 12.24. directory new
+ \e[1m12.24. directory new\e[0m
- directory new List all new messages
+ \e[1mdirectory new \e[22mList all new messages
- 12.25. directory own
+ \e[1m12.25. directory own\e[0m
- directory own List your own messages
+ \e[1mdirectory own \e[22mList your own messages
- 12.26. directory subject <string>
+ \e[1m12.26. directory subject <string>\e[0m
- directory subject <string> List all messages with <string> in subject
+ \e[1mdirectory subject <string> \e[22mList all messages with <string> in subject
- 12.27. directory to <call>
+ \e[1m12.27. directory to <call>\e[0m
- directory to <call> List all messages to <call>
+ \e[1mdirectory to <call> \e[22mList all messages to <call>
- 12.28. dx [by <call>] <freq> <call> <remarks>
+ \e[1m12.28. dx [by <call>] <freq> <call> <remarks>\e[0m
- dx [by <call>] <freq> <call> <remarks> Send a DX spot
+ \e[1mdx [by <call>] <freq> <call> <remarks> \e[22mSend a DX spot
This is how you send a DX Spot to other users. You can, in fact, now
- 12.29. echo <line>
+ \e[1m12.29. echo <line>\e[0m
- echo <line> Echo the line to the output
+ \e[1mecho <line> \e[22mEcho the line to the output
This command is useful in scripts and so forth for printing the line
- 12.30. filtering...
+ \e[1m12.30. filtering...\e[0m
- filtering... Filtering things in DXSpider
+ \e[1mfiltering... \e[22mFiltering things in DXSpider
There are a number of things you can filter in the DXSpider system.
The next filter line lets through just VHF/UHF spots from EU.
- 12.31. help
+ \e[1m12.31. help\e[0m
- help The HELP Command
+ \e[1mhelp \e[22mThe HELP Command
HELP is available for a number of commands. The syntax is:-
database for the <string> you specify and give you a list of likely
commands to look at with HELP.
- 12.32. join <group>
+ \e[1m12.32. join <group>\e[0m
- join <group> Join a chat or conference group
+ \e[1mjoin <group> \e[22mJoin a chat or conference group
JOIN allows you to join a network wide conference group. To join a
See also CHAT, LEAVE, SHOW/CHAT
- 12.33. kill <from msgno>-<to msgno>
+ \e[1m12.33. kill <from msgno>-<to msgno>\e[0m
- kill <from msgno>-<to msgno> Delete a range of messages
+ \e[1mkill <from msgno>-<to msgno> \e[22mDelete a range of messages
- 12.34. kill <msgno> [<msgno..]
+ \e[1m12.34. kill <msgno> [<msgno..]\e[0m
- kill <msgno> [<msgno..] Delete a message from the local system
+ \e[1mkill <msgno> [<msgno..] \e[22mDelete a message from the local system
- 12.35. kill <msgno> [<msgno> ...]
+ \e[1m12.35. kill <msgno> [<msgno> ...]\e[0m
- kill <msgno> [<msgno> ...] Remove or erase a message from the system
+ \e[1mkill <msgno> [<msgno> ...] \e[22mRemove 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.
- 12.36. kill from <regex>
+ \e[1m12.36. kill from <regex>\e[0m
- kill from <regex> Delete messages FROM a callsign or pattern
+ \e[1mkill from <regex> \e[22mDelete messages FROM a callsign or pattern
- 12.37. kill to <regex>
+ \e[1m12.37. kill to <regex>\e[0m
- kill to <regex> Delete messages TO a callsign or pattern
+ \e[1mkill to <regex> \e[22mDelete messages TO a callsign or pattern
- 12.38. leave <group>
+ \e[1m12.38. leave <group>\e[0m
- leave <group> Leave a chat or conference group
+ \e[1mleave <group> \e[22mLeave a chat or conference group
LEAVE allows you to leave a network wide conference group. To leave a
See also CHAT, JOIN, SHOW/CHAT
- 12.39. links
+ \e[1m12.39. links\e[0m
- links Show which nodes is physically connected
+ \e[1mlinks \e[22mShow which nodes is physically connected
This is a quick listing that shows which links are connected and some
information about them. See WHO for a list of all connections.
- 12.40. read
+ \e[1m12.40. read\e[0m
- read Read the next unread personal message addressed to you
+ \e[1mread \e[22mRead the next unread personal message addressed to you
- 12.41. read <msgno>
+ \e[1m12.41. read <msgno>\e[0m
- read <msgno> Read the specified message
+ \e[1mread <msgno> \e[22mRead 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.
- 12.42. reject
+ \e[1m12.42. reject\e[0m
- reject Set a filter to reject something
+ \e[1mreject \e[22mSet a filter to reject something
Create a filter to reject something
There are 2 types of filter, accept and reject. See HELP FILTERING
for more info.
- 12.43. reject/announce [0-9] <pattern>
+
\e[1m12.43. reject/announce [0-9] <pattern>
\e[0m
- reject/announce [0-9] <pattern> Set a 'reject' filter line for
+ \e[1mreject/announce [0-9] <pattern> \e[22mSet a 'reject' filter line for
announce
but this probably for advanced users...
- 12.44. reject/spots [0-9] <pattern>
+
\e[1m12.44. reject/spots [0-9] <pattern>
\e[0m
- reject/spots [0-9] <pattern> Set a 'reject' filter line for spots
+ \e[1mreject/spots [0-9] <pattern> \e[22mSet a 'reject' filter line for spots
Create a 'reject this spot' line for a filter.
- 12.45. reject/wcy [0-9] <pattern>
+
\e[1m12.45. reject/wcy [0-9] <pattern>
\e[0m
- reject/wcy [0-9] <pattern> set a 'reject' WCY filter
+ \e[1mreject/wcy [0-9] <pattern> \e[22mset a 'reject' WCY filter
It is unlikely that you will want to do this, but if you do then you
See HELP FILTER for information.
- 12.46. reject/wwv [0-9] <pattern>
+
\e[1m12.46. reject/wwv [0-9] <pattern>
\e[0m
- reject/wwv [0-9] <pattern> set a 'reject' WWV filter
+ \e[1mreject/wwv [0-9] <pattern> \e[22mset a 'reject' WWV filter
It is unlikely that you will want to do this, but if you do then you
See HELP FILTER for information.
- 12.47. reply
+ \e[1m12.47. reply\e[0m
- reply Reply (privately) to the last message that you have read
+ \e[1mreply \e[22mReply (privately) to the last message that you have read
- 12.48. reply <msgno>
+ \e[1m12.48. reply <msgno>\e[0m
- reply <msgno> Reply (privately) to the specified message
+ \e[1mreply <msgno> \e[22mReply (privately) to the specified message
- 12.49. reply b <msgno>
+ \e[1m12.49. reply b <msgno>\e[0m
- reply b <msgno> Reply as a Bulletin to the specified message
+ \e[1mreply b <msgno> \e[22mReply as a Bulletin to the specified message
- 12.50. reply noprivate <msgno>
+ \e[1m12.50. reply noprivate <msgno>\e[0m
- reply noprivate <msgno> Reply as a Bulletin to the specified message
+ \e[1mreply noprivate <msgno> \e[22mReply as a Bulletin to the specified message
- 12.51. reply rr <msgno>
+ \e[1m12.51. reply rr <msgno>\e[0m
- reply rr <msgno> Reply to the specified message with read receipt
+ \e[1mreply rr <msgno> \e[22mReply to the specified message with read receipt
You can reply to a message and the subject will automatically have
NOPRIVATE, B that you can use with the SEND command (see SEND for
further details)
- 12.52. send <call> [<call> ...]
+ \e[1m12.52. send <call> [<call> ...]\e[0m
- send <call> [<call> ...] Send a message to one or more callsigns
+ \e[1msend <call> [<call> ...] \e[22mSend a message to one or more callsigns
- 12.53. send copy <msgno> <call>
+ \e[1m12.53. send copy <msgno> <call>\e[0m
- send copy <msgno> <call> Send a copy of a message to someone
+ \e[1msend copy <msgno> <call> \e[22mSend a copy of a message to someone
- 12.54. send noprivate <call>
+ \e[1m12.54. send noprivate <call>\e[0m
- send noprivate <call> Send a message to all stations
+ \e[1msend noprivate <call> \e[22mSend a message to all stations
All the SEND commands will create a message which will be sent either
You can carry on with the message until you are ready to send it.
- 12.55. send private <call>
+ \e[1m12.55. send private <call>\e[0m
- send private <call> Send a personal message
+ \e[1msend private <call> \e[22mSend a personal message
- 12.56. send rr <call>
+ \e[1m12.56. send rr <call>\e[0m
- send rr <call> Send a message and ask for a read receipt
+ \e[1msend rr <call> \e[22mSend a message and ask for a read receipt
- 12.57. set/address <your address>
+ \e[1m12.57. set/address <your address>\e[0m
- set/address <your address> Record your postal address
+ \e[1mset/address <your address> \e[22mRecord your postal address
- 12.58. set/announce
+ \e[1m12.58. set/announce\e[0m
- set/announce Allow announce messages to come out on your terminal
+ \e[1mset/announce \e[22mAllow announce messages to come out on your terminal
- 12.59. set/anntalk
+ \e[1m12.59. set/anntalk\e[0m
- set/anntalk Allow talk like announce messages on your terminal
+ \e[1mset/anntalk \e[22mAllow talk like announce messages on your terminal
- 12.60. set/beep
+ \e[1m12.60. set/beep\e[0m
- set/beep Add a beep to DX and other messages on your terminal
+ \e[1mset/beep \e[22mAdd a beep to DX and other messages on your terminal
- 12.61. set/dx
+ \e[1m12.61. set/dx\e[0m
- set/dx Allow DX messages to come out on your terminal
+ \e[1mset/dx \e[22mAllow DX messages to come out on your terminal
- 12.62. set/dxcq
+ \e[1m12.62. set/dxcq\e[0m
- set/dxcq Show CQ Zones on the end of DX announcements
+ \e[1mset/dxcq \e[22mShow CQ Zones on the end of DX announcements
- 12.63. set/dxgrid
+ \e[1m12.63. set/dxgrid\e[0m
- set/dxgrid Allow QRA Grid Squares on the end of DX announcements
+ \e[1mset/dxgrid \e[22mAllow QRA Grid Squares on the end of DX announcements
- 12.64. set/dxitu
+ \e[1m12.64. set/dxitu\e[0m
- set/dxitu Show ITU Zones on the end of DX announcements
+ \e[1mset/dxitu \e[22mShow ITU Zones on the end of DX announcements
- 12.65. set/echo
+ \e[1m12.65. set/echo\e[0m
- set/echo Make the cluster echo your input
+ \e[1mset/echo \e[22mMake the cluster echo your input
- 12.66. set/email <email> ...
+ \e[1m12.66. set/email <email> ...\e[0m
- set/email <email> ... Set email address(es) and forward your personals
+ \e[1mset/email <email> ... \e[22mSet email address(es) and forward your personals
- 12.67. set/here
+ \e[1m12.67. set/here\e[0m
- set/here Tell the system you are present at your terminal
+ \e[1mset/here \e[22mTell the system you are present at your terminal
- 12.68. set/homenode <node>
+ \e[1m12.68. set/homenode <node>\e[0m
- set/homenode <node> Set your normal cluster callsign
+ \e[1mset/homenode <node> \e[22mSet your normal cluster callsign
Tell the cluster system where you normally connect to. Any Messages
- 12.69. set/language <lang>
+ \e[1m12.69. set/language <lang>\e[0m
- set/language <lang> Set the language you want to use
+ \e[1mset/language <lang> \e[22mSet the language you want to use
You can select the language that you want the cluster to use.
(Spanish), Czech (cz), French (fr), Portuguese (pt), Italian (it) and
nl (Dutch).
- 12.70. set/location <lat & long>
+ \e[1m12.70. set/location <lat & long>\e[0m
- set/location <lat & long> Set your latitude and longitude
+ \e[1mset/location <lat & long> \e[22mSet your latitude and longitude
- 12.71. set/logininfo
+ \e[1m12.71. set/logininfo\e[0m
- set/logininfo Inform when a station logs in locally
+ \e[1mset/logininfo \e[22mInform when a station logs in locally
- 12.72. set/name <your name>
+ \e[1m12.72. set/name <your name>\e[0m
- set/name <your name> Set your name
+ \e[1mset/name <your name> \e[22mSet your name
Tell the system what your name is eg:-
- 12.73. set/page <lines per page>
+ \e[1m12.73. set/page <lines per page>\e[0m
- set/page <lines per page> Set the lines per page
+ \e[1mset/page <lines per page> \e[22mSet the lines per page
Tell the system how many lines you wish on a page when the number of
The setting is stored in your user profile.
- 12.74. set/password
+ \e[1m12.74. set/password\e[0m
- set/password Set your own password
+ \e[1mset/password \e[22mSet your own password
This command only works for a 'telnet' user (currently). It will only
it right). You may or may not see the data echoed on the screen as you
type, depending on the type of telnet client you have.
- 12.75. set/prompt <string>
+ \e[1m12.75. set/prompt <string>\e[0m
- set/prompt <string> Set your prompt to <string>
+ \e[1mset/prompt <string> \e[22mSet your prompt to <string>
- 12.76. set/qra <locator>
+ \e[1m12.76. set/qra <locator>\e[0m
- set/qra <locator> Set your QRA Grid locator
+ \e[1mset/qra <locator> \e[22mSet your QRA Grid locator
Tell the system what your QRA (or Maidenhead) locator is. If you have
- 12.77. set/qth <your qth>
+ \e[1m12.77. set/qth <your qth>\e[0m
- set/qth <your qth> Set your QTH
+ \e[1mset/qth <your qth> \e[22mSet your QTH
Tell the system where you are. For example:-
- 12.78. set/talk
+ \e[1m12.78. set/talk\e[0m
- set/talk Allow TALK messages to come out on your terminal
+ \e[1mset/talk \e[22mAllow TALK messages to come out on your terminal
- 12.79. set/usstate
+ \e[1m12.79. set/usstate\e[0m
- set/usstate Allow US State info on the end of DX announcements
+ \e[1mset/usstate \e[22mAllow US State info on the end of DX announcements
- 12.80. set/wcy
+ \e[1m12.80. set/wcy\e[0m
- set/wcy Allow WCY messages to come out on your terminal
+ \e[1mset/wcy \e[22mAllow WCY messages to come out on your terminal
- 12.81. set/wwv
+ \e[1m12.81. set/wwv\e[0m
- set/wwv Allow WWV messages to come out on your terminal
+ \e[1mset/wwv \e[22mAllow WWV messages to come out on your terminal
- 12.82. set/wx
+ \e[1m12.82. set/wx\e[0m
- set/wx Allow WX messages to come out on your terminal
+ \e[1mset/wx \e[22mAllow WX messages to come out on your terminal
- 12.83. show/chat [<group>] [<lines>]
+ \e[1m12.83. show/chat [<group>] [<lines>]\e[0m
- show/chat [<group>] [<lines>] Show any chat or conferencing
+ \e[1mshow/chat [<group>] [<lines>] \e[22mShow any chat or conferencing
This command allows you to see any chat or conferencing that has
all groups. If you use a group name then it will show only chat for
that group.
- 12.84. show/configuration [<node>]
+ \e[1m12.84. show/configuration [<node>]\e[0m
- show/configuration [<node>] Show all the nodes and users visible
+ \e[1mshow/configuration [<node>] \e[22mShow all the nodes and users visible
This command allows you to see all the users that can be seen and the
- 12.85. show/configuration/node
+ \e[1m12.85. show/configuration/node\e[0m
- show/configuration/node Show all the nodes connected locally
+ \e[1mshow/configuration/node \e[22mShow all the nodes connected locally
Show all the nodes connected to this node.
- 12.86. show/contest <year and month>
+ \e[1m12.86. show/contest <year and month>\e[0m
- show/contest <year and month> Show all the contests for a month
+ \e[1mshow/contest <year and month> \e[22mShow all the contests for a month
Show all known contests which are maintained at
- 12.87. show/date [<prefix>|<callsign>]
+
\e[1m12.87. show/date [<prefix>|<callsign>]
\e[0m
- show/date [<prefix>|<callsign>] Show the local time
+ \e[1mshow/date [<prefix>|<callsign>] \e[22mShow the local time
This is very nearly the same as SHOW/TIME, the only difference the
prefixes then it will show UTC and UTC + the local offset (not
including DST) at the prefixes or callsigns that you specify.
- 12.88. show/db0sdx <callsign>
+ \e[1m12.88. show/db0sdx <callsign>\e[0m
- show/db0sdx <callsign> Show QSL infomation from DB0SDX database
+ \e[1mshow/db0sdx <callsign> \e[22mShow QSL infomation from DB0SDX database
This command queries the DB0SDX QSL server on the internet and returns
See also SHOW/QRZ, SHOW/WM7D.
- 12.89. show/dx
+ \e[1m12.89. show/dx\e[0m
- show/dx Interrogate the spot database
+ \e[1mshow/dx \e[22mInterrogate the spot database
If you just type SHOW/DX you will get the last so many spots (sysop
- 12.90. show/dxcc <prefix>
+
\e[1m12.90. show/dxcc <prefix>
\e[0m
- show/dxcc <prefix> Interrogate the spot database by country
+ \e[1mshow/dxcc <prefix> \e[22mInterrogate the spot database by country
This command takes the <prefix> (which can be a full or partial
- 12.91. show/dxqsl <callsign>
+ \e[1m12.91. show/dxqsl <callsign>\e[0m
- show/dxqsl <callsign> Show any QSL info gathered from spots
+ \e[1mshow/dxqsl <callsign> \e[22mShow any QSL info gathered from spots
The node collects information from the comment fields in spots (things
This gives you more background information.
- 12.92. show/dxstats [days] [date]
+ \e[1m12.92. show/dxstats [days] [date]\e[0m
- show/dxstats [days] [date] Show the DX Statistics
+ \e[1mshow/dxstats [days] [date] \e[22mShow the DX Statistics
Show the total DX spots for the last <days> no of days (default is
31), starting from a <date> (default: today).
- 12.93. show/files [<filearea> [<string>]]
+ \e[1m12.93. show/files [<filearea> [<string>]]\e[0m
- show/files [<filearea> [<string>]] List the contents of a filearea
+ \e[1mshow/files [<filearea> [<string>]] \e[22mList the contents of a filearea
SHOW/FILES on its own will show you a list of the various fileareas
See also TYPE - to see the contents of a file.
- 12.94. show/filter
+ \e[1m12.94. show/filter\e[0m
- show/filter Show the contents of all the filters you have set
+ \e[1mshow/filter \e[22mShow the contents of all the filters you have set
Show the contents of all the filters that are set. This command
displays all the filters set - for all the various categories.
- 12.95. show/hfstats [days] [date]
+ \e[1m12.95. show/hfstats [days] [date]\e[0m
- show/hfstats [days] [date] Show the HF DX Statistics
+ \e[1mshow/hfstats [days] [date] \e[22mShow the HF DX Statistics
Show the HF DX spots breakdown by band for the last <days> no of days
- 12.96. show/hftable [days] [date] [prefix ...]
+ \e[1m12.96. show/hftable [days] [date] [prefix ...]\e[0m
- show/hftable [days] [date] [prefix ...] Show the HF DX Spotter Table
+ \e[1mshow/hftable [days] [date] [prefix ...] \e[22mShow the HF DX Spotter Table
Show the HF DX Spotter table for the list of prefixes for the last
- 12.97. show/moon [ndays] [<prefix>|<callsign>]
+
\e[1m12.97. show/moon [ndays] [<prefix>|<callsign>]
\e[0m
- show/moon [ndays] [<prefix>|<callsign>] Show Moon rise and set times
+ \e[1mshow/moon [ndays] [<prefix>|<callsign>] \e[22mShow 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
Please note that the rise and set times are given as the UT times of
rise and set on the requested UT day.
- 12.98. show/muf <prefix> [<hours>][long]
+
\e[1m12.98. show/muf <prefix> [<hours>][long]
\e[0m
- show/muf <prefix> [<hours>][long] Show the likely propagation to a
+ \e[1mshow/muf <prefix> [<hours>][long] \e[22mShow the likely propagation to a
prefix
should be noted that the figures will probably not be very useful, nor
terrible accurate, but it is included for completeness.
- 12.99. show/newconfiguration [<node>]
+ \e[1m12.99. show/newconfiguration [<node>]\e[0m
- show/newconfiguration [<node>] Show all the nodes and users visible
+ \e[1mshow/newconfiguration [<node>] \e[22mShow all the nodes and users visible
This command allows you to see all the users that can be seen and the
BE WARNED: the list that is returned can be VERY long
- 12.100. show/newconfiguration/node
+ \e[1m12.100. show/newconfiguration/node\e[0m
- show/newconfiguration/node Show all the nodes connected locally
+ \e[1mshow/newconfiguration/node \e[22mShow all the nodes connected locally
Show all the nodes connected to this node in the new format.
- 12.101. show/prefix <callsign>
+ \e[1m12.101. show/prefix <callsign>\e[0m
- show/prefix <callsign> Interrogate the prefix database
+ \e[1mshow/prefix <callsign> \e[22mInterrogate the prefix database
This command takes the <callsign> (which can be a full or partial
See also SHOW/DXCC
- 12.102. show/qra <lat> <long>
+ \e[1m12.102. show/qra <lat> <long>\e[0m
- show/qra <lat> <long> Convert lat/long to a QRA Grid locator
+ \e[1mshow/qra <lat> <long> \e[22mConvert lat/long to a QRA Grid locator
This is a multipurpose command that allows you either to calculate the
- 12.103. show/qra <locator> [<locator>]
+ \e[1m12.103. show/qra <locator> [<locator>]\e[0m
- show/qra <locator> [<locator>] Show distance between QRA Grid locators
+ \e[1mshow/qra <locator> [<locator>] \e[22mShow distance between QRA Grid locators
- 12.104. show/qrz <callsign>
+ \e[1m12.104. show/qrz <callsign>\e[0m
- show/qrz <callsign> Show any callbook details on a callsign
+ \e[1mshow/qrz <callsign> \e[22mShow any callbook details on a callsign
This command queries the QRZ callbook server on the internet and
See also SHOW/WM7D for an alternative.
- 12.105. show/route <callsign> ...
+ \e[1m12.105. show/route <callsign> ...\e[0m
- show/route <callsign> ... Show the route to the callsign
+ \e[1mshow/route <callsign> ... \e[22mShow the route to the callsign
This command allows you to see to which node the callsigns specified
- 12.106. show/satellite <name> [<hours> <interval>]
+ \e[1m12.106. show/satellite <name> [<hours> <interval>]\e[0m
- show/satellite <name> [<hours> <interval>] Show tracking data
+ \e[1mshow/satellite <name> [<hours> <interval>] \e[22mShow tracking data
Show the tracking data from your location to the satellite of your
- 12.107. show/station [<callsign> ..]
+ \e[1m12.107. show/station [<callsign> ..]\e[0m
- show/station [<callsign> ..] Show information about a callsign
+ \e[1mshow/station [<callsign> ..] \e[22mShow information about a callsign
Show the information known about a callsign and whether (and where)
If no callsign is given then show the information for yourself.
- 12.108. show/sun [ndays] [<prefix>|<callsign>]
+
\e[1m12.108. show/sun [ndays] [<prefix>|<callsign>]
\e[0m
- show/sun [ndays] [<prefix>|<callsign>] Show sun rise and set times
+ \e[1mshow/sun [ndays] [<prefix>|<callsign>] \e[22mShow sun rise and set times
Show the sun rise and set times for a (list of) prefixes or callsigns,
Please note that the rise and set times are given as the UT times of
rise and set on the requested UT day.
- 12.109. show/time [<prefix>|<callsign>]
+
\e[1m12.109. show/time [<prefix>|<callsign>]
\e[0m
- show/time [<prefix>|<callsign>] Show the local time
+ \e[1mshow/time [<prefix>|<callsign>] \e[22mShow the local time
If no prefixes or callsigns are given then this command returns the
prefixes then it will show UTC and UTC + the local offset (not
including DST) at the prefixes or callsigns that you specify.
- 12.110. show/usdb [call ..]
+ \e[1m12.110. show/usdb [call ..]\e[0m
- show/usdb [call ..] Show information held on the FCC Call database
+ \e[1mshow/usdb [call ..] \e[22mShow information held on the FCC Call database
Show the City and State of a Callsign held on the FCC database if his
- 12.111. show/vhfstats [days] [date]
+ \e[1m12.111. show/vhfstats [days] [date]\e[0m
- show/vhfstats [days] [date] Show the VHF DX Statistics
+ \e[1mshow/vhfstats [days] [date] \e[22mShow 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).
- 12.112. show/vhftable [days] [date] [prefix ...]
+ \e[1m12.112. show/vhftable [days] [date] [prefix ...]\e[0m
- show/vhftable [days] [date] [prefix ...] Show the VHF DX Spotter Table
+ \e[1mshow/vhftable [days] [date] [prefix ...] \e[22mShow the VHF DX Spotter Table
Show the VHF DX Spotter table for the list of prefixes for the last
- 12.113. show/wcy
+ \e[1m12.113. show/wcy\e[0m
- show/wcy Show last 10 WCY broadcasts
+ \e[1mshow/wcy \e[22mShow last 10 WCY broadcasts
- 12.114. show/wcy <n>
+ \e[1m12.114. show/wcy <n>\e[0m
- show/wcy <n> Show last <n> WCY broadcasts
+ \e[1mshow/wcy <n> \e[22mShow last <n> WCY broadcasts
Display the most recent WCY information that has been received by the
system
- 12.115. show/wm7d <callsign>
+ \e[1m12.115. show/wm7d <callsign>\e[0m
- show/wm7d <callsign> Show callbook details on a US callsigns
+ \e[1mshow/wm7d <callsign> \e[22mShow callbook details on a US callsigns
This command queries the WM7D callbook server on the internet and
See also SHOW/QRZ.
- 12.116. show/wwv
+ \e[1m12.116. show/wwv\e[0m
- show/wwv Show last 10 WWV broadcasts
+ \e[1mshow/wwv \e[22mShow last 10 WWV broadcasts
- 12.117. show/wwv <n>
+ \e[1m12.117. show/wwv <n>\e[0m
- show/wwv <n> Show last <n> WWV broadcasts
+ \e[1mshow/wwv <n> \e[22mShow last <n> WWV broadcasts
Display the most recent WWV information that has been received by the
system
- 12.118. sysop
+ \e[1m12.118. sysop\e[0m
- sysop Regain your privileges if you login remotely
+ \e[1msysop \e[22mRegain your privileges if you login remotely
The system automatically reduces your privilege level to that of a
numbers but nothing will happen when you input a string. Any match is
case sensitive.
- 12.119. talk <call> > <node> [<text>]
+ \e[1m12.119. talk <call> > <node> [<text>]\e[0m
- talk <call> > <node> [<text>] Send a text message to another station
+ \e[1mtalk <call> > <node> [<text>] \e[22mSend a text message to another station
via a node
will send the hftable as you have it to all the people you are
currently talking to.
- 12.120. talk <call> [<text>]
+ \e[1m12.120. talk <call> [<text>]\e[0m
- talk <call> [<text>] Send a text message to another station
+ \e[1mtalk <call> [<text>] \e[22mSend a text message to another station
- 12.121. type <filearea>/<name>
+ \e[1m12.121. type <filearea>/<name>\e[0m
- type <filearea>/<name> Look at the contents of a file in one of the
+ \e[1mtype <filearea>/<name> \e[22mLook at the contents of a file in one of the
fileareas
See also SHOW/FILES to see what fileareas are available and a list of
content.
- 12.122. unset/announce
+ \e[1m12.122. unset/announce\e[0m
- unset/announce Stop announce messages coming out on your terminal
+ \e[1munset/announce \e[22mStop announce messages coming out on your terminal
- 12.123. unset/anntalk
+ \e[1m12.123. unset/anntalk\e[0m
- unset/anntalk Stop talk like announce messages on your terminal
+ \e[1munset/anntalk \e[22mStop talk like announce messages on your terminal
The announce system on legacy cluster nodes is used as a talk
allows you to see them again. This is the default.
- 12.124. unset/beep
+ \e[1m12.124. unset/beep\e[0m
- unset/beep Stop beeps for DX and other messages on your terminal
+ \e[1munset/beep \e[22mStop beeps for DX and other messages on your terminal
- 12.125. unset/dx
+ \e[1m12.125. unset/dx\e[0m
- unset/dx Stop DX messages coming out on your terminal
+ \e[1munset/dx \e[22mStop DX messages coming out on your terminal
- 12.126. unset/dxcq
+ \e[1m12.126. unset/dxcq\e[0m
- unset/dxcq Stop CQ Zones on the end of DX announcements
+ \e[1munset/dxcq \e[22mStop CQ Zones on the end of DX announcements
Display both the Spotter's and the Spotted's CQ Zone on the end of a
Do a STAT/USER to see which flags you have set if you are confused.
- 12.127. unset/dxgrid
+ \e[1m12.127. unset/dxgrid\e[0m
- unset/dxgrid Stop QRA Grid Squares on the end of DX announcements
+ \e[1munset/dxgrid \e[22mStop QRA Grid Squares on the end of DX announcements
A standard feature which is enabled in version 1.43 and above is that
Do a STAT/USER to see which flags you have set if you are confused.
- 12.128. unset/dxitu
+ \e[1m12.128. unset/dxitu\e[0m
- unset/dxitu Stop ITU Zones on the end of DX announcements
+ \e[1munset/dxitu \e[22mStop ITU Zones on the end of DX announcements
Display both the Spotter's and the Spotted's ITU Zone on the end of a
Do a STAT/USER to see which flags you have set if you are confused.
- 12.129. unset/echo
+ \e[1m12.129. unset/echo\e[0m
- unset/echo Stop the cluster echoing your input
+ \e[1munset/echo \e[22mStop the cluster echoing your input
If you are connected via a telnet session, different implimentations
YOU DO NOT NEED TO USE THIS COMMAND IF YOU ARE CONNECTED VIA AX25.
- 12.130. unset/email
+ \e[1m12.130. unset/email\e[0m
- unset/email Stop personal msgs being forwarded by email
+ \e[1munset/email \e[22mStop personal msgs being forwarded by email
If any personal messages come in for your callsign then you can use
- 12.131. unset/here
+ \e[1m12.131. unset/here\e[0m
- unset/here Tell the system you are absent from your terminal
+ \e[1munset/here \e[22mTell the system you are absent from your terminal
- 12.132. unset/logininfo
+ \e[1m12.132. unset/logininfo\e[0m
- unset/logininfo Inform when a station logs out locally
+ \e[1munset/logininfo \e[22mInform when a station logs out locally
- 12.133. unset/privilege
+ \e[1m12.133. unset/privilege\e[0m
- unset/privilege Remove any privilege for this session
+ \e[1munset/privilege \e[22mRemove any privilege for this session
You can use this command to 'protect' this session from unauthorised
either logout and login again (if you are on a console) or use the
SYSOP command.
- 12.134. unset/prompt
+ \e[1m12.134. unset/prompt\e[0m
- unset/prompt Set your prompt back to default
+ \e[1munset/prompt \e[22mSet your prompt back to default
This command will set your user prompt to exactly the string that you
UNSET/PROMPT will undo the SET/PROMPT command and set you prompt back
to normal.
- 12.135. unset/talk
+ \e[1m12.135. unset/talk\e[0m
- unset/talk Stop TALK messages coming out on your terminal
+ \e[1munset/talk \e[22mStop TALK messages coming out on your terminal
- 12.136. unset/usstate
+ \e[1m12.136. unset/usstate\e[0m
- unset/usstate Stop US State info on the end of DX announcements
+ \e[1munset/usstate \e[22mStop 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
Do a STAT/USER to see which flags you have set if you are confused.
- 12.137. unset/wcy
+ \e[1m12.137. unset/wcy\e[0m
- unset/wcy Stop WCY messages coming out on your terminal
+ \e[1munset/wcy \e[22mStop WCY messages coming out on your terminal
- 12.138. unset/wwv
+ \e[1m12.138. unset/wwv\e[0m
- unset/wwv Stop WWV messages coming out on your terminal
+ \e[1munset/wwv \e[22mStop WWV messages coming out on your terminal
- 12.139. unset/wx
+ \e[1m12.139. unset/wx\e[0m
- unset/wx Stop WX messages coming out on your terminal
+ \e[1munset/wx \e[22mStop WX messages coming out on your terminal
- 12.140. who
+ \e[1m12.140. who\e[0m
- who Show who is physically connected
+ \e[1mwho \e[22mShow who is physically connected
This is a quick listing that shows which callsigns are connected and
what sort of connection they have
- 12.141. wx <text>
+ \e[1m12.141. wx <text>\e[0m
- wx <text> Send a weather message to local users
+ \e[1mwx <text> \e[22mSend a weather message to local users
- 12.142. wx full <text>
+ \e[1m12.142. wx full <text>\e[0m
- wx full <text> Send a weather message to all cluster users
+ \e[1mwx full <text> \e[22mSend a weather message to all cluster users
projects / spider.git / commitdiff