X-Git-Url: http://gb7djk.dxcluster.net/gitweb/gitweb.cgi?a=blobdiff_plain;ds=inline;f=html%2Fadminmanual-8.html;h=2747eedf3a5d714afe11059072524c72d2e861d3;hb=4710b70a986b900450fd5a5850e88554184e0d57;hp=4d5450a1162215eed59f1ad2c55b1ed435a86c55;hpb=e90334372dd94c9deca9855be9ac7527a0da7870;p=spider.git diff --git a/html/adminmanual-8.html b/html/adminmanual-8.html index 4d5450a1..2747eedf 100644 --- a/html/adminmanual-8.html +++ b/html/adminmanual-8.html @@ -218,7 +218,36 @@ will be deleted. Beware! do this if you change this file whilst the cluster is running in order for the changes to take effect.
-
load/baddx Reload the bad DX table
Reload the /spider/data/baddx.pl file if you have changed it manually whilst +the cluster is running. This table contains the DX Calls that, if spotted, +will not be passed on. FR0G and TEST are classic examples. +
+
load/badmsg Reload the bad message table
+
+
Reload the /spider/msg/badmsg.pl file if you have changed it manually whilst +the cluster is running. This table contains a number of perl regular +expressions which are searched for in the fields targetted of each message. +If any of them match then that message is immediately deleted on receipt. +
+
load/badwords Reload the badwords file
+
+
Reload the /spider/data/badwords file if you have changed it manually whilst +the cluster is running. This file contains a list of words which, if found +on certain text portions of PC protocol, will cause those protocol frames +to be rejected. It will all put out a message if any of these words are +used on the announce, dx and talk commands. The words can be one or +more on a line, lines starting with '#' are ignored. +
+
load/bands Reload the band limits table
@@ -226,7 +255,7 @@ changes to take effect.
Reload the /spider/data/bands.pl file if you have changed it manually whilst the cluster is running.
-
load/cmd_cache Reload the automatic command cache
@@ -237,14 +266,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.
-
load/forward Reload the msg forwarding routing table
Reload the /spider/msg/forward.pl file if you have changed it manually whilst the cluster is running.
-
load/messages Reload the system messages file
@@ -254,7 +283,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 :-
unknown message 'xxxx' in lang 'en'
-
load/prefixes Reload the prefix table
@@ -262,7 +291,7 @@ command. You need to do this if get something like :-
Reload the /spider/data/prefix_data.pl file if you have changed it manually whilst the cluster is running.
-
merge <node> [<no spots>/<no wwv>] Ask for the latest spots and WWV
@@ -274,7 +303,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).
-
msg <cmd> <msgno> [data ...] Alter various message parameters
@@ -305,7 +334,7 @@ out.
STAT/MSG <msgno>
This will display more information on the message than DIR does.
-
pc <call> <text> Send text (eg PC Protocol) to <call>
@@ -318,7 +347,7 @@ arise (messages get stuck etc). eg:-
without any processing, added of "from <blah> to <blah>" or whatever.
pc G1TLH Try doing that properly!!!
-
ping <node> Send a ping command to another cluster node
@@ -328,7 +357,7 @@ The time returned is the length of time taken for a PC51 to go to another
cluster and be returned.
Any visible cluster node can be PINGed.
-
rcmd <node call> <cmd> Send a command to another DX cluster
@@ -340,21 +369,21 @@ that the node callsign of this cluster is in fact a node b) whether the
other system is allowing RCMDs from this node and c) whether you have
permission to send this command at all.
-
read <msgno> Read a message on the system
As a sysop you may read any message on the system
-
set/debug <name> Add a debug level to the debug set
You can remove this level with unset/debug <name>
-
set/isolate <node call> Isolate a node from the rest of the network
@@ -366,7 +395,7 @@ out from it nor goes back into from the rest of the nodes connected to you.
You can see which nodes are isolated with the show/isolate (1) command.
You can remove the isolation with the command unset/isolate.
-
set/sys_location <lat & long> Set your cluster latitude and longitude
@@ -376,7 +405,7 @@ what your latitude and longitude is. If you have not yet done a SET/QRA
then this command will set your QRA locator for you. For example:-
SET/LOCATION 52 22 N 0 57 E
-
set/lockout <call> Stop a callsign connecting to the cluster
@@ -384,7 +413,7 @@ then this command will set your QRA locator for you. For example:-
You can show who is locked out with the show/lockout (9) command.
To allow the user to connect again, use the command unset/lockout
-
set/node <call> [<call> ...] Make the callsign an AK1A cluster
@@ -401,7 +430,7 @@ set/arcluster
To see what your nodes are set to, use the show/nodes command.
-
set/obscount <count> <node call> Set the 'pump-up' obscelence counter
@@ -418,7 +447,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/pinginterval <time> <node call> Set the ping time to neighbouring nodes
@@ -433,7 +462,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
@@ -455,7 +484,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/password <callsign> <string> Set a users password
@@ -466,12 +495,12 @@ 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/sys_qra <locator> Set your cluster QRA locator
-
show/program Show the locations of all the included program modules
@@ -479,7 +508,7 @@ type password.
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.
-
shutdown Shutdown the cluster
@@ -487,7 +516,7 @@ is useful for checking where you think you have loaded a .pm file from.
Shutdown the cluster and disconnect all the users. If you have Spider set to respawn in /etc/inittab it will of course restart.
-
spoof <callsign> <command> Run commands as another user
@@ -497,7 +526,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.
-
stat/db <dbname> Show the status of a database
@@ -506,7 +535,7 @@ example.
Depending on your privilege level you will see more or less information. This command is unlikely to be of much use to anyone other than a sysop.
-
stat/channel <callsign> Show the status of a channel on the cluster
@@ -515,7 +544,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.
Only the fields that are defined (in perl term) will be displayed.
-
stat/msg <msgno> Show the status of a message
@@ -523,7 +552,7 @@ you are on or else for the callsign that you asked for.
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.
-
stat/user <callsign> Show the full status of a user