X-Git-Url: http://dxcluster.org/gitweb/gitweb.cgi?a=blobdiff_plain;f=cmd%2FCommands_en.hlp;h=86e22d4c672c84f3a60919a045f017efa96bd9bd;hb=e78daea2807bd541e89d89bd1c11087e55184de6;hp=d0cce0dad187b19a3d9dbce63b6a58afe6999172;hpb=8b21846900b9f840da86fef72e6ee86ac56cfb53;p=spider.git diff --git a/cmd/Commands_en.hlp b/cmd/Commands_en.hlp index d0cce0da..86e22d4c 100644 --- a/cmd/Commands_en.hlp +++ b/cmd/Commands_en.hlp @@ -1385,6 +1385,12 @@ This will show YOU the output from SH/VHFTABLE and also store it in the message. You can carry on with the message until you are ready to send it. + +=== 6^SEND_CONFIG^Broadcast PC92 C records +This is the PC92 equivalent of INIT. In that it will send out a new +PC92 C record to all interfaces. This can be used to bring other nodes +up to date quicker after a restart. + === 0^SET/ADDRESS ^Record your postal address === 9^SET/AGWENGINE^Enable the AGW Engine @@ -1653,6 +1659,20 @@ then this command will set your QRA locator for you. For example:- === 9^SET/LOCKOUT ^Stop a callsign connecting to the cluster === 9^UNSET/LOCKOUT ^Allow a callsign to connect to the cluster +=== 8^SET/MAXCONNECT [ ..]^Set max incoming connections for user/node +Set the maximum no of connections (parents) an incoming user or node is +allowed to have. If this incoming connection takes it over the separate +limits for users and nodes (defaults: 3 and 8 respectively), then the +connection is refused (with a polite message). + +The idea behind this to limit the number of copies of messages that +are sent to users (and nodes). Nodes really don't need to have more than +5 or 6 partners and users don't need more than two connections into the +cluster cloud. + +This check is only for INCOMING connections, no check is performed for +outgoing connections. + === 0^SET/NAME ^Set your name Tell the system what your name is eg:- SET/NAME Dirk @@ -2209,7 +2229,13 @@ the worldwide statistics. This command shows the hop counts set up for a node. You can specify which category you want to see. If you leave the category out then all the categories will be listed. - + +=== 0^SHOW/IK3QAR ^Obtain QSL info from IK3QAR database +Get QSL information from the online dabase run by IK3QAR. + +Your sysop needs to set up this command by obtaining a password from IK3QAR. +Instructions are available in local/Internet.pm + === 1^SHOW/ISOLATE^Show list of ISOLATED nodes === 9^SHOW/LOCKOUT |ALL^Show the list of locked out or excluded callsigns @@ -2331,17 +2357,18 @@ So if you have said: ACC/SPOT on hf Doing a SHOW/MYDX will now only, ever, show HF spots. All the other options on SH/DX can still be used. -=== 0^SHOW/NEWCONFIGURATION []^Show all the nodes and users visible -This command allows you to see all the users that can be seen -and the nodes to which they are connected. +=== 0^SHOW/NEWCONFIGURATION [USERS|]^Show the cluster map +Show the map of the whole cluster. -This command produces essentially the same information as -SHOW/CONFIGURATION except that it shows all the duplication of -any routes that might be present It also uses a different format -which may not take up quite as much space if you don't have any -loops. +This shows the structure of the cluster that you are connected to. By +default it will only show the nodes that are known. By adding the keyword +USER to the command it will show all the users as well. -BE WARNED: the list that is returned can be VERY long +As there will be loops, you will see '...', this means that the information +is as printed earlier and that is a looped connection from here on. + +BE WARNED: the list that is returned can be VERY long (particularly +with the USER keyword) === 0^SHOW/NEWCONFIGURATION/NODE^Show all the nodes connected locally Show all the nodes connected to this node in the new format.