X-Git-Url: http://scm.dxcluster.org/gitweb/gitweb.cgi?a=blobdiff_plain;f=html%2Fadminmanual-11.html;h=e08773e303a1952d9a5499aefc66f1e7e93c0dd4;hb=b85014c2efe367be21460ff3e72f4a0727e6c26c;hp=1080a7d395783fe0b0a100eaff96544dbf416a0e;hpb=1a739957114ea367098a5731c86edb6d9bb808e2;p=spider.git diff --git a/html/adminmanual-11.html b/html/adminmanual-11.html index 1080a7d3..e08773e3 100644 --- a/html/adminmanual-11.html +++ b/html/adminmanual-11.html @@ -671,8 +671,10 @@ this command. You can remove more than one message at a time.
As a sysop you can kill any message on the system.
kill full <msgno> [<msgno>] Delete a message from the whole cluster
kill full <msgno> [<msgno>] Delete a message from the whole cluster
+
Delete a message (usually a 'bulletin') from the whole cluster system.
This uses the subject field, so any messages that have exactly the same subject will be deleted. Beware! @@ -697,8 +699,10 @@ changes to take effect.
load/baddx Reload the bad DX table
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.