mirror of
git://scm.dxcluster.org/scm/spider
synced 2024-09-21 15:57:12 +00:00
2260 lines
73 KiB
HTML
2260 lines
73 KiB
HTML
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN">
|
|
<HTML>
|
|
<HEAD>
|
|
<META NAME="GENERATOR" CONTENT="SGML-Tools 1.0.9">
|
|
<TITLE>The DXSpider Administration Manual v1.47: The DXSpider command set</TITLE>
|
|
<LINK HREF="adminmanual-8.html" REL=previous>
|
|
<LINK HREF="adminmanual.html#toc9" REL=contents>
|
|
<link rel=stylesheet href="style.css" type="text/css" title="default stylesheet">
|
|
</HEAD>
|
|
<BODY>
|
|
Next
|
|
<A HREF="adminmanual-8.html">Previous</A>
|
|
<A HREF="adminmanual.html#toc9">Contents</A>
|
|
<HR>
|
|
<H2><A NAME="s9">9. The DXSpider command set</A></H2>
|
|
|
|
<P>Below is a complete list of commands available from the cluster prompt.
|
|
Most maintenance tasks are automatic but there are some commands that are useful
|
|
for a sysop. These are listed below in alphabetical order. The number in
|
|
brackets following the command name is the permissions level needed to use
|
|
the command.
|
|
<P>
|
|
<H2><A NAME="ss9.1">9.1 accept/announce (0)</A>
|
|
</H2>
|
|
|
|
<P><CODE><B>accept/announce [0-9] <pattern></B> Set an accept filter
|
|
line for announce</CODE>
|
|
<P>
|
|
<P>Create an 'accept this announce' line for a filter.
|
|
<P>An accept filter line means that if the announce matches this filter it is
|
|
passed onto the user. See HELP FILTERS for more info. Please read this
|
|
to understand how filters work - it will save a lot of grief later on.
|
|
<P>You can use any of the following things in this line:-
|
|
<P>
|
|
<BLOCKQUOTE><CODE>
|
|
<PRE>
|
|
info <string> eg: iota or qsl
|
|
by <prefixes> eg: G,M,2
|
|
origin <prefixes>
|
|
origin_dxcc <numbers> eg: 61,62 (from eg: sh/pre G)
|
|
origin_itu <numbers>
|
|
origin_zone <numbers>
|
|
by_dxcc <numbers>
|
|
by_itu <numbers>
|
|
by_zone <numbers>
|
|
channel <prefixes>
|
|
wx 1 filter WX announces
|
|
dest <prefixes> eg: 6MUK,WDX (distros)
|
|
</PRE>
|
|
</CODE></BLOCKQUOTE>
|
|
<P>some examples:-
|
|
<P>
|
|
<BLOCKQUOTE><CODE>
|
|
<PRE>
|
|
acc/ann dest 6MUK
|
|
acc/ann 2 by_zone 14,15,16
|
|
(this could be all on one line: acc/ann dest 6MUK or by_zone 14,15,16)
|
|
</PRE>
|
|
</CODE></BLOCKQUOTE>
|
|
<P>or
|
|
<P>
|
|
<BLOCKQUOTE><CODE>
|
|
<PRE>
|
|
acc/ann by G,M,2
|
|
</PRE>
|
|
</CODE></BLOCKQUOTE>
|
|
<P>This filter would only allow announces that were posted buy UK stations.
|
|
You can use the tag 'all' to accept everything eg:
|
|
<P>
|
|
<BLOCKQUOTE><CODE>
|
|
<PRE>
|
|
acc/ann all
|
|
</PRE>
|
|
</CODE></BLOCKQUOTE>
|
|
<P>but this probably for advanced users...
|
|
<P>
|
|
<H2><A NAME="ss9.2">9.2 accept/announce (extended for sysops) (8)</A>
|
|
</H2>
|
|
|
|
<P><CODE><B>accept/announce <call> [input] [0-9]<pattern></B> Announce filter sysop version</CODE>
|
|
<P>
|
|
<P>This version allows a sysop to set a filter for a callsign as well as the
|
|
default for nodes and users eg:-
|
|
<P>
|
|
<BLOCKQUOTE><CODE>
|
|
<PRE>
|
|
accept/ann by G,M,2
|
|
accept/ann input node_default by G,M,2
|
|
accept/ann user_default by G,M,2
|
|
</PRE>
|
|
</CODE></BLOCKQUOTE>
|
|
<P>
|
|
<H2><A NAME="ss9.3">9.3 accept/spots (0)</A>
|
|
</H2>
|
|
|
|
<P><CODE><B>accept/announce [0-9] <pattern></B> Set an accept filter line for spots</CODE>
|
|
<P>
|
|
<P>Create an 'accept this spot' line for a filter.
|
|
<P>
|
|
<P>An accept filter line means that if the spot matches this filter it is
|
|
passed onto the user. See HELP FILTERS for more info. Please read this
|
|
to understand how filters work - it will save a lot of grief later on.
|
|
<P>You can use any of the following things in this line:-
|
|
<P>
|
|
<BLOCKQUOTE><CODE>
|
|
<PRE>
|
|
freq <range> eg: 0/30000 or hf or hf/cw or 6m,4m,2m
|
|
on <range> same as 'freq'
|
|
call <prefixes> eg: G,PA,HB9
|
|
info <string> eg: iota or qsl
|
|
by <prefixes>
|
|
call_dxcc <numbers> eg: 61,62 (from eg: sh/pre G)
|
|
call_itu <numbers>
|
|
call_zone <numbers>
|
|
by_dxcc <numbers>
|
|
by_itu <numbers>
|
|
by_zone <numbers>
|
|
origin <prefixes>
|
|
channel <prefixes>
|
|
</PRE>
|
|
</CODE></BLOCKQUOTE>
|
|
<P>
|
|
<P>For frequencies, you can use any of the band names defined in
|
|
SHOW/BANDS and you can use a subband name like: cw, rtty, data, ssb -
|
|
thus: hf/ssb. You can also just have a simple range like: 0/30000 -
|
|
this is more efficient than saying simply: freq HF (but don't get
|
|
too hung up about that)
|
|
<P>some examples:-
|
|
<P>
|
|
<BLOCKQUOTE><CODE>
|
|
<PRE>
|
|
acc/spot 1 on hf/cw
|
|
acc/spot 2 on vhf and (by_zone 14,15,16 or call_zone 14,15,16)
|
|
</PRE>
|
|
</CODE></BLOCKQUOTE>
|
|
<P>You can use the tag 'all' to accept everything, eg:
|
|
<P>
|
|
<BLOCKQUOTE><CODE>
|
|
<PRE>
|
|
acc/spot 3 all
|
|
</PRE>
|
|
</CODE></BLOCKQUOTE>
|
|
<P>but this probably for advanced users...
|
|
<P>
|
|
<H2><A NAME="ss9.4">9.4 accept/spots (extended for sysops) (8)</A>
|
|
</H2>
|
|
|
|
<P><CODE><B>accept/spots <call> [input] [0-9] <pattern></B> Spot filter sysop version</CODE>
|
|
<P>
|
|
<P>This version allows a sysop to set a filter for a callsign as well as the
|
|
default for nodes and users eg:-
|
|
<P>
|
|
<BLOCKQUOTE><CODE>
|
|
<PRE>
|
|
accept/spot db0sue-7 1 by_zone 14,15,16
|
|
accept/spot node_default all
|
|
set/hops node_default 10
|
|
|
|
accept/spot user_default by G,M,2
|
|
</PRE>
|
|
</CODE></BLOCKQUOTE>
|
|
<P>
|
|
<H2><A NAME="ss9.5">9.5 accept/wcy (0)</A>
|
|
</H2>
|
|
|
|
<P><CODE><B>accept/wcy [0-9] <pattern></B> set an accept WCY filter</CODE>
|
|
<P>
|
|
<P>It is unlikely that you will want to do this, but if you do then you can
|
|
filter on the following fields:-
|
|
<P>
|
|
<BLOCKQUOTE><CODE>
|
|
<PRE>
|
|
by <prefixes> eg: G,M,2
|
|
origin <prefixes>
|
|
origin_dxcc <numbers> eg: 61,62 (from eg: sh/pre G)
|
|
origin_itu <numbers>
|
|
origin_zone <numbers>
|
|
by_dxcc <numbers>
|
|
by_itu <numbers>
|
|
by_zone <numbers>
|
|
channel <prefixes>
|
|
</PRE>
|
|
</CODE></BLOCKQUOTE>
|
|
<P>
|
|
<P>There are no examples because WCY Broadcasts only come from one place and
|
|
you either want them or not (see UNSET/WCY if you don't want them).
|
|
<P>This command is really provided for future use.
|
|
<P>See HELP FILTER for information.
|
|
<P>
|
|
<H2><A NAME="ss9.6">9.6 accept/wcy (extended for sysops) (8)</A>
|
|
</H2>
|
|
|
|
<P><CODE><B>accept/wcy <call> [input] [0-9] <pattern></B>
|
|
WCY filter sysop version</CODE>
|
|
<P>
|
|
<P>This version allows a sysop to set a filter for a callsign as well as the
|
|
default for nodes and users eg:-
|
|
<P>
|
|
<BLOCKQUOTE><CODE>
|
|
<PRE>
|
|
accept/wcy node_default all
|
|
set/hops node_default 10
|
|
</PRE>
|
|
</CODE></BLOCKQUOTE>
|
|
<P>
|
|
<H2><A NAME="ss9.7">9.7 accept/wwv (0)</A>
|
|
</H2>
|
|
|
|
<P><CODE><B>accept/wwv [0-9] <pattern></B> Set an accept WWV filter</CODE>
|
|
<P>
|
|
<P>It is unlikely that you will want to do this, but if you do then you can
|
|
filter on the following fields:-
|
|
<P>
|
|
<BLOCKQUOTE><CODE>
|
|
<PRE>
|
|
by <prefixes> eg: G,M,2
|
|
origin <prefixes>
|
|
origin_dxcc <numbers> eg: 61,62 (from eg: sh/pre G)
|
|
origin_itu <numbers>
|
|
origin_zone <numbers>
|
|
by_dxcc <numbers>
|
|
by_itu <numbers>
|
|
by_zone <numbers>
|
|
channel <prefixes>
|
|
</PRE>
|
|
</CODE></BLOCKQUOTE>
|
|
<P>for example
|
|
<P>
|
|
<BLOCKQUOTE><CODE>
|
|
<PRE>
|
|
accept/wwv by_zone 4
|
|
</PRE>
|
|
</CODE></BLOCKQUOTE>
|
|
<P>is probably the only useful thing to do (which will only show WWV broadcasts
|
|
by stations in the US).
|
|
<P>See HELP FILTER for information.
|
|
<P>
|
|
<H2><A NAME="ss9.8">9.8 accept/wwv (extended for sysops) (8)</A>
|
|
</H2>
|
|
|
|
<P><CODE><B>accept/wwv <call> [input] [0-9] <pattern></B>
|
|
WWV filter sysop version</CODE>
|
|
<P>
|
|
<P>This version allows a sysop to set a filter for a callsign as well as the
|
|
default for nodes and users eg:-
|
|
<P>
|
|
<BLOCKQUOTE><CODE>
|
|
<PRE>
|
|
accept/wwv db0sue-7 1 by_zone 4
|
|
accept/wwv node_default all
|
|
set/hops node_default 10
|
|
|
|
accept/wwv user_default by W,K
|
|
</PRE>
|
|
</CODE></BLOCKQUOTE>
|
|
<P>
|
|
<H2><A NAME="ss9.9">9.9 announce (0)</A>
|
|
</H2>
|
|
|
|
<P><CODE><B>announce <text></B> Send an announcement to local users</CODE>
|
|
<P>
|
|
<P>Send an announcement to LOCAL users only, where <text> is the text
|
|
of the announcement you wish to broadcast
|
|
<P>
|
|
<H2><A NAME="ss9.10">9.10 announce full (0)</A>
|
|
</H2>
|
|
|
|
<P><CODE><B>announce full <text></B> Send an announcement cluster wide</CODE>
|
|
<P>
|
|
<P>This command will send your announcement across the whole cluster
|
|
network.
|
|
<P>
|
|
<P>
|
|
<H2><A NAME="ss9.11">9.11 announce sysop (5)</A>
|
|
</H2>
|
|
|
|
<P><CODE><B>announce sysop <text></B></CODE>
|
|
<P>
|
|
<P>Send an announcement to Sysops only
|
|
<P>
|
|
<H2><A NAME="ss9.12">9.12 apropos (0)</A>
|
|
</H2>
|
|
|
|
<P><CODE><B>apropos <string></B> Search the help database</CODE>
|
|
<P>
|
|
<P>Search the help database for <string> (it isn't case sensitive),
|
|
and print the names of all the commands that may be relevant.
|
|
<P>
|
|
<H2><A NAME="ss9.13">9.13 bye (0)</A>
|
|
</H2>
|
|
|
|
<P><CODE><B>bye</B> Exit from the cluster</CODE>
|
|
<P>
|
|
<P>This will disconnect you from the cluster
|
|
<P>
|
|
<H2><A NAME="ss9.14">9.14 catchup (5)</A>
|
|
</H2>
|
|
|
|
<P><CODE><B>catchup <node_call> All|[<msgno> ...]</B> Mark a message as sent</CODE>
|
|
<P>
|
|
<P>When you send messages the fact that you have forwarded it to another node
|
|
is remembered so that it isn't sent again. When you have a new partner
|
|
node and you add their callsign to your /spider/msg/forward.pl file, all
|
|
outstanding non-private messages will be forwarded to them. This may well
|
|
be ALL the non-private messages. You can prevent this by using these
|
|
commmands:-
|
|
<P>
|
|
<BLOCKQUOTE><CODE>
|
|
<PRE>
|
|
catchup GB7DJK all
|
|
catchup GB7DJK 300 301 302 303 500-510
|
|
</PRE>
|
|
</CODE></BLOCKQUOTE>
|
|
<P>and to undo what you have just done:-
|
|
<P>
|
|
<BLOCKQUOTE><CODE>
|
|
<PRE>
|
|
uncatchup GB7DJK all
|
|
uncatchup GB7DJK 300 301 302 303 500-510
|
|
</PRE>
|
|
</CODE></BLOCKQUOTE>
|
|
<P>which will arrange for them to be forward candidates again.
|
|
<P>Order is not important.
|
|
<P>
|
|
<H2><A NAME="ss9.15">9.15 clear/spots (0)</A>
|
|
</H2>
|
|
|
|
<P><CODE><B>clear/spots [1|all]</B> Clear a spot filter line</CODE>
|
|
<P>
|
|
<P>This command allows you to clear (remove) a line in a spot filter or to
|
|
remove the whole filter.
|
|
<P>If you have a filter:-
|
|
<P>
|
|
<BLOCKQUOTE><CODE>
|
|
<PRE>
|
|
acc/spot 1 on hf/cw
|
|
acc/spot 2 on vhf and (by_zone 14,15,16 or call_zone 14,15,16)
|
|
</PRE>
|
|
</CODE></BLOCKQUOTE>
|
|
<P>and you say:-
|
|
<P>
|
|
<BLOCKQUOTE><CODE>
|
|
<PRE>
|
|
clear/spot 1
|
|
</PRE>
|
|
</CODE></BLOCKQUOTE>
|
|
<P>you will be left with:-
|
|
<P>
|
|
<BLOCKQUOTE><CODE>
|
|
<PRE>
|
|
acc/spot 2 on vhf and (by_zone 14,15,16 or call_zone 14,15,16)
|
|
</PRE>
|
|
</CODE></BLOCKQUOTE>
|
|
<P>If you do:
|
|
<P>
|
|
<BLOCKQUOTE><CODE>
|
|
<PRE>
|
|
clear/spot all
|
|
</PRE>
|
|
</CODE></BLOCKQUOTE>
|
|
<P>the filter will be completely removed.
|
|
<P>
|
|
<P>
|
|
<H2><A NAME="ss9.16">9.16 connect (5) </A>
|
|
</H2>
|
|
|
|
<P><CODE><B>connect <callsign></B> Start a connection to another DX Cluster</CODE>
|
|
<P>
|
|
<P>Start a connection process that will culminate in a new connection to the
|
|
DX cluster <callsign>. This process creates a new 'client' process which will
|
|
use the script in /spider/connect/<callsign> to effect the 'chat' exchange
|
|
necessary to traverse the network(s) to logon to the cluster <callsign>.
|
|
<P>
|
|
<H2><A NAME="ss9.17">9.17 dbavail (0)</A>
|
|
</H2>
|
|
|
|
<P><CODE><B>dbavail</B> Show a list of all the databases in the system</CODE>
|
|
<P>
|
|
<P>The title says it all really, this command lists all the databases defined
|
|
in the system. It is also aliased to SHOW/COMMAND.
|
|
<P>
|
|
<H2><A NAME="ss9.18">9.18 dbcreate (9)</A>
|
|
</H2>
|
|
|
|
<P><CODE><B>dbcreate <name></B> Create a database entry<BR>
|
|
<B>dbcreate <name> chain <name> [<name>..]</B> Create a chained database entry<BR>
|
|
<B>dbcreate <name> remote <node></B> Create a remote database
|
|
entry<BR></CODE>
|
|
<P>
|
|
<P>DBCREATE allows you to define a database in the system. It doesn't actually
|
|
create anything, just defines it.
|
|
<P>The databases that are created are simple DB_File hash databases, they are
|
|
therefore already 'indexed'.
|
|
<P>You can define a local database with the first form of the command eg:
|
|
<P>DBCREATE oblast
|
|
<P>You can also chain databases with the addition of the 'chain' keyword.
|
|
This will search each database one after the other. A typical example
|
|
is:
|
|
<P>DBCREATE sdx_qsl chain sql_ad
|
|
<P>No checking is done to see if the any of the chained databases exist, in
|
|
fact it is usually better to do the above statement first then do each of
|
|
the chained databases.
|
|
<P>Databases can exist offsite. To define a database that lives on another
|
|
node do:
|
|
<P>DBCREATE buckmaster remote gb7dxc
|
|
<P>Remote databases cannot be chained; however, the last database in a
|
|
a chain can be a remote database eg:
|
|
<P>DBCREATE qsl chain gb7dxc
|
|
<P>To see what databases have been defined do:
|
|
<P>DBAVAIL (or it will have been aliased to SHOW/COMMAND)
|
|
<P>It would be normal for you to add an entry into your local Aliases file
|
|
to allow people to use the 'SHOW/<dbname>' style syntax. So you would
|
|
need to add a line like:-
|
|
<P>
|
|
<BLOCKQUOTE><CODE>
|
|
<PRE>
|
|
's' => [
|
|
..
|
|
..
|
|
'^sh\w*/buc', 'dbshow buckmaster', 'dbshow',
|
|
..
|
|
..
|
|
],
|
|
</PRE>
|
|
</CODE></BLOCKQUOTE>
|
|
<P>to allow
|
|
<P>SH/BUCK g1tlh
|
|
<P>to work as they may be used to.
|
|
<P>See DBIMPORT for the importing of existing AK1A format data to databases.
|
|
See DBSHOW for generic database enquiry
|
|
<P>
|
|
<H2><A NAME="ss9.19">9.19 dbimport (9)</A>
|
|
</H2>
|
|
|
|
<P><CODE><B>dbimport <dbname></B> Import AK1A data into a database</CODE>
|
|
<P>
|
|
<P>If you want to import or update data in bulk to a database you can use
|
|
this command. It will either create or update entries into an existing
|
|
database. For example:-
|
|
<P>DBIMPORT oblast /tmp/OBLAST.FUL
|
|
<P>will import the standard OBLAST database that comes with AK1A into the
|
|
oblast database held locally.
|
|
<P>
|
|
<H2><A NAME="ss9.20">9.20 dbremove (9)</A>
|
|
</H2>
|
|
|
|
<P><CODE><B>dbremove <dbname></B> Delete a database</CODE>
|
|
<P>
|
|
<P>DBREMOVE will completely remove a database entry and also delete any data
|
|
file that is associated with it.
|
|
<P>There is no warning, no comeback, no safety net.
|
|
<P>For example:
|
|
<P>DBREMOVE oblast
|
|
<P>will remove the oblast database from the system and it will also remove
|
|
the associated datafile.
|
|
<P>I repeat:
|
|
<P>There is no warning, no comeback, no safety net.
|
|
<P>You have been warned.
|
|
<P>
|
|
<H2><A NAME="ss9.21">9.21 dbshow (0)</A>
|
|
</H2>
|
|
|
|
<P><CODE><B>dbshow <dbname> <key></B> Display an entry, if it exists, in a database</CODE>
|
|
<P>
|
|
<P>This is the generic user interface to the database to the database system.
|
|
It is expected that the sysop will add an entry to the local Aliases file
|
|
so that users can use the more familiar AK1A style of enquiry such as:
|
|
<P>
|
|
<BLOCKQUOTE><CODE>
|
|
<PRE>
|
|
SH/BUCK G1TLH
|
|
</PRE>
|
|
</CODE></BLOCKQUOTE>
|
|
<P>but if he hasn't and the database really does exist (use DBAVAIL or
|
|
SHOW/COMMAND to find out) you can do the same thing with:
|
|
<P>
|
|
<BLOCKQUOTE><CODE>
|
|
<PRE>
|
|
DBSHOW buck G1TLH
|
|
</PRE>
|
|
</CODE></BLOCKQUOTE>
|
|
<P>
|
|
<P>
|
|
<H2><A NAME="ss9.22">9.22 debug (9)</A>
|
|
</H2>
|
|
|
|
<P><CODE><B>debug</B> Set the cluster program into debug mode</CODE>
|
|
<P>
|
|
<P>Executing this command will only have an effect if you are running the cluster
|
|
in debug mode i.e.
|
|
<P>
|
|
<BLOCKQUOTE><CODE>
|
|
<PRE>
|
|
perl -d cluster.pl
|
|
</PRE>
|
|
</CODE></BLOCKQUOTE>
|
|
<P>It will interrupt the cluster just after the debug command has finished.
|
|
<P>
|
|
<H2><A NAME="ss9.23">9.23 directory (0)</A>
|
|
</H2>
|
|
|
|
<P><CODE><B>directory</B> List messages<BR> <B>directory all</B> List all messages<BR>
|
|
<B>directory own</B> List your own messages<BR>
|
|
<B>directory new</B> List all new messages<BR>
|
|
<B>directory to <call></B> List all messages to <call><BR>
|
|
<B>directory from <call></B> List all messages from <call><BR>
|
|
<B>directory subject <string></B> List all messages with <string> in subject<BR>
|
|
<B>directory <nn></B> List last <nn> messages<BR>
|
|
<B>directory <from>-<to></B> List messages <from> message <to> message <BR></CODE>
|
|
<P>
|
|
<P>List the messages in the messages directory.
|
|
<P>If there is a 'p' one space after the message number then it is a
|
|
personal message. If there is a '-' between the message number and the
|
|
'p' then this indicates that the message has been read.
|
|
<P>You can use shell escape characters such as '*' and '?' in the <call>
|
|
fields.
|
|
<P>You can combine some of the various directory commands together eg:-
|
|
<P>
|
|
<BLOCKQUOTE><CODE>
|
|
<PRE>
|
|
DIR TO G1TLH 5
|
|
or
|
|
DIR SUBJECT IOTA 200-250
|
|
</PRE>
|
|
</CODE></BLOCKQUOTE>
|
|
<P>You can abbreviate all the commands to one letter and use ak1a syntax:-
|
|
<P>
|
|
<BLOCKQUOTE><CODE>
|
|
<PRE>
|
|
DIR/T G1* 10
|
|
DIR/S QSL 10-100 5
|
|
</PRE>
|
|
</CODE></BLOCKQUOTE>
|
|
<P>
|
|
<P>
|
|
<H2><A NAME="ss9.24">9.24 directory (extended for sysops) (5)</A>
|
|
</H2>
|
|
|
|
<P>Works just like the user command except that sysops can see ALL messages.
|
|
<P>
|
|
<H2><A NAME="ss9.25">9.25 disconnect (8)</A>
|
|
</H2>
|
|
|
|
<P><CODE><B>disconnect <call> [<call> ...]</B> Disconnect a user or node</CODE>
|
|
<P>
|
|
<P>Disconnect any <call> connected locally
|
|
<P>
|
|
<H2><A NAME="ss9.26">9.26 dx (0)</A>
|
|
</H2>
|
|
|
|
<P><CODE><B>dx [by <call>] <freq> <call> <remarks></B> Send a DX spot</CODE>
|
|
<P>
|
|
<P>This is how you send a DX Spot to other users. You can, in fact, now
|
|
enter the <freq> and the <call> either way round.
|
|
<P>
|
|
<BLOCKQUOTE><CODE>
|
|
<PRE>
|
|
DX FR0G 144.600
|
|
DX 144.600 FR0G
|
|
DX 144600 FR0G
|
|
</PRE>
|
|
</CODE></BLOCKQUOTE>
|
|
<P>will all give the same result. You can add some remarks to the end
|
|
of the command and they will be added to the spot.
|
|
<P>
|
|
<BLOCKQUOTE><CODE>
|
|
<PRE>
|
|
DX FR0G 144600 this is a test
|
|
</PRE>
|
|
</CODE></BLOCKQUOTE>
|
|
<P>You can credit someone else by saying:-
|
|
<P>
|
|
<BLOCKQUOTE><CODE>
|
|
<PRE>
|
|
DX by G1TLH FR0G 144.600 he isn't on the cluster
|
|
</PRE>
|
|
</CODE></BLOCKQUOTE>
|
|
<P>The <freq> is compared against the available bands set up in the
|
|
cluster. See SHOW/BANDS for more information.
|
|
<P>
|
|
<H2><A NAME="ss9.27">9.27 export (9)</A>
|
|
</H2>
|
|
|
|
<P><CODE><B>export <msgno> <filename></B> Export a message to a file</CODE>
|
|
<P>
|
|
<P>Export a message to a file. This command can only be executed on a local
|
|
console with a fully privileged user. The file produced will be in a form
|
|
ready to be imported back into the cluster by placing it in the import
|
|
directory (/spider/msg/import).
|
|
<P>This command cannot overwrite an existing file. This is to provide some
|
|
measure of security. Any files written will owned by the same user as the
|
|
main cluster, otherwise you can put the new files anywhere the cluster can
|
|
access. For example:-
|
|
<P>EXPORT 2345 /tmp/a
|
|
<P>
|
|
<H2><A NAME="ss9.28">9.28 export_users (9)</A>
|
|
</H2>
|
|
|
|
<P><CODE><B>export_users [<filename>]</B> Export the users database to ascii</CODE>
|
|
<P>
|
|
<P>Export the users database to a file in ascii format. If no filename
|
|
is given then it will export the file to /spider/data/user_asc.
|
|
<P>If the file already exists it will be renamed to <filename>.o. In fact
|
|
up to 5 generations of the file can be kept each one with an extra 'o' on the
|
|
suffix.
|
|
<P>BE WARNED: this will write to any file you have write access to. No check is
|
|
made on the filename (if any) that you specify.
|
|
<P>
|
|
<H2><A NAME="ss9.29">9.29 forward/latlong (8)</A>
|
|
</H2>
|
|
|
|
<P><CODE><B>forward/latlong <node_call></B> Send latitude and longitude information to another cluster</CODE>
|
|
<P>
|
|
<P>This command sends all the latitude and longitude information that your
|
|
cluster is holding against callsigns. One advantage of recieving this
|
|
information is that more locator information is held by you. This
|
|
means that more locators are given on the DX line assuming you have
|
|
<EM>set/dxgrid</EM> enabled. This could be a LOT of information though, so
|
|
it is not recommended on slow links.
|
|
<P>
|
|
<H2><A NAME="ss9.30">9.30 forward/opername (1)</A>
|
|
</H2>
|
|
|
|
<P><CODE><B>forward/opername <call></B> Send out information on this <call> to all clusters</CODE>
|
|
<P>
|
|
<P>This command sends out any information held in the user file which can
|
|
be broadcast in PC41 protocol packets. This information is Name, QTH, Location
|
|
and Homenode. PC41s are only sent for the information that is available.
|
|
<P>
|
|
<H2><A NAME="ss9.31">9.31 help (0)</A>
|
|
</H2>
|
|
|
|
<P><CODE><B>help <cmd></B> Get help on a command</CODE>
|
|
<P>
|
|
<P>All commands can be abbreviated, so SHOW/DX can be abbreviated
|
|
to SH/DX, ANNOUNCE can be shortened to AN and so on.
|
|
<P>Look at the APROPOS <string> command which will search the help database
|
|
for the <string> you specify and give you a list of likely commands
|
|
to look at with HELP.
|
|
<P>
|
|
<H2><A NAME="ss9.32">9.32 init (5)</A>
|
|
</H2>
|
|
|
|
<P><CODE><B>init <node call></B> Re-initialise a link to an AK1A compatible node</CODE>
|
|
<P>
|
|
<P>This command attempts to re-initialise a link to a (usually) AK1A node
|
|
that has got confused, usually by a protocol loop of some kind. It may
|
|
work - but you usually will be better off simply disconnecting it (or
|
|
better, if it is a real AK1A node, doing an RCMD <node> DISC/F <your
|
|
node>).
|
|
<P>Best of luck - you will need it.
|
|
<P>
|
|
<H2><A NAME="ss9.33">9.33 kill (0)</A>
|
|
</H2>
|
|
|
|
<P><CODE><B>kill <msgno> [<msgno> ..]</B> Delete a message from the local system</CODE>
|
|
<P>
|
|
<P>Delete a message from the local system. You will only be able to
|
|
delete messages that you have originated or been sent (unless you are
|
|
the sysop).
|
|
<P>
|
|
<H2><A NAME="ss9.34">9.34 kill (5)</A>
|
|
</H2>
|
|
|
|
<P><CODE><B>kill <msgno> [<msgno> ...]</B> Remove or erase a message from the system<BR>
|
|
<B>kill from <call></B> Remove all messages from a callsign<BR>
|
|
<B>kill to <call></B> Remove all messages to a callsign<BR></CODE>
|
|
<P>
|
|
<P>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.
|
|
<P>As a sysop you can kill any message on the system.
|
|
<P>
|
|
<H2><A NAME="ss9.35">9.35 kill full (5)</A>
|
|
</H2>
|
|
|
|
<P><CODE><B>kill full <msgno> [<msgno>]</B> Delete a message from the whole cluster</CODE>
|
|
<P>
|
|
<P>Delete a message (usually a 'bulletin') from the whole cluster system.
|
|
<P>This uses the subject field, so any messages that have exactly the same subject
|
|
will be deleted. Beware!
|
|
<P>
|
|
<H2><A NAME="ss9.36">9.36 links (0)</A>
|
|
</H2>
|
|
|
|
<P><CODE><B>links</B> Show which nodes are physically connected</CODE>
|
|
<P>
|
|
<P>This is a quick listing that shows which links are connected and
|
|
some information about them. See WHO for a list of all connections.
|
|
<P>
|
|
<P>
|
|
<H2><A NAME="ss9.37">9.37 load/aliases (9)</A>
|
|
</H2>
|
|
|
|
<P><CODE><B>load/aliases</B> Reload the command alias table</CODE>
|
|
<P>
|
|
<P>Reload the /spider/cmd/Aliases file after you have editted it. You will need to
|
|
do this if you change this file whilst the cluster is running in order for the
|
|
changes to take effect.
|
|
<P>
|
|
<P>
|
|
<H2><A NAME="ss9.38">9.38 load/baddx (9)</A>
|
|
</H2>
|
|
|
|
<P><CODE><B>load/baddx</B> Reload the bad DX table</CODE>
|
|
<P>
|
|
<P>Reload the /spider/data/baddx.pl file if you have changed it manually whilst
|
|
the cluster is running. This table contains the DX Calls that, if spotted,
|
|
will not be passed on. FR0G and TEST are classic examples.
|
|
<P>
|
|
<H2><A NAME="ss9.39">9.39 load/badmsg (9)</A>
|
|
</H2>
|
|
|
|
<P><CODE><B>load/badmsg</B> Reload the bad message table</CODE>
|
|
<P>
|
|
<P>Reload the /spider/msg/badmsg.pl file if you have changed it manually whilst
|
|
the cluster is running. This table contains a number of perl regular
|
|
expressions which are searched for in the fields targetted of each message.
|
|
If any of them match then that message is immediately deleted on receipt.
|
|
<P>
|
|
<H2><A NAME="ss9.40">9.40 load/badwords (9)</A>
|
|
</H2>
|
|
|
|
<P><CODE><B>load/badwords</B> Reload the badwords file</CODE>
|
|
<P>
|
|
<P>Reload the /spider/data/badwords file if you have changed it manually whilst
|
|
the cluster is running. This file contains a list of words which, if found
|
|
on certain text portions of PC protocol, will cause those protocol frames
|
|
to be rejected. It will all put out a message if any of these words are
|
|
used on the announce, dx and talk commands. The words can be one or
|
|
more on a line, lines starting with '#' are ignored.
|
|
<P>
|
|
<H2><A NAME="ss9.41">9.41 load/bands (9)</A>
|
|
</H2>
|
|
|
|
<P><CODE><B>load/bands</B> Reload the band limits table</CODE>
|
|
<P>
|
|
<P>Reload the /spider/data/bands.pl file if you have changed it manually whilst
|
|
the cluster is running.
|
|
<P>
|
|
<H2><A NAME="ss9.42">9.42 load/cmd_cache (9)</A>
|
|
</H2>
|
|
|
|
<P><CODE><B>load/cmd_cache</B> Reload the automatic command cache</CODE>
|
|
<P>
|
|
<P>Normally, if you change a command file in the cmd or local_cmd tree it will
|
|
automatially be picked up by the cluster program. Sometimes it can get confused
|
|
if you are doing a lot of moving commands about or delete a command in the
|
|
local_cmd tree and want to use the normal one again. Execute this command to
|
|
reset everything back to the state it was just after a cluster restart.
|
|
<P>
|
|
<H2><A NAME="ss9.43">9.43 load/forward (9)</A>
|
|
</H2>
|
|
|
|
<P><CODE><B>load/forward</B> Reload the msg forwarding routing table</CODE>
|
|
<P>Reload the /spider/msg/forward.pl file if you have changed it
|
|
manually whilst the cluster is running.
|
|
<P>
|
|
<H2><A NAME="ss9.44">9.44 load/messages (9)</A>
|
|
</H2>
|
|
|
|
<P><CODE><B>load/messages</B> Reload the system messages file</CODE>
|
|
<P>
|
|
<P>If you change the /spider/perl/Messages file (usually whilst fiddling/writing ne
|
|
commands) you can have them take effect during a cluster session by executing this
|
|
command. You need to do this if get something like :-
|
|
<P>unknown message 'xxxx' in lang 'en'
|
|
<P>
|
|
<H2><A NAME="ss9.45">9.45 load/prefixes (9)</A>
|
|
</H2>
|
|
|
|
<P><CODE><B>load/prefixes</B> Reload the prefix table</CODE>
|
|
<P>
|
|
<P>Reload the /spider/data/prefix_data.pl file if you have changed it manually
|
|
whilst the cluster is running.
|
|
<P>
|
|
<H2><A NAME="ss9.46">9.46 merge (5)</A>
|
|
</H2>
|
|
|
|
<P><CODE><B>merge <node> [<no spots>/<no wwv>]</B> Ask for the latest spots and WWV</CODE>
|
|
<P>
|
|
<P>MERGE allows you to bring your spot and wwv database up to date. By default
|
|
it will request the last 10 spots and 5 WWVs from the node you select. The
|
|
node must be connected locally.
|
|
<P>You can request any number of spots or wwv and although they will be appended
|
|
to your databases they will not duplicate any that have recently been added
|
|
(the last 2 days for spots and last month for WWV data).
|
|
<P>
|
|
<H2><A NAME="ss9.47">9.47 msg (9)</A>
|
|
</H2>
|
|
|
|
<P><CODE><B>msg <cmd> <msgno> [data ...]</B> Alter various message parameters</CODE>
|
|
<P>
|
|
<P>Alter message parameters like To, From, Subject, whether private or bulletin
|
|
or return receipt (RR) is required or whether to keep this message from timing
|
|
out.
|
|
<P>
|
|
<BLOCKQUOTE><CODE>
|
|
<PRE>
|
|
MSG TO <msgno> <call> - change TO callsign to <call>
|
|
MSG FRom <msgno> <call> - change FROM callsign to <call>
|
|
MSG PRrivate <msgno> - set private flag
|
|
MSG NOPRrivate <msgno> - unset private flag
|
|
MSG RR <msgno> - set RR flag
|
|
MSG NORR <msgno> - unset RR flag
|
|
MSG KEep <msgno> - set the keep flag (message won't be deleted ever)
|
|
MSG NOKEep <msgno> - unset the keep flag
|
|
MSG SUbject <msgno> <new> - change the subject to <new>
|
|
MSG WAittime <msgno> - remove any waitting time for this message
|
|
MSG NOREad <msgno> - mark message as unread
|
|
MSG REad <msgno> - mark message as read
|
|
MSG QUeue - queue any outstanding bulletins
|
|
MSG QUeue 1 - queue any outstanding private messages
|
|
</PRE>
|
|
</CODE></BLOCKQUOTE>
|
|
<P>You can look at the status of a message by using:-
|
|
<P>STAT/MSG <msgno>
|
|
<P>This will display more information on the message than DIR does.
|
|
<P>
|
|
<H2><A NAME="ss9.48">9.48 pc (8)</A>
|
|
</H2>
|
|
|
|
<P><CODE><B>pc <call> <text></B> Send text (eg PC Protocol) to <call></CODE>
|
|
<P>
|
|
<P>Send some arbitrary text to a locally connected callsign. No processing is done on
|
|
the text. This command allows you to send PC Protocol to unstick things if problems
|
|
arise (messages get stuck etc). eg:-
|
|
<P>pc gb7djk PC33^GB7TLH^GB7DJK^400^
|
|
<P>You can also use in the same way as a talk command to a connected user but
|
|
without any processing, added of "from <blah> to <blah>" or whatever.
|
|
<P>pc G1TLH Try doing that properly!!!
|
|
<P>
|
|
<H2><A NAME="ss9.49">9.49 ping (1)</A>
|
|
</H2>
|
|
|
|
<P><CODE><B>ping <node></B> Check the link quality between nodes</CODE>
|
|
<P>
|
|
<P>his command allows you to send a frame to another cluster node on
|
|
the network and get a return frame. The time it takes to do this
|
|
is a good indication of the quality of the link. The actual time
|
|
it takes is output to the console in seconds.
|
|
Any visible cluster node can be PINGed.
|
|
<P>
|
|
<P>
|
|
<H2><A NAME="ss9.50">9.50 rcmd (1)</A>
|
|
</H2>
|
|
|
|
<P><CODE><B>rcmd <node call> <cmd></B> Send a command to another DX cluster</CODE>
|
|
<P>
|
|
<P>This command allows you to send nearly any command to another DX Cluster
|
|
node that is connected to the system.
|
|
<P>Whether you get any output is dependant on a) whether the other system knows
|
|
that the node callsign of this cluster is in fact a node b) whether the
|
|
other system is allowing RCMDs from this node and c) whether you have
|
|
permission to send this command at all.
|
|
<P>
|
|
<H2><A NAME="ss9.51">9.51 read (0)</A>
|
|
</H2>
|
|
|
|
<P><CODE><B>read</B> Read the next unread personal message addressed to you<BR>
|
|
<B>read <msgno></B> Read the specified message<BR></CODE>
|
|
<P>
|
|
<P>You can read any messages that are sent as 'non-personal' and also any
|
|
message either sent by or sent to your callsign.
|
|
<P>
|
|
<P>
|
|
<H2><A NAME="ss9.52">9.52 read (extended for sysops) (5) </A>
|
|
</H2>
|
|
|
|
<P><CODE><B>read <msgno></B> Read a message on the system</CODE>
|
|
<P>
|
|
<P>As a sysop you may read any message on the system
|
|
<P>
|
|
<H2><A NAME="ss9.53">9.53 reject/announce</A>
|
|
</H2>
|
|
|
|
<P><CODE><B>reject/announce [0-9] <pattern></B> Set a reject filter
|
|
for announce</CODE>
|
|
<P>
|
|
<P>Create an 'reject this announce' line for a filter.
|
|
<P>An reject filter line means that if the announce matches this filter it is
|
|
passed onto the user. See HELP FILTERS for more info. Please read this
|
|
to understand how filters work - it will save a lot of grief later on.
|
|
<P>You can use any of the following things in this line:-
|
|
<P>
|
|
<BLOCKQUOTE><CODE>
|
|
<PRE>
|
|
info <string> eg: iota or qsl
|
|
by <prefixes> eg: G,M,2
|
|
origin <prefixes>
|
|
origin_dxcc <numbers> eg: 61,62 (from eg: sh/pre G)
|
|
origin_itu <numbers>
|
|
origin_zone <numbers>
|
|
by_dxcc <numbers>
|
|
by_itu <numbers>
|
|
by_zone <numbers>
|
|
channel <prefixes>
|
|
wx 1 filter WX announces
|
|
dest <prefixes> eg: 6MUK,WDX (distros)
|
|
</PRE>
|
|
</CODE></BLOCKQUOTE>
|
|
<P>some examples:-
|
|
<P>
|
|
<BLOCKQUOTE><CODE>
|
|
<PRE>
|
|
rej/ann by_zone 14,15,16 and not by G,M,2
|
|
</PRE>
|
|
</CODE></BLOCKQUOTE>
|
|
<P>You can use the tag 'all' to reject everything eg:
|
|
<P>
|
|
<BLOCKQUOTE><CODE>
|
|
<PRE>
|
|
rej/ann all
|
|
</PRE>
|
|
</CODE></BLOCKQUOTE>
|
|
<P>but this probably for advanced users...
|
|
<P>
|
|
<H2><A NAME="ss9.54">9.54 reject/announce (extended for sysops) (8)</A>
|
|
</H2>
|
|
|
|
<P><CODE><B>reject/announce <call> [input] [0-9] <pattern></B> Announce filter sysop version</CODE>
|
|
<P>
|
|
<P>This version allows a sysop to set a filter for a callsign as well as the
|
|
default for nodes and users eg:-
|
|
<P>
|
|
<BLOCKQUOTE><CODE>
|
|
<PRE>
|
|
reject/ann by G,M,2
|
|
reject/ann input node_default by G,M,2
|
|
reject/ann user_default by G,M,2
|
|
</PRE>
|
|
</CODE></BLOCKQUOTE>
|
|
<P>
|
|
<H2><A NAME="ss9.55">9.55 reject/spots (0)</A>
|
|
</H2>
|
|
|
|
<P><CODE><B>reject/spots [0-9] <pattern></B> Set a reject filter line for spots</CODE>
|
|
<P>
|
|
<P>Create a 'reject this spot' line for a filter.
|
|
<P>A reject filter line means that if the spot matches this filter it is
|
|
dumped (not passed on). See HELP FILTERS for more info. Please read this
|
|
to understand how filters work - it will save a lot of grief later on.
|
|
<P>You can use any of the following things in this line:-
|
|
<P>
|
|
<BLOCKQUOTE><CODE>
|
|
<PRE>
|
|
freq <range> eg: 0/30000 or hf or hf/cw or 6m,4m,2m
|
|
on <range> same as 'freq'
|
|
call <prefixes> eg: G,PA,HB9
|
|
info <string> eg: iota or qsl
|
|
by <prefixes>
|
|
call_dxcc <numbers> eg: 61,62 (from eg: sh/pre G)
|
|
call_itu <numbers>
|
|
call_zone <numbers>
|
|
by_dxcc <numbers>
|
|
by_itu <numbers>
|
|
by_zone <numbers>
|
|
origin <prefixes>
|
|
channel <prefixes>
|
|
</PRE>
|
|
</CODE></BLOCKQUOTE>
|
|
<P>For frequencies, you can use any of the band names defined in
|
|
SHOW/BANDS and you can use a subband name like: cw, rtty, data, ssb -
|
|
thus: hf/ssb. You can also just have a simple range like: 0/30000 -
|
|
this is more efficient than saying simply: on HF (but don't get
|
|
too hung up about that)
|
|
<P>some examples:-
|
|
<P>
|
|
<BLOCKQUOTE><CODE>
|
|
<PRE>
|
|
rej/spot 1 on hf
|
|
rej/spot 2 on vhf and not (by_zone 14,15,16 or call_zone 14,15,16)
|
|
</PRE>
|
|
</CODE></BLOCKQUOTE>
|
|
<P>You can use the tag 'all' to reject everything eg:
|
|
<P>
|
|
<BLOCKQUOTE><CODE>
|
|
<PRE>
|
|
rej/spot 3 all
|
|
</PRE>
|
|
</CODE></BLOCKQUOTE>
|
|
<P>but this probably for advanced users...
|
|
<P>
|
|
<H2><A NAME="ss9.56">9.56 reject/spots (extended for sysops) (8)</A>
|
|
</H2>
|
|
|
|
<P><CODE><B>reject/spots <call> [input] [0-9] <pattern></B>
|
|
Reject spot filter sysop version </CODE>
|
|
<P>
|
|
<P>This version allows a sysop to set a filter for a callsign as well as the
|
|
default for nodes and users eg:-
|
|
<P>
|
|
<BLOCKQUOTE><CODE>
|
|
<PRE>
|
|
reject/spot db0sue-7 1 by_zone 14,15,16
|
|
reject/spot node_default all
|
|
set/hops node_default 10
|
|
|
|
reject/spot user_default by G,M,2
|
|
</PRE>
|
|
</CODE></BLOCKQUOTE>
|
|
<P>
|
|
<H2><A NAME="ss9.57">9.57 reject/wcy (0)</A>
|
|
</H2>
|
|
|
|
<P><CODE><B>reject/wcy [0-9] <pattern></B> Set a reject WCY filter</CODE>
|
|
<P>
|
|
<P>It is unlikely that you will want to do this, but if you do then you can
|
|
filter on the following fields:-
|
|
<P>
|
|
<BLOCKQUOTE><CODE>
|
|
<PRE>
|
|
by <prefixes> eg: G,M,2
|
|
origin <prefixes>
|
|
origin_dxcc <numbers> eg: 61,62 (from eg: sh/pre G)
|
|
origin_itu <numbers>
|
|
origin_zone <numbers>
|
|
by_dxcc <numbers>
|
|
by_itu <numbers>
|
|
by_zone <numbers>
|
|
channel <prefixes>
|
|
</PRE>
|
|
</CODE></BLOCKQUOTE>
|
|
<P>There are no examples because WCY Broadcasts only come from one place and
|
|
you either want them or not (see UNSET/WCY if you don't want them).
|
|
<P>This command is really provided for future use.
|
|
<P>See HELP FILTER for information.
|
|
<P>
|
|
<H2><A NAME="ss9.58">9.58 reject/wcy (extended for sysops) (8)</A>
|
|
</H2>
|
|
|
|
<P><CODE><B>reject/wcy <call> [input] [0-9] <pattern></B>
|
|
WCY reject filter sysop version</CODE>
|
|
<P>
|
|
<P>This version allows a sysop to set a filter for a callsign as well as the
|
|
default for nodes and users eg:-
|
|
<P>reject/wcy gb7djk all
|
|
<P>
|
|
<H2><A NAME="ss9.59">9.59 reject/wwv (0)</A>
|
|
</H2>
|
|
|
|
<P><CODE><B>reject/wwv [0-9] <pattern></B> Set a reject WWV filter</CODE>
|
|
<P>
|
|
<P>It is unlikely that you will want to do this, but if you do then you can
|
|
filter on the following fields:-
|
|
<P>
|
|
<BLOCKQUOTE><CODE>
|
|
<PRE>
|
|
by <prefixes> eg: G,M,2
|
|
origin <prefixes>
|
|
origin_dxcc <numbers> eg: 61,62 (from eg: sh/pre G)
|
|
origin_itu <numbers>
|
|
origin_zone <numbers>
|
|
by_dxcc <numbers>
|
|
by_itu <numbers>
|
|
by_zone <numbers>
|
|
channel <prefixes>
|
|
</PRE>
|
|
</CODE></BLOCKQUOTE>
|
|
<P>for example
|
|
<P>
|
|
<BLOCKQUOTE><CODE>
|
|
<PRE>
|
|
reject/wwv by_zone 14,15,16
|
|
</PRE>
|
|
</CODE></BLOCKQUOTE>
|
|
<P>is probably the only useful thing to do (which will only show WWV broadcasts
|
|
by stations in the US).
|
|
<P>See HELP FILTER for information.
|
|
<P>
|
|
<H2><A NAME="ss9.60">9.60 reject/wwv (extended for sysops) (8)</A>
|
|
</H2>
|
|
|
|
<P><CODE><B>reject/wwv <call> [input] [0-9] <pattern></B>
|
|
WWV reject filter sysop version</CODE>
|
|
<P>
|
|
<P>This version allows a sysop to set a filter for a callsign as well as the
|
|
default for nodes and users eg:-
|
|
<P>
|
|
<BLOCKQUOTE><CODE>
|
|
<PRE>
|
|
reject/wwv db0sue-7 1 by_zone 4
|
|
reject/wwv node_default all
|
|
|
|
reject/wwv user_default by W
|
|
</PRE>
|
|
</CODE></BLOCKQUOTE>
|
|
<P>
|
|
<H2><A NAME="ss9.61">9.61 reply (0)</A>
|
|
</H2>
|
|
|
|
<P><CODE><B>reply</B> Reply (privately) to the last message that you have read<BR>
|
|
<B>reply <msgno></B> Reply (privately) to the specified message<BR>
|
|
<B>reply B <msgno></B> Reply as a Bulletin to the specified message<BR>
|
|
<B>reply NOPrivate <msgno></B> Reply as a Bulletin to the specified
|
|
message<BR>
|
|
<B>reply RR <msgno></B> Reply to the specified message with read receipt<BR></CODE>
|
|
<P>
|
|
<P>You can reply to a message and the subject will automatically have
|
|
"Re:" inserted in front of it, if it isn't already present.
|
|
<P>You can also use all the extra qualifiers such as RR, PRIVATE,
|
|
NOPRIVATE, B that you can use with the SEND command (see SEND
|
|
for further details)
|
|
<P>
|
|
<H2><A NAME="ss9.62">9.62 send (0)</A>
|
|
</H2>
|
|
|
|
<P><CODE><B>send <call> [<call> ...]</B> Send a message to one or more callsigns<BR>
|
|
<B>send RR <call></B> Send a message and ask for a read receipt<BR>
|
|
<B>send COPY <msgno> <call></B> Send a copy of a message to someone<BR>
|
|
<B>send PRIVATE <call></B> Send a personal message<BR>
|
|
<B>send NOPRIVATE <call></B> Send a message to all stations<BR></CODE>
|
|
<P>
|
|
<P>All the SEND commands will create a message which will be sent either to
|
|
an individual callsign or to one of the 'bulletin' addresses.
|
|
<P>SEND <call> on its own acts as though you had typed SEND PRIVATE, that is
|
|
it will mark the message as personal and send it to the cluster node that
|
|
that callsign is connected to.
|
|
<P>You can have more than one callsign in all of the SEND commands.
|
|
<P>You can have multiple qualifiers so that you can have for example:-
|
|
<P>
|
|
<BLOCKQUOTE><CODE>
|
|
<PRE>
|
|
SEND RR COPY 123 PRIVATE G1TLH G0RDI
|
|
</PRE>
|
|
</CODE></BLOCKQUOTE>
|
|
<P>which should send a copy of message 123 to G1TLH and G0RDI and you will
|
|
receive a read receipt when they have read the message.
|
|
<P>SB is an alias for SEND NOPRIVATE (or send a bulletin in BBS speak)
|
|
SP is an alias for SEND PRIVATE
|
|
<P>
|
|
<H2><A NAME="ss9.63">9.63 set/address (0)</A>
|
|
</H2>
|
|
|
|
<P><CODE><B>set/address <your_address></B> Record your postal address</CODE>
|
|
<P>
|
|
<P>Literally, record your address details on the cluster.
|
|
<P>
|
|
<H2><A NAME="ss9.64">9.64 set/announce (0)</A>
|
|
</H2>
|
|
|
|
<P><CODE><B>set/announce</B> Allow announce messages</CODE>
|
|
<P>
|
|
<P>Allow announce messages to arrive at your terminal.
|
|
<P>
|
|
<H2><A NAME="ss9.65">9.65 set/arcluster (5)</A>
|
|
</H2>
|
|
|
|
<P><CODE><B>set/arcluster <node_call> [<node_call> ...]</B> Make
|
|
the node_call an AR-Cluster type node</CODE>
|
|
<P>
|
|
<P>Set the node_call as an AR-Cluster type node
|
|
<P>
|
|
<H2><A NAME="ss9.66">9.66 set/baddx (8)</A>
|
|
</H2>
|
|
|
|
<P><CODE><B>set/baddx <call></B> Stop words we do not wish to see in the callsign field
|
|
of a dx spot being propagated</CODE>
|
|
<P>
|
|
<P>Setting a word as 'baddx' will prevent spots with that word in the callsign
|
|
field of a DX spot from going any further. They will not be displayed and they
|
|
will not be sent onto other nodes.
|
|
<P>The word must be wriiten in full, no wild cards are allowed eg:-
|
|
<P>
|
|
<BLOCKQUOTE><CODE>
|
|
<PRE>
|
|
set/baddx FORSALE VIDEO FR0G
|
|
</PRE>
|
|
</CODE></BLOCKQUOTE>
|
|
<P>To allow a word again, use the following command ...
|
|
<P>
|
|
<BLOCKQUOTE><CODE>
|
|
<PRE>
|
|
unset/baddx VIDEO
|
|
</PRE>
|
|
</CODE></BLOCKQUOTE>
|
|
<P>
|
|
<H2><A NAME="ss9.67">9.67 set/badnode (6)</A>
|
|
</H2>
|
|
|
|
<P><CODE><B>set/badnode <node_call></B> Stop spots from this node_call
|
|
being propagated</CODE>
|
|
<P>
|
|
<P>Setting a callsign as a 'badnode' will prevent spots from that node
|
|
going any further. They will not be displayed and they will not be
|
|
sent onto other nodes.
|
|
<P>The call can be a full or partial call (or a prefix), eg:-
|
|
<P>
|
|
<BLOCKQUOTE><CODE>
|
|
<PRE>
|
|
set/badnode K1TTT
|
|
</PRE>
|
|
</CODE></BLOCKQUOTE>
|
|
<P>will stop anything from K1TTT (including any SSID's)
|
|
<P>
|
|
<BLOCKQUOTE><CODE>
|
|
<PRE>
|
|
unset/badnode K1TTT
|
|
</PRE>
|
|
</CODE></BLOCKQUOTE>
|
|
<P>will allow spots from him again.
|
|
<P>Use with extreme care. This command may well be superceded by FILTERing.
|
|
<P>
|
|
<H2><A NAME="ss9.68">9.68 set/badspotter (8)</A>
|
|
</H2>
|
|
|
|
<P><CODE><B>set/badspotter <call></B> Stop spots from this callsign being propagated</CODE>
|
|
<P>
|
|
<P>Setting a callsign as a 'badspotter' will prevent spots from this callsign
|
|
going any further. They will not be displayed and they will not be
|
|
sent onto other nodes.
|
|
<P>The call must be written in full, no wild cards are allowed eg:-
|
|
<P>
|
|
<BLOCKQUOTE><CODE>
|
|
<PRE>
|
|
set/badspotter VE2STN
|
|
</PRE>
|
|
</CODE></BLOCKQUOTE>
|
|
<P>will stop anything from VE2STN. If you want SSIDs as well then you must
|
|
enter them specifically.
|
|
<P>
|
|
<BLOCKQUOTE><CODE>
|
|
<PRE>
|
|
unset/badspotter VE2STN
|
|
</PRE>
|
|
</CODE></BLOCKQUOTE>
|
|
<P>will allow spots from him again.
|
|
<P>Use with extreme care. This command may well be superceded by FILTERing.
|
|
<P>
|
|
<H2><A NAME="ss9.69">9.69 set/beep (0)</A>
|
|
</H2>
|
|
|
|
<P><CODE><B>set/beep</B> Add beeps to terminal messages</CODE>
|
|
<P>
|
|
<P>Add a beep to DX and other terminal messages.
|
|
<P>
|
|
<H2><A NAME="ss9.70">9.70 set/clx (5)</A>
|
|
</H2>
|
|
|
|
<P><CODE><B>set/clx <node_call> [<node_call> ...]</B> Make
|
|
the node_call a CLX type node</CODE>
|
|
<P>
|
|
<P>Set the node_call as a CLX type node
|
|
<P>
|
|
<H2><A NAME="ss9.71">9.71 set/debug (9)</A>
|
|
</H2>
|
|
|
|
<P><CODE><B>set/debug <name></B> Add a debug level to the debug set</CODE>
|
|
<P>
|
|
<P>You can choose to log several different levels. The levels are
|
|
<P>chan
|
|
state
|
|
msg
|
|
cron
|
|
connect
|
|
<P>You can show what levels you are logging with the <EM>show/debug</EM>
|
|
command.
|
|
<P>You can remove a debug level with unset/debug <name>
|
|
<P>
|
|
<H2><A NAME="ss9.72">9.72 set/dx (0)</A>
|
|
</H2>
|
|
|
|
<P><CODE><B>set/dx</B>Allow DX messages to arrive at your terminal</CODE>
|
|
<P>
|
|
<P>You can stop DX messages with the <EM>unset/dx</EM> command
|
|
<P>
|
|
<H2><A NAME="ss9.73">9.73 set/dxgrid (0)</A>
|
|
</H2>
|
|
|
|
<P><CODE><B>set/dxgrid</B>Allow grid squares on the end of DX messages</CODE>
|
|
<P>
|
|
<P>Some logging programs do not like the additional information at
|
|
the end of a DX spot. If this is the case, use the <EM>unset/dxgrid</EM>
|
|
command to remove the grid squares.
|
|
<P>
|
|
<H2><A NAME="ss9.74">9.74 set/dxnet (5)</A>
|
|
</H2>
|
|
|
|
<P><CODE><B>set/dxnet <node_call> [<node_call> ...]</B> Make
|
|
the node_call a DXNet type node</CODE>
|
|
<P>
|
|
<P>Set the node_call as a DXNet type node
|
|
<P>
|
|
<H2><A NAME="ss9.75">9.75 set/echo (0)</A>
|
|
</H2>
|
|
|
|
<P><CODE><B>set/echo</B> Make the cluster echo your input</CODE>
|
|
<P>
|
|
<P>If you are connected via a telnet session, different implimentations
|
|
of telnet handle echo differently depending on whether you are
|
|
connected via port 23 or some other port. You can use this command
|
|
to change the setting appropriately.
|
|
<P>You can remove the echo with the <EM>unset/echo</EM> command
|
|
<P>The setting is stored in your user profile.
|
|
<P>YOU DO NOT NEED TO USE THIS COMMAND IF YOU ARE CONNECTED VIA AX25.
|
|
<P>
|
|
<H2><A NAME="ss9.76">9.76 set/here (0)</A>
|
|
</H2>
|
|
|
|
<P><CODE><B>set/here</B> Set the here flag</CODE>
|
|
<P>
|
|
<P>Let others on the cluster know you are here by only displaying your
|
|
callsign. If you are away from your terminal you can use the <EM>unset/here</EM>
|
|
command to let people know you are away. This simply puts brackets
|
|
around your callsign to indicate you are not available.
|
|
<P>
|
|
<H2><A NAME="ss9.77">9.77 set/homenode (0)</A>
|
|
</H2>
|
|
|
|
<P><CODE><B>set/homenode <node_call></B> Set your home cluster</CODE>
|
|
<P>
|
|
<P>Tell the cluster system where you normally connect to. Any Messages sent
|
|
to you will normally find their way there should you not be connected.
|
|
eg:-
|
|
<P>
|
|
<BLOCKQUOTE><CODE>
|
|
<PRE>
|
|
SET/HOMENODE gb7djk
|
|
</PRE>
|
|
</CODE></BLOCKQUOTE>
|
|
<P>
|
|
<H2><A NAME="ss9.78">9.78 set/hops (8)</A>
|
|
</H2>
|
|
|
|
<P><CODE><B>set/hops <node_call> ann|spots|wwv|wcy <n></B>
|
|
Set hop count</CODE>
|
|
<P>
|
|
<P>Set the hop count for a particular type of broadcast for a node.
|
|
<P>This command allows you to set up special hop counts for a node
|
|
for currently: announce, spots, wwv and wcy broadcasts.
|
|
<P>
|
|
<BLOCKQUOTE><CODE>
|
|
<PRE>
|
|
eg:
|
|
set/hops gb7djk ann 10
|
|
set/hops gb7mbc spots 20
|
|
</PRE>
|
|
</CODE></BLOCKQUOTE>
|
|
<P>Set SHOW/HOPS for information on what is already set. This command
|
|
creates a filter and works in conjunction with the filter system.
|
|
<P>
|
|
<H2><A NAME="ss9.79">9.79 set/isolate (9)</A>
|
|
</H2>
|
|
|
|
<P><CODE><B>set/isolate <node call></B> Isolate a node from the rest of the network</CODE>
|
|
<P>
|
|
<P>Connect a node to your system in such a way that you are a full protocol
|
|
member of its network and can see all spots on it, but nothing either leaks
|
|
out from it nor goes back into from the rest of the nodes connected to you.
|
|
<P>You can potentially connect several nodes in this way.
|
|
<P>You can see which nodes are isolated with the show/isolate (1) command.
|
|
<P>You can remove the isolation with the command unset/isolate.
|
|
<P>
|
|
<H2><A NAME="ss9.80">9.80 set/language (0)</A>
|
|
</H2>
|
|
|
|
<P><CODE><B>set/language <language></B> Set the language you wish to use</CODE>
|
|
<P>
|
|
<P>You can select the language that you want the cluster to use. Currently
|
|
the languages available are <EM>en</EM> (English) and <EM>nl</EM> (Dutch).
|
|
<P>
|
|
<H2><A NAME="ss9.81">9.81 set/location (0)</A>
|
|
</H2>
|
|
|
|
<P><CODE><B>set/location <lat and long></B> Set your latitude and longitude</CODE>
|
|
<P>
|
|
<P>You can set your latitude and longitude manually or alternatively use the
|
|
<EM>set/qra</EM> command which will do the conversion for you.
|
|
<P>
|
|
<BLOCKQUOTE><CODE>
|
|
<PRE>
|
|
set/location 54 04 N 2 02 E
|
|
</PRE>
|
|
</CODE></BLOCKQUOTE>
|
|
<P>
|
|
<P>
|
|
<H2><A NAME="ss9.82">9.82 set/sys_location (9)</A>
|
|
</H2>
|
|
|
|
<P><CODE><B>set/sys_location <lat & long></B> Set your cluster latitude and longitude</CODE>
|
|
<P>
|
|
<P>In order to get accurate headings and such like you must tell the system
|
|
what your latitude and longitude is. If you have not yet done a SET/QRA
|
|
then this command will set your QRA locator for you. For example:-
|
|
<P>
|
|
<BLOCKQUOTE><CODE>
|
|
<PRE>
|
|
SET/LOCATION 52 22 N 0 57 E
|
|
</PRE>
|
|
</CODE></BLOCKQUOTE>
|
|
<P>
|
|
<H2><A NAME="ss9.83">9.83 set/logininfo (0)</A>
|
|
</H2>
|
|
|
|
<P><CODE><B>set/logininfo</B> Show logins and logouts of nodes and users</CODE>
|
|
<P>
|
|
<P>Show users and nodes when they log in and out of the local cluster. You
|
|
can stop these messages by using the <EM>unset/logininfo</EM> command.
|
|
<P>
|
|
<P>
|
|
<H2><A NAME="ss9.84">9.84 set/lockout (9)</A>
|
|
</H2>
|
|
|
|
<P><CODE><B>set/lockout <call></B> Stop a callsign connecting to the cluster</CODE>
|
|
<P>
|
|
<P>You can show who is locked out with the <EM>show/lockout</EM> command.
|
|
To allow the user to connect again, use the <EM>unset/lockout</EM> command.
|
|
<P>
|
|
<H2><A NAME="ss9.85">9.85 set/name (0)</A>
|
|
</H2>
|
|
|
|
<P><CODE><B>set/name <your_name></B> Set your name</CODE>
|
|
<P>
|
|
<P>Tell the cluster what your name is, eg:-
|
|
<P>
|
|
<BLOCKQUOTE><CODE>
|
|
<PRE>
|
|
set/name Dirk
|
|
</PRE>
|
|
</CODE></BLOCKQUOTE>
|
|
<P>
|
|
<H2><A NAME="ss9.86">9.86 set/node (9)</A>
|
|
</H2>
|
|
|
|
<P><CODE><B>set/node <call> [<call> ...]</B> Make the callsign an AK1A cluster</CODE>
|
|
<P>
|
|
<P>Tell the system that the call(s) are to be treated as AK1A cluster and
|
|
fed PC Protocol rather normal user commands.
|
|
<P>From version 1.41 you can also set the following types of cluster
|
|
<P>
|
|
<BLOCKQUOTE><CODE>
|
|
<PRE>
|
|
set/spider
|
|
set/dxnet
|
|
set/clx
|
|
set/arcluster
|
|
</PRE>
|
|
</CODE></BLOCKQUOTE>
|
|
<P>To see what your nodes are set to, use the <EM>show/nodes</EM> command.
|
|
<P>
|
|
<H2><A NAME="ss9.87">9.87 set/obscount (9)</A>
|
|
</H2>
|
|
|
|
<P><CODE><B>set/obscount <count> <node call></B> Set the 'pump-up' obsolescence counter</CODE>
|
|
<P>
|
|
<P>From version 1.35 onwards neighbouring nodes are pinged at regular intervals (see
|
|
SET/PINGINTERVAL), usually 300 seconds or 5 minutes. There is a 'pump-up'
|
|
counter which is decremented on every outgoing ping and then reset to
|
|
the 'obscount' value on every incoming ping. The default value of this
|
|
parameter is 2.
|
|
<P>What this means is that a neighbouring node will be pinged twice at
|
|
(default) 300 second intervals and if no reply has been heard just before
|
|
what would be the third attempt, that node is disconnected.
|
|
<P>If a ping is heard then the obscount is reset to the full value. Using
|
|
default values, if a node has not responded to a ping within 15 minutes,
|
|
it is disconnected.
|
|
<P>
|
|
<H2><A NAME="ss9.88">9.88 set/page (0)</A>
|
|
</H2>
|
|
|
|
<P><CODE><B>set/page <n></B> Set the number of lines per page</CODE>
|
|
<P>
|
|
<P>Tell the system how many lines you wish on a page when the number of lines
|
|
of output from a command is more than this. The default is 20. Setting it
|
|
explicitly to 0 will disable paging.
|
|
<P>
|
|
<BLOCKQUOTE><CODE>
|
|
<PRE>
|
|
SET/PAGE 30
|
|
SET/PAGE 0
|
|
</PRE>
|
|
</CODE></BLOCKQUOTE>
|
|
<P>The setting is stored in your user profile.
|
|
<P>
|
|
<P>
|
|
<H2><A NAME="ss9.89">9.89 set/password (9)</A>
|
|
</H2>
|
|
|
|
<P><CODE><B>set/password <callsign> <string></B> Set a users password</CODE>
|
|
<P>
|
|
<P>The password for a user can only be set by a full sysop. The string
|
|
can contain any characters but any spaces are removed (you can type in
|
|
spaces - but they won't appear in the password). You can see the
|
|
result with STAT/USER. The password is the usual 30 character baycom
|
|
type password.
|
|
<P>
|
|
<H2><A NAME="ss9.90">9.90 set/pinginterval (9)</A>
|
|
</H2>
|
|
|
|
<P><CODE><B>set/pinginterval <time> <node call></B> Set the ping time to neighbouring nodes</CODE>
|
|
<P>
|
|
<P>As from version 1.35 all neighbouring nodes are pinged at regular intervals
|
|
in order to determine the rolling quality of the link and, in future, to
|
|
affect routing decisions. The default interval is 300 secs or 5 minutes.
|
|
<P>You can use this command to set a different interval. Please don't.
|
|
<P>But if you do the value you enter is treated as minutes up 60 and seconds
|
|
for numbers greater than that.
|
|
<P>This is used also to help determine when a link is down at the far end
|
|
(as certain cluster software doesn't always notice), see SET/OBSCOUNT
|
|
for more information.
|
|
<P>
|
|
<H2><A NAME="ss9.91">9.91 set/privilege (9)</A>
|
|
</H2>
|
|
|
|
<P><CODE><B>set/privilege <n> <call> [<call> ...]</B> Set the privilege level on a call</CODE>
|
|
<P>
|
|
<P>Set the privilege level on a callsign. The privilege levels that pertain
|
|
to commands are as default:-
|
|
<P>
|
|
<BLOCKQUOTE><CODE>
|
|
<PRE>
|
|
0 - normal user
|
|
1 - allow remote nodes normal user RCMDs
|
|
5 - various privileged commands (including shutdown, but not disc-
|
|
connect), the normal level for another node.
|
|
8 - more privileged commands (including disconnect)
|
|
9 - local sysop privilege. DO NOT SET ANY REMOTE USER OR NODE TO THIS
|
|
LEVEL.
|
|
</PRE>
|
|
</CODE></BLOCKQUOTE>
|
|
<P>If you are a sysop and you come in as a normal user on a remote connection
|
|
your privilege will automatically be set to 0.
|
|
<P>
|
|
<H2><A NAME="ss9.92">9.92 set/spider (5)</A>
|
|
</H2>
|
|
|
|
<P><CODE><B>set/spider <node_call> [<node_call> ...]</B> Make
|
|
the node_call a DXSpider type node</CODE>
|
|
<P>
|
|
<P>Set the node_call as a DXSpider type node
|
|
<P>
|
|
<H2><A NAME="ss9.93">9.93 set/sys_qra (9)</A>
|
|
</H2>
|
|
|
|
<P><CODE><B>set/sys_qra <locator></B> Set your cluster QRA locator</CODE>
|
|
<P>
|
|
<H2><A NAME="ss9.94">9.94 set/qra (0)</A>
|
|
</H2>
|
|
|
|
<P><CODE><B>set/qra <locator></B> Set your QRA locator</CODE>
|
|
<P>
|
|
<P>Tell the system what your QRA (or Maidenhead) locator is. If you have not
|
|
done a SET/LOCATION then your latitude and longitude will be set roughly
|
|
correctly (assuming your locator is correct ;-). For example:-
|
|
<P>
|
|
<BLOCKQUOTE><CODE>
|
|
<PRE>
|
|
SET/QRA JO02LQ
|
|
</PRE>
|
|
</CODE></BLOCKQUOTE>
|
|
<P>
|
|
<H2><A NAME="ss9.95">9.95 set/qth (0)</A>
|
|
</H2>
|
|
|
|
<P><CODE><B>set/qth <your QTH></B> Set your QTH</CODE>
|
|
<P>
|
|
<P>Tell the system where your are. For example:-
|
|
<P>
|
|
<BLOCKQUOTE><CODE>
|
|
<PRE>
|
|
set/qth East Dereham, Norfolk
|
|
</PRE>
|
|
</CODE></BLOCKQUOTE>
|
|
<P>
|
|
<H2><A NAME="ss9.96">9.96 set/talk (0)</A>
|
|
</H2>
|
|
|
|
<P><CODE><B>set/talk</B> Allow talk messages to be seen at your console</CODE>
|
|
<P>
|
|
<P>Allow talk messages to arrive at your console. You can switch off
|
|
talks with the <EM>unset/talk</EM> command.
|
|
<P>
|
|
<H2><A NAME="ss9.97">9.97 set/wcy (0)</A>
|
|
</H2>
|
|
|
|
<P><CODE><B>set/wcy</B> Allow WCY messages to be seen at your console</CODE>
|
|
<P>
|
|
<P>Allow WCY information to be seen at your console. You can switch off
|
|
WCY messages with the <EM>unset/wcy</EM> command.
|
|
<P>
|
|
<H2><A NAME="ss9.98">9.98 set/wwv (0)</A>
|
|
</H2>
|
|
|
|
<P><CODE><B>set/wwv</B> Allow WWV messages to be seen at your console</CODE>
|
|
<P>
|
|
<P>Allow WWV information to be seen at your console. You can switch off
|
|
WWV messages with the <EM>unset/wwv</EM> command.
|
|
<P>
|
|
<H2><A NAME="ss9.99">9.99 set/wx (0)</A>
|
|
</H2>
|
|
|
|
<P><CODE><B>set/wx</B> Allow WX messages to be seen at your console</CODE>
|
|
<P>
|
|
<P>Allow WX information to be seen at your console. You can switch off
|
|
WX messages with the <EM>unset/wx</EM> command.
|
|
<P>
|
|
<H2><A NAME="ss9.100">9.100 show/baddx (1)</A>
|
|
</H2>
|
|
|
|
<P><CODE><B>show/baddx</B>Show all the bad dx calls in the system</CODE>
|
|
<P>
|
|
<P>Display all the bad dx callsigns in the system, see SET/BADDX
|
|
for more information.
|
|
<P>
|
|
<H2><A NAME="ss9.101">9.101 show/badnode (6)</A>
|
|
</H2>
|
|
|
|
<P><CODE><B>show/badnode</B> Show all the bad nodes in the system</CODE>
|
|
<P>
|
|
<P>Display all the bad node callsigns in the system, see SET/BADNODE
|
|
for more information.
|
|
<P>
|
|
<H2><A NAME="ss9.102">9.102 show/badspotter (1)</A>
|
|
</H2>
|
|
|
|
<P><CODE><B>show/badspotter</B> Show all the bad spotters in the system</CODE>
|
|
<P>
|
|
<P>Display all the bad spotter's callsigns in the system, see SET/BADSPOTTER
|
|
for more information.
|
|
<P>
|
|
<H2><A NAME="ss9.103">9.103 show/configuration (0)</A>
|
|
</H2>
|
|
|
|
<P><CODE><B>show/configuration [<node>]</B> Show all visible nodes and their users</CODE>
|
|
<P>
|
|
<P>This command allows you to see all the users that can be seen
|
|
and the nodes to which they are connected. With the optional <EM>node</EM>,
|
|
you can specify a particular node to look at.
|
|
<P>This command is normally abbreviated to: sh/c
|
|
<P>BE WARNED: the list that is returned can be VERY long
|
|
<P>
|
|
<H2><A NAME="ss9.104">9.104 show/configuration/node (0)</A>
|
|
</H2>
|
|
|
|
<P><CODE><B>show/configuration/node</B> Show all the nodes connected</CODE>
|
|
<P>
|
|
<P>Show all the nodes connected locally and the nodes they have connected.
|
|
<P>
|
|
<H2><A NAME="ss9.105">9.105 show/connect (1)</A>
|
|
</H2>
|
|
|
|
<P><CODE><B>show/connect</B> Show all the active connections</CODE>
|
|
<P>
|
|
<P>This command shows information on all the active connections known to
|
|
the node. This command gives slightly more information than WHO.
|
|
<P>
|
|
<H2><A NAME="ss9.106">9.106 show/date (0)</A>
|
|
</H2>
|
|
|
|
<P><CODE><B>show/date [<prefix>|<callsign>]</B> Show
|
|
the local time</CODE>
|
|
<P>
|
|
<P>This is very nearly the same as SHOW/TIME, the only difference the format
|
|
of the date string if no arguments are given.
|
|
<P>If no prefixes or callsigns are given then this command returns the local
|
|
time and UTC as the computer has it right now. If you give some prefixes
|
|
then it will show UTC and UTC + the local offset (not including DST) at
|
|
the prefixes or callsigns that you specify.
|
|
<P>
|
|
<H2><A NAME="ss9.107">9.107 show/debug (9)</A>
|
|
</H2>
|
|
|
|
<P><CODE><B>show/debug</B> Show what levels of debug you are logging</CODE>
|
|
<P>
|
|
<P>The levels can be set with <EM>set/debug</EM>
|
|
<P>
|
|
<H2><A NAME="ss9.108">9.108 show/dx (0)</A>
|
|
</H2>
|
|
|
|
<P><CODE><B>show/dx [options]</B> interrogate the spot database</CODE>
|
|
<P>
|
|
<P>If you just type SHOW/DX you will get the last so many spots
|
|
(sysop configurable, but usually 10).
|
|
<P>In addition you can add any number of these options in very nearly
|
|
any order to the basic SHOW/DX command, they are:-
|
|
<P>
|
|
<BLOCKQUOTE><CODE>
|
|
<PRE>
|
|
|
|
on <band> - eg 160m 20m 2m 23cm 6mm
|
|
on <region> - eg hf vhf uhf shf (see SHOW/BANDS)
|
|
|
|
<number> - the number of spots you want
|
|
<from>-<to> - <from> spot no <to> spot no in
|
|
the selected list
|
|
|
|
<prefix> - for a spotted callsign beginning with <prefix>
|
|
*<suffix> - for a spotted callsign ending in <suffix>
|
|
*<string>* - for a spotted callsign containing <string>
|
|
|
|
day <number> - starting <number> days ago
|
|
day <from>-<to> - <from> days <to> days ago
|
|
|
|
info <text> - any spots containing <text> in the info or remarks
|
|
|
|
by <call> - any spots spotted by <call> (spotter <call>
|
|
is the same).
|
|
|
|
qsl - this automatically looks for any qsl info on the call
|
|
held in the spot database.
|
|
|
|
iota [<iota>] - If the iota island number is missing it will
|
|
look for the string iota and anything which looks like
|
|
an iota island number. If you specify then it will look
|
|
for that island.
|
|
|
|
qra [<locator>] - this will look for the specific locator if
|
|
you specify one or else anything that looks like a locator.
|
|
</PRE>
|
|
</CODE></BLOCKQUOTE>
|
|
<P>e.g.
|
|
<P>
|
|
<BLOCKQUOTE><CODE>
|
|
<PRE>
|
|
|
|
SH/DX 9m0
|
|
SH/DX on 20m info iota
|
|
SH/DX 9a on vhf day 30
|
|
SH/DX rf1p qsl
|
|
SH/DX iota
|
|
SH/DX iota eu-064
|
|
SH/DX qra jn86
|
|
</PRE>
|
|
</CODE></BLOCKQUOTE>
|
|
<P>
|
|
<H2><A NAME="ss9.109">9.109 show/dxcc (0)</A>
|
|
</H2>
|
|
|
|
<P><CODE><B>show/dxcc <prefix></B> Interrogate the spot database by country</CODE>
|
|
<P>
|
|
<P>This command takes the <prefix> (which can be a full or partial
|
|
callsign if desired), looks up which internal country number it is
|
|
and then displays all the spots as per SH/DX for that country.
|
|
<P>The options for SHOW/DX also apply to this command.
|
|
e.g.
|
|
<P>
|
|
<BLOCKQUOTE><CODE>
|
|
<PRE>
|
|
|
|
SH/DXCC G
|
|
SH/DXCC W on 20m info iota
|
|
</PRE>
|
|
</CODE></BLOCKQUOTE>
|
|
<P>
|
|
<H2><A NAME="ss9.110">9.110 show/files (0)</A>
|
|
</H2>
|
|
|
|
<P><CODE><B>show/files [<filearea> [<string>]]</B> List
|
|
the contents of a filearea</CODE>
|
|
<P>
|
|
<P>SHOW/FILES on its own will show you a list of the various fileareas
|
|
available on the system. To see the contents of a particular file
|
|
area type:-
|
|
<P>
|
|
<BLOCKQUOTE><CODE>
|
|
<PRE>
|
|
SH/FILES <filearea>
|
|
</PRE>
|
|
</CODE></BLOCKQUOTE>
|
|
<P>where <filearea> is the name of the filearea you want to see the
|
|
contents of.
|
|
<P>You can also use shell globbing characters like '*' and '?' in a
|
|
string to see a selection of files in a filearea eg:-
|
|
<P>
|
|
<BLOCKQUOTE><CODE>
|
|
<PRE>
|
|
SH/FILES bulletins arld*
|
|
</PRE>
|
|
</CODE></BLOCKQUOTE>
|
|
<P>See also TYPE - to see the contents of a file.
|
|
<P>
|
|
<H2><A NAME="ss9.111">9.111 show/filter (0)</A>
|
|
</H2>
|
|
|
|
<P><CODE><B>show/filter</B> Show the filters you have set</CODE>
|
|
<P>
|
|
<P>Show the contents of all the filters that are set by you. This command
|
|
displays all the filters set - for all the various categories.
|
|
<P>
|
|
<H2><A NAME="ss9.112">9.112 show/filter (extended for sysops) (5)</A>
|
|
</H2>
|
|
|
|
<P><CODE><B>show/filter <callsign></B> Show the filters set by <callsign></CODE>
|
|
<P>
|
|
<P>A sysop can look at any filters that have been set.
|
|
<P>
|
|
<H2><A NAME="ss9.113">9.113 show/hops (8)</A>
|
|
</H2>
|
|
|
|
<P><CODE><B>show/hops <node_call> [ann|spots|wcy|wwv|]</B> Show the hop counts for a node</CODE>
|
|
<P>
|
|
<P>This command shows the hop counts set up for a node. You can specify
|
|
which category you want to see. If you leave the category out then
|
|
all the categories will be listed.
|
|
<P>
|
|
<H2><A NAME="ss9.114">9.114 show/isolate (1)</A>
|
|
</H2>
|
|
|
|
<P><CODE><B>show/isolate</B> Show a list of isolated nodes</CODE>
|
|
<P>
|
|
<P>Show which nodes are currently set to be isolated.
|
|
<P>
|
|
<H2><A NAME="ss9.115">9.115 show/lockout (9)</A>
|
|
</H2>
|
|
|
|
<P><CODE><B>show/lockout</B> Show a list of excluded callsigns</CODE>
|
|
<P>
|
|
<P>Show a list of callsigns that have been excluded (locked out) of the
|
|
cluster locally with the <EM>set/lockout</EM> command
|
|
<P>
|
|
<H2><A NAME="ss9.116">9.116 show/log (8)</A>
|
|
</H2>
|
|
|
|
<P><CODE><B>show/log [<callsign>]</B> Show excerpts from the system log</CODE>
|
|
<P>
|
|
<P>This command outputs a short section of the system log. On its own
|
|
it will output a general logfile. With the optional callsign it will
|
|
show output from the log associated with that callsign.
|
|
<P>
|
|
<H2><A NAME="ss9.117">9.117 show/moon (0)</A>
|
|
</H2>
|
|
|
|
<P><CODE><B>show/moon [<prefix>|<callsign>]</B> Show moon
|
|
rise and set times</CODE>
|
|
<P>
|
|
<P>Show the Moon rise and set times for a (list of) prefixes or callsigns,
|
|
together with the azimuth and elevation of the sun currently at those
|
|
locations.
|
|
<P>If you don't specify any prefixes or callsigns, it will show the times for
|
|
your QTH (assuming you have set it with either SET/LOCATION or SET/QRA),
|
|
together with the current azimuth and elevation.
|
|
<P>In addition, it will show the gain or loss dB relative to the nominal
|
|
distance of 385,000Km due to the ellipsoidal nature of the orbit.
|
|
<P>If all else fails it will show the Moonrise and set times for the node
|
|
that you are connected to.
|
|
<P>For example:-
|
|
<P>
|
|
<BLOCKQUOTE><CODE>
|
|
<PRE>
|
|
SH/MOON
|
|
SH/MOON G1TLH W5UN
|
|
</PRE>
|
|
</CODE></BLOCKQUOTE>
|
|
<P>
|
|
<H2><A NAME="ss9.118">9.118 show/muf (0)</A>
|
|
</H2>
|
|
|
|
<P><CODE><B>show/muf <prefix> [<hours>][long]</B> Show
|
|
the likely propagation to <prefix></CODE>
|
|
<P>
|
|
<P>This command allow you to estimate the likelihood of you contacting
|
|
a station with the prefix you have specified. The output assumes a modest
|
|
power of 20dBW and receiver sensitivity of -123dBm (about 0.15muV/10dB SINAD)
|
|
<P>The result predicts the most likely operating frequencies and signal
|
|
levels for high frequency (shortwave) radio propagation paths on
|
|
specified days of the year and hours of the day. It is most useful for
|
|
paths between 250 km and 6000 km, but can be used with reduced accuracy
|
|
for paths shorter or longer than this.
|
|
<P>The command uses a routine MINIMUF 3.5 developed by the U.S. Navy and
|
|
used to predict the MUF given the predicted flux, day of the year,
|
|
hour of the day and geographic coordinates of the transmitter and
|
|
receiver. This routine is reasonably accurate for the purposes here,
|
|
with a claimed RMS error of 3.8 MHz, but much smaller and less complex
|
|
than the programs used by major shortwave broadcasting organizations,
|
|
such as the Voice of America.
|
|
<P>The command will display some header information detailing its
|
|
assumptions, together with the locations, latitude and longitudes and
|
|
bearings. It will then show UTC (UT), local time at the other end
|
|
(LT), calculate the MUFs, Sun zenith angle at the midpoint of the path
|
|
(Zen) and the likely signal strengths. Then for each frequency for which
|
|
the system thinks there is a likelihood of a circuit it prints a value.
|
|
<P>The value is currently a likely S meter reading based on the conventional
|
|
6dB / S point scale. If the value has a '+' appended it means that it is
|
|
1/2 an S point stronger. If the value is preceeded by an 'm' it means that
|
|
there is likely to be much fading and by an 's' that the signal is likely
|
|
to be noisy.
|
|
<P>By default SHOW/MUF will show the next two hours worth of data. You
|
|
can specify anything up to 24 hours worth of data by appending the no of
|
|
hours required after the prefix. For example:-
|
|
<P>
|
|
<BLOCKQUOTE><CODE>
|
|
<PRE>
|
|
SH/MUF W
|
|
</PRE>
|
|
</CODE></BLOCKQUOTE>
|
|
<P>produces:
|
|
<P>
|
|
<BLOCKQUOTE><CODE>
|
|
<PRE>
|
|
RxSens: -123 dBM SFI: 159 R: 193 Month: 10 Day: 21
|
|
Power : 20 dBW Distance: 6283 km Delay: 22.4 ms
|
|
Location Lat / Long Azim
|
|
East Dereham, Norfolk 52 41 N 0 57 E 47
|
|
United-States-W 43 0 N 87 54 W 299
|
|
UT LT MUF Zen 1.8 3.5 7.0 10.1 14.0 18.1 21.0 24.9 28.0 50.0
|
|
18 23 11.5 -35 mS0+ mS2 S3
|
|
19 0 11.2 -41 mS0+ mS2 S3
|
|
</PRE>
|
|
</CODE></BLOCKQUOTE>
|
|
<P>indicating that you will have weak, fading circuits on top band and
|
|
80m but usable signals on 40m (about S3).
|
|
<P>inputing:-
|
|
<P>
|
|
<BLOCKQUOTE><CODE>
|
|
<PRE>
|
|
SH/MUF W 24
|
|
</PRE>
|
|
</CODE></BLOCKQUOTE>
|
|
<P>will get you the above display, but with the next 24 hours worth of
|
|
propagation data.
|
|
<P>
|
|
<BLOCKQUOTE><CODE>
|
|
<PRE>
|
|
SH/MUF W L 24
|
|
SH/MUF W 24 Long
|
|
</PRE>
|
|
</CODE></BLOCKQUOTE>
|
|
<P>Gives you an estimate of the long path propagation characterics. It
|
|
should be noted that the figures will probably not be very useful, nor
|
|
terrible accurate, but it is included for completeness.
|
|
<P>
|
|
<H2><A NAME="ss9.119">9.119 show/node (1)</A>
|
|
</H2>
|
|
|
|
<P><CODE><B>show/node [<node_call> ...]</B> Show the type and version
|
|
number of nodes</CODE>
|
|
<P>
|
|
<P>Show the type and version (if connected) of the nodes specified on the
|
|
command line. If no callsigns are specified then a sorted list of all
|
|
the non-user callsigns known to the system will be displayed.
|
|
<P>
|
|
<H2><A NAME="ss9.120">9.120 show/prefix (0)</A>
|
|
</H2>
|
|
|
|
<P><CODE><B>show/prefix <callsign></B> Interrogate the prefix database</CODE>
|
|
<P>
|
|
<P>This command takes the <callsign> (which can be a full or partial
|
|
callsign or a prefix), looks up which internal country number
|
|
it is and then displays all the relevant prefixes for that country
|
|
together with the internal country no, the CQ and ITU regions.
|
|
<P>See also SHOW/DXCC
|
|
<P>
|
|
<P>
|
|
<H2><A NAME="ss9.121">9.121 show/program (5)</A>
|
|
</H2>
|
|
|
|
<P><CODE><B>show/program</B> Show the locations of all the included program modules</CODE>
|
|
<P>
|
|
<P>Show the name and location where every program module was load from. This
|
|
is useful for checking where you think you have loaded a .pm file from.
|
|
<P>
|
|
<H2><A NAME="ss9.122">9.122 show/qra (0)</A>
|
|
</H2>
|
|
|
|
<P><CODE><B>show/qra <locator> [<locator>]</B> Show the distance
|
|
between locators<BR>
|
|
<B>show/qra <lat> <long></B> Convert latitude and longitude to a locator</CODE>
|
|
<P>
|
|
<P>This is a multipurpose command that allows you either to calculate the
|
|
distance and bearing between two locators or (if only one locator is
|
|
given on the command line) the distance and beraing from your station
|
|
to the locator. For example:-
|
|
<P>
|
|
<BLOCKQUOTE><CODE>
|
|
<PRE>
|
|
SH/QRA IO92QL
|
|
SH/QRA JN06 IN73
|
|
</PRE>
|
|
</CODE></BLOCKQUOTE>
|
|
<P>The first example will show the distance and bearing to the locator from
|
|
yourself, the second example will calculate the distance and bearing from
|
|
the first locator to the second. You can use 4 or 6 character locators.
|
|
<P>It is also possible to convert a latitude and longitude to a locator by
|
|
using this command with a latitude and longitude as an argument, for
|
|
example:-
|
|
<P>
|
|
<BLOCKQUOTE><CODE>
|
|
<PRE>
|
|
SH/QRA 52 41 N 0 58 E
|
|
</PRE>
|
|
</CODE></BLOCKQUOTE>
|
|
<P>
|
|
<H2><A NAME="ss9.123">9.123 show/qrz (0)</A>
|
|
</H2>
|
|
|
|
<P><CODE><B>show/qrz <callsign></B> Show any callbook details on a callsign</CODE>
|
|
<P>
|
|
<P>This command queries the QRZ callbook server on the internet
|
|
and returns any information available for that callsign. This service
|
|
is provided for users of this software by http://www.qrz.com
|
|
<P>
|
|
<H2><A NAME="ss9.124">9.124 show/route (0)</A>
|
|
</H2>
|
|
|
|
<P><CODE><B>show/route <callsign></B> Show the route to <callsign></CODE>
|
|
<P>
|
|
<P>This command allows you to see to which node the callsigns specified are
|
|
connected. It is a sort of inverse sh/config.
|
|
<P>
|
|
<BLOCKQUOTE><CODE>
|
|
<PRE>
|
|
sh/route n2tly
|
|
</PRE>
|
|
</CODE></BLOCKQUOTE>
|
|
<P>
|
|
<H2><A NAME="ss9.125">9.125 show/satellite (0)</A>
|
|
</H2>
|
|
|
|
<P><CODE><B>show/satellite <name> [<hours> <interval>]</B>
|
|
Show satellite tracking data</CODE>
|
|
<P>
|
|
<P>Show the tracking data from your location to the satellite of your choice
|
|
from now on for the next few hours.
|
|
<P>If you use this command without a satellite name it will display a list
|
|
of all the satellites known currently to the system.
|
|
<P>If you give a name then you can obtain tracking data of all the passes
|
|
that start and finish 5 degrees below the horizon. As default it will
|
|
give information for the next three hours for every five minute period.
|
|
<P>You can alter the number of hours and the step size, within certain
|
|
limits.
|
|
<P>Each pass in a period is separated with a row of '-----' characters
|
|
<P>So for example:-
|
|
<P>
|
|
<BLOCKQUOTE><CODE>
|
|
<PRE>
|
|
SH/SAT AO-10
|
|
SH/SAT FENGYUN1 12 2
|
|
</PRE>
|
|
</CODE></BLOCKQUOTE>
|
|
<P>
|
|
<H2><A NAME="ss9.126">9.126 show/sun (0)</A>
|
|
</H2>
|
|
|
|
<P><CODE><B>show/sun [<prefix>|<callsign>]</B> Show
|
|
sun rise and set times</CODE>
|
|
<P>
|
|
<P>Show the sun rise and set times for a (list of) prefixes or callsigns,
|
|
together with the azimuth and elevation of the sun currently at those
|
|
locations.
|
|
<P>If you don't specify any prefixes or callsigns, it will show the times for
|
|
your QTH (assuming you have set it with either SET/LOCATION or SET/QRA),
|
|
together with the current azimuth and elevation.
|
|
<P>If all else fails it will show the sunrise and set times for the node
|
|
that you are connected to.
|
|
<P>For example:-
|
|
<P>
|
|
<BLOCKQUOTE><CODE>
|
|
<PRE>
|
|
SH/SUN
|
|
SH/SUN G1TLH K9CW ZS
|
|
</PRE>
|
|
</CODE></BLOCKQUOTE>
|
|
<P>
|
|
<H2><A NAME="ss9.127">9.127 show/time (0)</A>
|
|
</H2>
|
|
|
|
<P><CODE><B>show/time [<prefix>|<callsign>]</B> Show
|
|
the local time</CODE>
|
|
<P>
|
|
<P>If no prefixes or callsigns are given then this command returns the local
|
|
time and UTC as the computer has it right now. If you give some prefixes
|
|
then it will show UTC and UTC + the local offset (not including DST) at
|
|
the prefixes or callsigns that you specify.
|
|
<P>
|
|
<H2><A NAME="ss9.128">9.128 show/wcy (0)</A>
|
|
</H2>
|
|
|
|
<P><CODE><B>show/wcy</B> Show the last 10 WCY broadcasts<BR>
|
|
<B>show/wcy <n></B> Show the last <n> WCY broadcasts</CODE>
|
|
<P>
|
|
<P>Display the most recent WCY information that has been received by the system
|
|
<P>
|
|
<H2><A NAME="ss9.129">9.129 show/wwv (0)</A>
|
|
</H2>
|
|
|
|
<P><CODE><B>show/wwv</B> Show the last 10 WWV broadcasts<BR>
|
|
<B>show/wwv <n></B> Show the last <n> WWV broadcasts</CODE>
|
|
<P>
|
|
<P>Display the most recent WWV information that has been received by the system
|
|
<P>
|
|
<P>
|
|
<H2><A NAME="ss9.130">9.130 shutdown (5)</A>
|
|
</H2>
|
|
|
|
<P><CODE><B>shutdown</B> Shutdown the cluster</CODE>
|
|
<P>
|
|
<P>Shutdown the cluster and disconnect all the users. If you have Spider
|
|
set to respawn in /etc/inittab it will of course restart.
|
|
<P>
|
|
<H2><A NAME="ss9.131">9.131 spoof (9)</A>
|
|
</H2>
|
|
|
|
<P><CODE><B>spoof <callsign> <command></B> Run commands as another user</CODE>
|
|
<P>
|
|
<P>This is a very simple yet powerful command for the sysop. It allows you to
|
|
issue commands as if you were a different user. This is very useful for the
|
|
kind of things that users seem to always get wrong.. like home_node for
|
|
example.
|
|
<P>
|
|
<H2><A NAME="ss9.132">9.132 stat/db (5)</A>
|
|
</H2>
|
|
|
|
<P><CODE><B>stat/db <dbname></B> Show the status of a database</CODE>
|
|
<P>
|
|
<P>Show the internal status of a database descriptor.
|
|
<P>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.
|
|
<P>
|
|
<H2><A NAME="ss9.133">9.133 stat/channel (5)</A>
|
|
</H2>
|
|
|
|
<P><CODE><B>stat/channel <callsign></B> Show the status of a channel on the cluster</CODE>
|
|
<P>
|
|
<P>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.
|
|
<P>Only the fields that are defined (in perl term) will be displayed.
|
|
<P>
|
|
<H2><A NAME="ss9.134">9.134 stat/msg (5)</A>
|
|
</H2>
|
|
|
|
<P><CODE><B>stat/msg <msgno></B> Show the status of a message</CODE>
|
|
<P>
|
|
<P>This command shows the internal status of a message and includes information
|
|
such as to whom it has been forwarded, its size, origin etc etc.
|
|
<P>
|
|
<H2><A NAME="ss9.135">9.135 stat/user (5)</A>
|
|
</H2>
|
|
|
|
<P><CODE><B>stat/user <callsign></B> Show the full status of a user</CODE>
|
|
<P>
|
|
<P>Shows the full contents of a user record including all the secret flags
|
|
and stuff.
|
|
<P>Only the fields that are defined (in perl term) will be displayed.
|
|
<P>
|
|
<H2><A NAME="ss9.136">9.136 sysop (0)</A>
|
|
</H2>
|
|
|
|
<P><CODE><B>sysop</B> Regain your privileges if you login remotely</CODE>
|
|
<P>
|
|
<P>The system automatically reduces your privilege level to that of a
|
|
normal user if you login in remotely. This command allows you to
|
|
regain your normal privilege level. It uses the normal system: five
|
|
numbers are returned that are indexes into the character array that is
|
|
your assigned password (see SET/PASSWORD). The indexes start from
|
|
zero.
|
|
<P>You are expected to return a string which contains the characters
|
|
required in the correct order. You may intersperse those characters
|
|
with others to obscure your reply for any watchers. For example (and
|
|
these values are for explanation :-):
|
|
<P>
|
|
<BLOCKQUOTE><CODE>
|
|
<PRE>
|
|
password = 012345678901234567890123456789
|
|
> sysop
|
|
22 10 15 17 3
|
|
</PRE>
|
|
</CODE></BLOCKQUOTE>
|
|
<P>you type:-
|
|
<P>
|
|
<BLOCKQUOTE><CODE>
|
|
<PRE>
|
|
aa2bbbb0ccc5ddd7xxx3n
|
|
or 2 0 5 7 3
|
|
or 20573
|
|
</PRE>
|
|
</CODE></BLOCKQUOTE>
|
|
<P>They will all match. If there is no password you will still be offered
|
|
numbers but nothing will happen when you input a string. Any match is
|
|
case sensitive.
|
|
<P>
|
|
<H2><A NAME="ss9.137">9.137 talk (0)</A>
|
|
</H2>
|
|
|
|
<P><CODE><B>talk <callsign></B> Enter talk mode with <callsign><BR>
|
|
<B>talk <callsign> <text></B> Send a text message to <callsign><BR>
|
|
<B>talk <callsign> > <node_call> [<text>]</B>
|
|
Send a text message to <callsign> via <node_call></CODE>
|
|
<P>
|
|
<P>Send a short message to any other station that is visible on the cluster
|
|
system. You can send it to anyone you can see with a SHOW/CONFIGURATION
|
|
command, they don't have to be connected locally.
|
|
<P>The second form of TALK is used when other cluster nodes are connected
|
|
with restricted information. This usually means that they don't send
|
|
the user information usually associated with logging on and off the cluster.
|
|
<P>If you know that G3JNB is likely to be present on GB7TLH, but you can only
|
|
see GB7TLH in the SH/C list but with no users, then you would use the
|
|
second form of the talk message.
|
|
<P>If you want to have a ragchew with someone you can leave the text message
|
|
out and the system will go into 'Talk' mode. What this means is that a
|
|
short message is sent to the recipient telling them that you are in a 'Talking'
|
|
frame of mind and then you just type - everything you send will go to the
|
|
station that you asked for.
|
|
<P>All the usual announcements, spots and so on will still come out on your
|
|
terminal.
|
|
<P>If you want to do something (such as send a spot) you precede the normal
|
|
command with a '/' character, eg:-
|
|
<P>
|
|
<BLOCKQUOTE><CODE>
|
|
<PRE>
|
|
/DX 14001 G1TLH What's a B class licensee doing on 20m CW?
|
|
/HELP talk
|
|
</PRE>
|
|
</CODE></BLOCKQUOTE>
|
|
<P>To leave talk mode type:
|
|
<P>
|
|
<BLOCKQUOTE><CODE>
|
|
<PRE>
|
|
/EX
|
|
</PRE>
|
|
</CODE></BLOCKQUOTE>
|
|
<P>
|
|
<H2><A NAME="ss9.138">9.138 type (0)</A>
|
|
</H2>
|
|
|
|
<P><CODE><B>type <filearea>/<name></B> Look at a file in one of the fileareas</CODE>
|
|
<P>
|
|
<P>Type out the contents of a file in a filearea. So, for example, in
|
|
filearea 'bulletins' you want to look at file 'arld051' you would
|
|
enter:-
|
|
<P>
|
|
<BLOCKQUOTE><CODE>
|
|
<PRE>
|
|
TYPE bulletins/arld051
|
|
</PRE>
|
|
</CODE></BLOCKQUOTE>
|
|
<P>See also SHOW/FILES to see what fileareas are available and a
|
|
list of content.
|
|
<P>
|
|
<H2><A NAME="ss9.139">9.139 who (0)</A>
|
|
</H2>
|
|
|
|
<P><CODE><B>who</B> Show who is physically connected locally</CODE>
|
|
<P>
|
|
<P>This is a quick listing that shows which callsigns are connected and
|
|
what sort of connection they have
|
|
<P>
|
|
<H2><A NAME="ss9.140">9.140 wx (0)</A>
|
|
</H2>
|
|
|
|
<P><CODE><B>wx <text></B> Send a weather message to local users<BR>
|
|
<B>wx full <text> </B> Send a weather message to all cluster users</CODE>
|
|
<P>
|
|
<P>Weather messages can sometimes be useful if you are experiencing an extreme
|
|
that may indicate enhanced conditions
|
|
<P>
|
|
<H2><A NAME="ss9.141">9.141 wx (enhanced for sysops) (5)</A>
|
|
</H2>
|
|
|
|
<P><CODE><B>wx sysop <text></B> Send a weather message to other clusters only</CODE>
|
|
<P>
|
|
<P>Send a weather message only to other cluster nodes and not to general users.
|
|
<P>
|
|
<P>
|
|
<P>
|
|
<HR>
|
|
Next
|
|
<A HREF="adminmanual-8.html">Previous</A>
|
|
<A HREF="adminmanual.html#toc9">Contents</A>
|
|
</BODY>
|
|
</HTML>
|