X-Git-Url: http://dxcluster.org/gitweb/gitweb.cgi?a=blobdiff_plain;f=html%2Fadminmanual-8.html;h=2747eedf3a5d714afe11059072524c72d2e861d3;hb=f71ce364c08e7e603d69ebfe0a94381a3adccb6c;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.

-

8.16 load/bands (9) +

8.16 load/baddx (9) +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. +

+

8.17 load/badmsg (9) +

+ +

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. +

+

8.18 load/badwords (9) +

+ +

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. +

+

8.19 load/bands (9)

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.

-

8.17 load/cmd_cache (9) +

8.20 load/cmd_cache (9)

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.

-

8.18 load/forward (9) +

8.21 load/forward (9)

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.

-

8.19 load/messages (9) +

8.22 load/messages (9)

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'

-

8.20 load/prefixes (9) +

8.23 load/prefixes (9)

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.

-

8.21 merge (5) +

8.24 merge (5)

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).

-

8.22 msg (9) +

8.25 msg (9)

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.

-

8.23 pc (8) +

8.26 pc (8)

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!!!

-

8.24 ping (1) +

8.27 ping (1)

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.

-

8.25 rcmd (1) +

8.28 rcmd (1)

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.

-

8.26 read (5) +

8.29 read (5)

read <msgno> Read a message on the system

As a sysop you may read any message on the system

-

8.27 set/debug (9) +

8.30 set/debug (9)

set/debug <name> Add a debug level to the debug set

You can remove this level with unset/debug <name>

-

8.28 set/isolate (9) +

8.31 set/isolate (9)

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.

-

8.29 set/sys_location (9) +

8.32 set/sys_location (9)

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

-

8.30 set/lockout (9) +

8.33 set/lockout (9)

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

-

8.31 set/node (9) +

8.34 set/node (9)

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.

-

8.32 set/obscount (9) +

8.35 set/obscount (9)

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.

-

8.33 set/pinginterval (9) +

8.36 set/pinginterval (9)

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.

-

8.34 set/privilege (9) +

8.37 set/privilege (9)

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.

-

8.35 set/password (9) +

8.38 set/password (9)

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.

-

8.36 set/sys_qra (9) +

8.39 set/sys_qra (9)

set/sys_qra <locator> Set your cluster QRA locator

-

8.37 show program (5) +

8.40 show program (5)

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.

-

8.38 shutdown (5) +

8.41 shutdown (5)

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.

-

8.39 spoof (9) +

8.42 spoof (9)

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.

-

8.40 stat/db (5) +

8.43 stat/db (5)

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.

-

8.41 stat/channel (5) +

8.44 stat/channel (5)

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.

-

8.42 stat/msg (5) +

8.45 stat/msg (5)

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.

-

8.43 stat/user (5) +

8.46 stat/user (5)

stat/user <callsign> Show the full status of a user