-
accept/route <call> [0-9] <pattern> Set an 'accept' filter line for routing
+
+
Create an 'accept this routing PC Protocol' line for a filter. +
+
An accept filter line means that if a PC16/17/19/21/24/41/50 matches this filter +it is passed thru that interface. See HELP FILTERING for more info. Please read this +to understand how filters work - it will save a lot of grief later on. +
+
You can use any of the following things in this line:- +
+
+
+ call <prefixes> the callsign of the thingy
+ call_dxcc <numbers> eg: 61,62 (from eg: sh/pre G)
+ call_itu <numbers>
+ call_zone <numbers>
+ origin <prefixes> really the interface it came in on
+ origin_dxcc <numbers> eg: 61,62 (from eg: sh/pre G)
+ origin_itu <numbers>
+ origin_zone <numbers>
+
++
some examples:- +
+
+
+ acc/route gb7djk call_dxcc 61,38 (send only UK+EIRE nodes)
+ acc/route gb7djk call gb7djk (equiv to SET/ISOLATE)
+
++
You can use the tag 'all' to accept everything eg: +
+
+
+ acc/route all
+
++
accept/announce [0-9] <pattern> Set an accept filter line for spots
@@ -142,7 +185,7 @@ too hung up about that)
but this probably for advanced users...
-
accept/spots <call> [input] [0-9] <pattern> Spot filter sysop version
@@ -160,7 +203,7 @@ default for nodes and users eg:-
-
accept/wcy [0-9] <pattern> set an accept WCY filter
@@ -187,7 +230,7 @@ you either want them or not (see UNSET/WCY if you don't want them).
This command is really provided for future use.
See HELP FILTER for information.
-
accept/wcy <call> [input] [0-9] <pattern>
@@ -203,7 +246,7 @@ default for nodes and users eg:-
-
accept/wwv [0-9] <pattern> Set an accept WWV filter
@@ -235,7 +278,7 @@ filter on the following fields:-
by stations in the US).
See HELP FILTER for information.
-
accept/wwv <call> [input] [0-9] <pattern>
@@ -254,15 +297,17 @@ default for nodes and users eg:-
-
announce <text> Send an announcement to local users
Send an announcement to LOCAL users only, where <text> is the text -of the announcement you wish to broadcast +of the announcement you wish to broadcast. If you do not wish to receive +announces, use the set/noannounce command. Any announces made by +a sysop will override set/noannounce.
-
announce full <text> Send an announcement cluster wide
@@ -271,14 +316,14 @@ of the announcement you wish to broadcast
network.
-
announce sysop <text>
Send an announcement to Sysops only
-
apropos <string> Search the help database
@@ -286,14 +331,14 @@ network.
Search the help database for <string> (it isn't case sensitive), and print the names of all the commands that may be relevant.
-
bye Exit from the cluster
This will disconnect you from the cluster
-
catchup <node_call> All|[<msgno> ...] Mark a message as sent
@@ -322,7 +367,7 @@ commmands:-
which will arrange for them to be forward candidates again.
Order is not important.
-
clear/spots [1|all] Clear a spot filter line
@@ -361,7 +406,7 @@ remove the whole filter.
the filter will be completely removed.
-
connect <callsign> Start a connection to another DX Cluster
@@ -371,7 +416,7 @@ DX cluster <callsign>. This process creates a new 'client' process which w
use the script in /spider/connect/<callsign> to effect the 'chat' exchange
necessary to traverse the network(s) to logon to the cluster <callsign>.
-
dbavail Show a list of all the databases in the system
@@ -379,7 +424,7 @@ necessary to traverse the network(s) to logon to the cluster <callsign>.
The title says it all really, this command lists all the databases defined in the system. It is also aliased to SHOW/COMMAND.
-
See DBIMPORT for the importing of existing AK1A format data to databases.
See DBSHOW for generic database enquiry
- will import the standard OBLAST database that comes with AK1A into the
oblast database held locally.
- There is no warning, no comeback, no safety net.
You have been warned.
-dbcreate <name> Create a database entry
@@ -429,7 +474,7 @@ need to add a line like:-
8.19 dbimport (9)
+
8.20 dbimport (9)
dbimport <dbname> Import AK1A data into a database
@@ -441,7 +486,7 @@ database. For example:-
8.20 dbremove (9)
+
8.21 dbremove (9)
dbremove <dbname> Delete a database
@@ -457,7 +502,7 @@ the associated datafile.
8.21 dbshow (0)
+
8.22 dbshow (0)
dbshow <dbname> <key> Display an entry, if it exists, in a database
@@ -481,7 +526,7 @@ SHOW/COMMAND to find out) you can do the same thing with:
-
debug Set the cluster program into debug mode
@@ -496,7 +541,7 @@ in debug mode i.e.
It will interrupt the cluster just after the debug command has finished.
-
directory List messages
directory all List all messages
@@ -533,19 +578,19 @@ or
-
Works just like the user command except that sysops can see ALL messages.
-
disconnect <call> [<call> ...] Disconnect a user or node
Disconnect any <call> connected locally
-
dx [by <call>] <freq> <call> <remarks> Send a DX spot
@@ -578,7 +623,7 @@ of the command and they will be added to the spot.
The <freq> is compared against the available bands set up in the cluster. See SHOW/BANDS for more information.
-
export <msgno> <filename> Export a message to a file
@@ -593,7 +638,7 @@ main cluster, otherwise you can put the new files anywhere the cluster can
access. For example:-
EXPORT 2345 /tmp/a
-
export_users [<filename>] Export the users database to ascii
@@ -606,7 +651,7 @@ suffix.
BE WARNED: this will write to any file you have write access to. No check is made on the filename (if any) that you specify.
-
forward/latlong <node_call> Send latitude and longitude information to another cluster
@@ -618,7 +663,7 @@ means that more locators are given on the DX line assuming you have
set/dxgrid enabled. This could be a LOT of information though, so
it is not recommended on slow links.
-
forward/opername <call> Send out information on this <call> to all clusters
@@ -627,7 +672,7 @@ it is not recommended on slow links.
be broadcast in PC41 protocol packets. This information is Name, QTH, Location
and Homenode. PC41s are only sent for the information that is available.
-
help <cmd> Get help on a command
@@ -638,7 +683,7 @@ to SH/DX, ANNOUNCE can be shortened to AN and so on.
for the <string> you specify and give you a list of likely commands
to look at with HELP.
-
init <node call> Re-initialise a link to an AK1A compatible node
@@ -650,7 +695,7 @@ better, if it is a real AK1A node, doing an RCMD <node> DISC/F <your
node>).
Best of luck - you will need it.
-
kill <msgno> [<msgno> ..] Delete a message from the local system
@@ -659,7 +704,7 @@ node>).
delete messages that you have originated or been sent (unless you are
the sysop).
-
As a sysop you can kill any message on the system.
- This uses the subject field, so any messages that have exactly the same subject
will be deleted. Beware!
-
-
-
-
- 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.
-
-
- 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.
-
- Reload the /spider/data/bands.pl file if you have changed it manually whilst
the cluster is running.
-
- Reload the /spider/msg/forward.pl file if you have changed it
manually whilst the cluster is running.
- unknown message 'xxxx' in lang 'en'
- Reload the /spider/data/prefix_data.pl file if you have changed it manually
whilst the cluster is running.
-
- STAT/MSG <msgno>
This will display more information on the message than DIR does.
- pc G1TLH Try doing that properly!!!
-
-
-
-
As a sysop you may read any message on the system
- but this probably for advanced users...
-
+
+ Create an 'reject this routing PC Protocol' line for a filter.
+
+ An reject filter line means that if a PC16/17/19/21/24/41/50 matches this filter
+it is NOT passed thru that interface. See HELP FILTERING for more info. Please
+read this to understand how filters work - it will save a lot of grief later on.
+You can use any of the following things in this line:-
+
+
+ some examples:-
+
+
+ You can use the tag 'all' to reject everything eg:
+
+
Add a beep to DX and other terminal messages.
-
+
Set the node_call as a CLX type node
- You can remove a debug level with unset/debug <name>
-
You can stop DX messages with the unset/dx command
-
-
Set the node_call as a DXNet type node
- The setting is stored in your user profile.
YOU DO NOT NEED TO USE THIS COMMAND IF YOU ARE CONNECTED VIA AX25.
-kill <msgno> [<msgno> ...] Remove or erase a message from the system
@@ -670,7 +715,7 @@ the sysop).
this command. You can remove more than one message at a time.
8.35 kill full (5)
+
8.36 kill full (5)
kill full <msgno> [<msgno>] Delete a message from the whole cluster
@@ -679,7 +724,7 @@ this command. You can remove more than one message at a time.
8.36 links (0)
+
8.37 links (0)
links Show which nodes are physically connected
@@ -688,7 +733,7 @@ will be deleted. Beware!
some information about them. See WHO for a list of all connections.
8.37 load/aliases (9)
+
8.38 load/aliases (9)
load/aliases Reload the command alias table
@@ -697,16 +742,6 @@ some information about them. See WHO for a list of all connections.
do this if you change this file whilst the cluster is running in order for the
changes to take effect.
8.38 load/baddx (9)
-
-
-load/baddx Reload the bad DX table
-8.39 load/badmsg (9)
@@ -717,19 +752,7 @@ 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.
8.40 load/badwords (9)
-
-
-load/badwords Reload the badwords file
-8.41 load/bands (9)
+
8.40 load/bands (9)
load/bands Reload the band limits table
@@ -737,7 +760,7 @@ more on a line, lines starting with '#' are ignored.
8.42 load/cmd_cache (9)
+
8.41 load/cmd_cache (9)
load/cmd_cache Reload the automatic command cache
@@ -748,14 +771,14 @@ 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.
8.43 load/forward (9)
+
8.42 load/forward (9)
load/forward Reload the msg forwarding routing table
8.44 load/messages (9)
+
8.43 load/messages (9)
load/messages Reload the system messages file
@@ -765,7 +788,7 @@ commands) you can have them take effect during a cluster session by executing th
command. You need to do this if get something like :-
8.45 load/prefixes (9)
+
8.44 load/prefixes (9)
load/prefixes Reload the prefix table
@@ -773,7 +796,7 @@ command. You need to do this if get something like :-
8.46 merge (5)
+
8.45 merge (5)
merge <node> [<no spots>/<no wwv>] Ask for the latest spots and WWV
@@ -785,7 +808,7 @@ node must be connected locally.
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).
8.47 msg (9)
+
8.46 msg (9)
msg <cmd> <msgno> [data ...] Alter various message parameters
@@ -816,7 +839,7 @@ out.
8.48 pc (8)
+
8.47 pc (8)
pc <call> <text> Send text (eg PC Protocol) to <call>
@@ -829,7 +852,7 @@ arise (messages get stuck etc). eg:-
without any processing, added of "from <blah> to <blah>" or whatever.
8.49 ping (1)
+
8.48 ping (1)
ping <node> Check the link quality between nodes
@@ -841,7 +864,7 @@ it takes is output to the console in seconds.
Any visible cluster node can be PINGed.
8.50 rcmd (1)
+
8.49 rcmd (1)
rcmd <node call> <cmd> Send a command to another DX cluster
@@ -853,7 +876,7 @@ 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.
8.51 read (0)
+
8.50 read (0)
read Read the next unread personal message addressed to you
@@ -863,14 +886,14 @@ permission to send this command at all.
message either sent by or sent to your callsign.
8.52 read (extended for sysops) (5)
+
8.51 read (extended for sysops) (5)
read <msgno> Read a message on the system
8.53 reject/announce
+
8.52 reject/announce
reject/announce [0-9] <pattern> Set a reject filter
@@ -914,7 +937,7 @@ to understand how filters work - it will save a lot of grief later on.
8.54 reject/announce (extended for sysops) (8)
+
8.53 reject/announce (extended for sysops) (8)
reject/announce <call> [input] [0-9] <pattern> Announce filter sysop version
@@ -930,6 +953,47 @@ default for nodes and users eg:-
8.54 reject/route (8)
+
+
+reject/route <call> [0-9] <pattern> Set an 'reject' filter line for routing
+
+
+
+ call <prefixes> the callsign of the thingy
+ call_dxcc <numbers> eg: 61,62 (from eg: sh/pre G)
+ call_itu <numbers>
+ call_zone <numbers>
+ origin <prefixes> really the interface it came in on
+ origin_dxcc <numbers> eg: 61,62 (from eg: sh/pre G)
+ origin_itu <numbers>
+ origin_zone <numbers>
+
+
+
+
+ rej/route gb7djk call_dxcc 61,38 (everything except UK+EIRE nodes)
+
+
+
+
+ rej/route all (equiv to [very] restricted mode)
+
+8.55 reject/spots (0)
@@ -1233,7 +1297,12 @@ enter them specifically.
8.70 set/clx (5)
+
8.70 set/bbs (5)
+
+
+set/bbs <call> [<call>..]Make <call> a BBS
+8.71 set/clx (5)
set/clx <node_call> [<node_call> ...] Make
@@ -1241,7 +1310,7 @@ the node_call a CLX type node
8.71 set/debug (9)
+
8.72 set/debug (9)
set/debug <name> Add a debug level to the debug set
@@ -1256,14 +1325,14 @@ connect
command.
8.72 set/dx (0)
+
8.73 set/dx (0)
set/dxAllow DX messages to arrive at your terminal
8.73 set/dxgrid (0)
+
8.74 set/dxgrid (0)
set/dxgridAllow grid squares on the end of DX messages
@@ -1272,7 +1341,7 @@ command.
the end of a DX spot. If this is the case, use the unset/dxgrid
command to remove the grid squares.
8.74 set/dxnet (5)
+
8.75 set/dxnet (5)
set/dxnet <node_call> [<node_call> ...] Make
@@ -1280,7 +1349,7 @@ the node_call a DXNet type node
8.75 set/echo (0)
+
8.76 set/echo (0)
set/echo Make the cluster echo your input
@@ -1293,7 +1362,7 @@ to change the setting appropriately.
8.76 set/here (0)
+
8.77 set/here (0)
set/here Set the here flag
@@ -1303,7 +1372,7 @@ callsign. If you are away from your terminal you can use the unset/here
-8.77 set/homenode (0)
+
8.78 set/homenode (0)
set/homenode <node_call> Set your home cluster
@@ -1318,7 +1387,7 @@ eg:-
-
Set SHOW/HOPS for information on what is already set. This command
creates a filter and works in conjunction with the filter system.
- You can see which nodes are isolated with the show/isolate (1) command.
You can remove the isolation with the command unset/isolate.
- You can select the language that you want the cluster to use. Currently
the languages available are en (English) and nl (Dutch).
-set/hops <node_call> ann|spots|wwv|wcy <n>
@@ -1338,7 +1407,7 @@ eg:
8.79 set/isolate (9)
+
8.80 set/isolate (9)
set/isolate <node call> Isolate a node from the rest of the network
@@ -1350,7 +1419,7 @@ out from it nor goes back into from the rest of the nodes connected to you.
8.80 set/language (0)
+
8.81 set/language (0)
set/language <language> Set the language you wish to use
@@ -1358,7 +1427,7 @@ out from it nor goes back into from the rest of the nodes connected to you.
8.81 set/location (0)
+
8.82 set/location (0)
set/location <lat and long> Set your latitude and longitude
@@ -1373,7 +1442,7 @@ the languages available are en (English) and nl (Dutch).
-
set/sys_location <lat & long> Set your cluster latitude and longitude
@@ -1388,7 +1457,7 @@ then this command will set your QRA locator for you. For example:-
-
set/logininfo Show logins and logouts of nodes and users
@@ -1397,7 +1466,7 @@ then this command will set your QRA locator for you. For example:-
can stop these messages by using the unset/logininfo command.
-
set/lockout <call> Stop a callsign connecting to the cluster
@@ -1405,7 +1474,7 @@ can stop these messages by using the unset/logininfo command.
You can show who is locked out with the show/lockout command. To allow the user to connect again, use the unset/lockout command.
-
set/name <your_name> Set your name
@@ -1418,7 +1487,7 @@ To allow the user to connect again, use the unset/lockout command.
-
set/node <call> [<call> ...] Make the callsign an AK1A cluster
@@ -1437,7 +1506,7 @@ fed PC Protocol rather normal user commands.
To see what your nodes are set to, use the show/nodes command.
-
set/obscount <count> <node call> Set the 'pump-up' obsolescence counter
@@ -1454,7 +1523,7 @@ what would be the third attempt, that node is disconnected.
default values, if a node has not responded to a ping within 15 minutes,
it is disconnected.
-
set/page <n> Set the number of lines per page
@@ -1472,7 +1541,7 @@ explicitly to 0 will disable paging.
The setting is stored in your user profile.
-
set/password <callsign> <string> Set a users password
@@ -1483,7 +1552,7 @@ spaces - but they won't appear in the password). You can see the
result with STAT/USER. The password is the usual 30 character baycom
type password.
-
set/pinginterval <time> <node call> Set the ping time to neighbouring nodes
@@ -1498,7 +1567,7 @@ for numbers greater than that.
(as certain cluster software doesn't always notice), see SET/OBSCOUNT
for more information.
-
set/privilege <n> <call> [<call> ...] Set the privilege level on a call
@@ -1520,7 +1589,7 @@ to commands are as default:-
If you are a sysop and you come in as a normal user on a remote connection your privilege will automatically be set to 0.
-
set/spider <node_call> [<node_call> ...] Make
@@ -1528,12 +1597,12 @@ the node_call a DXSpider type node
Set the node_call as a DXSpider type node
-
set/sys_qra <locator> Set your cluster QRA locator
-
set/qra <locator> Set your QRA locator
@@ -1548,7 +1617,7 @@ correctly (assuming your locator is correct ;-). For example:-
-
set/qth <your QTH> Set your QTH
@@ -1561,7 +1630,7 @@ correctly (assuming your locator is correct ;-). For example:-
-
set/talk Allow talk messages to be seen at your console
@@ -1569,7 +1638,7 @@ correctly (assuming your locator is correct ;-). For example:-
Allow talk messages to arrive at your console. You can switch off talks with the unset/talk command.
-
set/wcy Allow WCY messages to be seen at your console
@@ -1577,7 +1646,7 @@ talks with the unset/talk command.
Allow WCY information to be seen at your console. You can switch off WCY messages with the unset/wcy command.
-
set/wwv Allow WWV messages to be seen at your console
@@ -1585,7 +1654,7 @@ WCY messages with the unset/wcy command.
Allow WWV information to be seen at your console. You can switch off WWV messages with the unset/wwv command.
-
set/wx Allow WX messages to be seen at your console
@@ -1593,7 +1662,7 @@ WWV messages with the unset/wwv command.
Allow WX information to be seen at your console. You can switch off WX messages with the unset/wx command.
-
show/baddxShow all the bad dx calls in the system
@@ -1601,7 +1670,7 @@ WX messages with the unset/wx command.
Display all the bad dx callsigns in the system, see SET/BADDX for more information.
-
show/badnode Show all the bad nodes in the system
@@ -1609,7 +1678,7 @@ for more information.
Display all the bad node callsigns in the system, see SET/BADNODE for more information.
-
show/badspotter Show all the bad spotters in the system
@@ -1617,7 +1686,7 @@ for more information.
Display all the bad spotter's callsigns in the system, see SET/BADSPOTTER for more information.
-
show/configuration [<node>] Show all visible nodes and their users
@@ -1628,14 +1697,14 @@ you can specify a particular node to look at.
This command is normally abbreviated to: sh/c
BE WARNED: the list that is returned can be VERY long
-
show/configuration/node Show all the nodes connected
Show all the nodes connected locally and the nodes they have connected.
-
show/connect Show all the active connections
@@ -1643,7 +1712,7 @@ you can specify a particular node to look at.
This command shows information on all the active connections known to the node. This command gives slightly more information than WHO.
-
-
The levels can be set with set/debug
-show/date [<prefix>|<callsign>] Show
@@ -1656,14 +1725,14 @@ 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.
8.107 show/debug (9)
+
8.108 show/debug (9)
show/debug Show what levels of debug you are logging
8.108 show/dx (0)
+
8.109 show/dx (0)
show/dx [options] interrogate the spot database
@@ -1722,7 +1791,7 @@ qra [<locator>] - this will look for the specific locator if
-
show/dxcc <prefix> Interrogate the spot database by country
@@ -1741,7 +1810,7 @@ e.g.
-
show/files [<filearea> [<string>]] List
@@ -1768,7 +1837,7 @@ string to see a selection of files in a filearea eg:-
See also TYPE - to see the contents of a file.
-
show/filter Show the filters you have set
@@ -1776,14 +1845,14 @@ string to see a selection of files in a filearea eg:-
Show the contents of all the filters that are set by you. This command displays all the filters set - for all the various categories.
-
show/filter <callsign> Show the filters set by <callsign>
A sysop can look at any filters that have been set.
-
show/hops <node_call> [ann|spots|wcy|wwv|] Show the hop counts for a node
@@ -1792,14 +1861,14 @@ displays all the filters set - for all the various categories.
which category you want to see. If you leave the category out then
all the categories will be listed.
-
show/isolate Show a list of isolated nodes
Show which nodes are currently set to be isolated.
-
show/lockout Show a list of excluded callsigns
@@ -1807,7 +1876,7 @@ all the categories will be listed.
Show a list of callsigns that have been excluded (locked out) of the cluster locally with the set/lockout command
-
show/log [<callsign>] Show excerpts from the system log
@@ -1816,7 +1885,7 @@ cluster locally with the set/lockout command
it will output a general logfile. With the optional callsign it will
show output from the log associated with that callsign.
-
show/moon [<prefix>|<callsign>] Show moon
@@ -1841,7 +1910,7 @@ that you are connected to.
-
-
- See also SHOW/DXCC
- Show the name and location where every program module was load from. This
is useful for checking where you think you have loaded a .pm file from.
-
-
-show/muf <prefix> [<hours>][long] Show
@@ -1918,7 +1987,7 @@ propagation data.
should be noted that the figures will probably not be very useful, nor
terrible accurate, but it is included for completeness.
8.119 show/node (1)
+
8.120 show/node (1)
show/node [<node_call> ...] Show the type and version
@@ -1928,7 +1997,7 @@ number of nodes
command line. If no callsigns are specified then a sorted list of all
the non-user callsigns known to the system will be displayed.
8.120 show/prefix (0)
+
8.121 show/prefix (0)
show/prefix <callsign> Interrogate the prefix database
@@ -1940,7 +2009,7 @@ together with the internal country no, the CQ and ITU regions.
8.121 show/program (5)
+
8.122 show/program (5)
show/program Show the locations of all the included program modules
@@ -1948,7 +2017,7 @@ together with the internal country no, the CQ and ITU regions.
8.122 show/qra (0)
+
8.123 show/qra (0)
show/qra <locator> [<locator>] Show the distance
@@ -1979,7 +2048,7 @@ SH/QRA 52 41 N 0 58 E
8.123 show/qrz (0)
+
8.124 show/qrz (0)
show/qrz <callsign> Show any callbook details on a callsign
@@ -1988,7 +2057,7 @@ SH/QRA 52 41 N 0 58 E
and returns any information available for that callsign. This service
is provided for users of this software by http://www.qrz.com
8.124 show/route (0)
+
8.125 show/route (0)
show/route <callsign> Show the route to <callsign>
@@ -2002,7 +2071,7 @@ connected. It is a sort of inverse sh/config.
-
show/satellite <name> [<hours> <interval>]
@@ -2027,7 +2096,7 @@ SH/SAT FENGYUN1 12 2
-
show/sun [<prefix>|<callsign>] Show
@@ -2050,7 +2119,7 @@ that you are connected to.
-
-
Display the most recent WCY information that has been received by the system
- Display the most recent WWV information that has been received by the system
- Shutdown the cluster and disconnect all the users. If you have Spider
set to respawn in /etc/inittab it will of course restart.
-
- 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.
- Only the fields that are defined (in perl term) will be displayed.
- 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.
- If no message number is given then the status of the message system is
+displayed.
+
+
+
+ Only the fields that are defined (in perl term) will be displayed.
-
-
- See also SHOW/FILES to see what fileareas are available and a
list of content.
- This is a quick listing that shows which callsigns are connected and
what sort of connection they have
- Weather messages can sometimes be useful if you are experiencing an extreme
that may indicate enhanced conditions
-show/time [<prefix>|<callsign>] Show
@@ -2061,7 +2130,7 @@ 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.
8.128 show/wcy (0)
+
8.129 show/wcy (0)
show/wcy Show the last 10 WCY broadcasts
@@ -2069,7 +2138,7 @@ the prefixes or callsigns that you specify.
8.129 show/wwv (0)
+
8.130 show/wwv (0)
show/wwv Show the last 10 WWV broadcasts
@@ -2078,7 +2147,7 @@ the prefixes or callsigns that you specify.
8.130 shutdown (5)
+
8.131 shutdown (5)
shutdown Shutdown the cluster
@@ -2086,7 +2155,7 @@ the prefixes or callsigns that you specify.
8.131 spoof (9)
+
8.132 spoof (9)
spoof <callsign> <command> Run commands as another user
@@ -2096,7 +2165,7 @@ 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.
8.132 stat/db (5)
+
8.133 stat/db (5)
stat/db <dbname> Show the status of a database
@@ -2105,7 +2174,7 @@ example.
8.133 stat/channel (5)
+
8.134 stat/channel (5)
stat/channel <callsign> Show the status of a channel on the cluster
@@ -2114,7 +2183,7 @@ This command is unlikely to be of much use to anyone other than a sysop.
you are on or else for the callsign that you asked for.
8.134 stat/msg (5)
+
8.135 stat/msg (5)
stat/msg <msgno> Show the status of a message
@@ -2122,7 +2191,20 @@ you are on or else for the callsign that you asked for.
8.135 stat/user (5)
+
8.136 stat/route_node (5)
+
+
+stat/route_node <callsign> Show the data in a Route::Node object
+8.137 stat/route_user (5)
+
+
+stat/route_user <callsign> Show the data in a Route::User object
+8.138 stat/user (5)
stat/user <callsign> Show the full status of a user
@@ -2131,7 +2213,7 @@ such as to whom it has been forwarded, its size, origin etc etc.
and stuff.
8.136 sysop (0)
+
8.139 sysop (0)
sysop Regain your privileges if you login remotely
@@ -2167,7 +2249,7 @@ these values are for explanation :-):
numbers but nothing will happen when you input a string. Any match is
case sensitive.
8.137 talk (0)
+
8.140 talk (0)
talk <callsign> Enter talk mode with <callsign>
@@ -2208,7 +2290,7 @@ command with a '/' character, eg:-
8.138 type (0)
+
8.141 type (0)
type <filearea>/<name> Look at a file in one of the fileareas
@@ -2225,7 +2307,7 @@ enter:-
8.139 who (0)
+
8.142 who (0)
who Show who is physically connected locally
@@ -2233,7 +2315,7 @@ list of content.
8.140 wx (0)
+
8.143 wx (0)
wx <text> Send a weather message to local users
@@ -2242,7 +2324,7 @@ what sort of connection they have
8.141 wx (enhanced for sysops) (5)
+
8.144 wx (enhanced for sysops) (5)
wx sysop <text> Send a weather message to other clusters only