X-Git-Url: http://dxcluster.org/gitweb/gitweb.cgi?a=blobdiff_plain;f=cmd%2FCommands_en.hlp;h=bb0420865fb23144d50db50e9490116238e83824;hb=f21f292746ef4a2edc703e48542d1ed2d85d14cd;hp=585811d29b4710a00bd777b2998cb036839d8d5e;hpb=3f1c5ab45aa13e99da6bea0bfcc6d4434beb5871;p=spider.git diff --git a/cmd/Commands_en.hlp b/cmd/Commands_en.hlp index 585811d2..bb042086 100644 --- a/cmd/Commands_en.hlp +++ b/cmd/Commands_en.hlp @@ -32,8 +32,8 @@ DX cluster . This process creates a new 'client' process which will use the script in /spider/connect/ to effect the 'chat' exchange necessary to traverse the network(s) to logon to the cluster . -=== 9^CATCH All|[ ...]^Mark a message as sent -=== 9^UNCATCH All|[msgno> ...]^Unmark a message as sent +=== 5^CATCHUP All|[ ...]^Mark a message as sent +=== 5^UNCATCHUP All|[msgno> ...]^Unmark a message as sent 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 @@ -41,16 +41,18 @@ 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:- - catch GB7DJK all - catch GB7DJK 300 301 302 303 + catchup GB7DJK all + catchup GB7DJK 300 301 302 303 500-510 and to undo what you have just done:- - uncatch GB7DJK all - uncatch GB7DJK 300 301 302 303 + uncatchup GB7DJK all + uncatchup GB7DJK 300 301 302 303 500-510 which will arrange for them to be forward candidates again. +Order is not important. + === 0^DBAVAIL^Show a list of all the Databases in the system Title says it all really, this command lists all the databases defined in the system. It is also aliased to SHOW/COMMAND. @@ -292,6 +294,25 @@ running in order for the changes to take effect. Reload the /spider/data/bands.pl file if you have changed it manually whilst the cluster is running. +=== 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. + +=== 9^LOAD/BADMSG^Reload the bad msg 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. + +=== 9^LOAD/BADWORDS^Reload the bad words table +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. + === 9^LOAD/CMD_CACHE^Reload the automatic command cache 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 @@ -612,6 +633,10 @@ Tell the system where you are. For example:- === 0^SET/WX^Allow WX messages to come out on your terminal === 0^UNSET/WX^Stop WX messages coming out on your terminal +=== 0^SHOW/CALL ^Show any callbook details on a callsign +This command queries an international callbook server on the internet +and returns any information available for that callsign. + === 0^SHOW/DATE [|]^Show the local time This is very nearly the same as SHOW/TIME, the only difference the format of the date string if no arguments are given.