add sh/rbn command

[spider.git] / cmd / Commands_en.hlp

diff --git a/cmd/Commands_en.hlp b/cmd/Commands_en.hlp
index a44426a38cb53ad7c9d3841b52b0cbf9589e6cd3..c6e38efcbb2e66d753ac770190af1f52efc9cab3 100644 (file)
--- a/cmd/Commands_en.hlp
+++ b/cmd/Commands_en.hlp
@@ -1120,10 +1120,6 @@ is a good indication of the quality of the link.  The actual time
 it takes is output to the console in seconds.
 Any visible cluster node can be PINGed.
 
-=== 9^RBN^The Reverse Beacon or Skimmer System
-Please read the document /spider/RBN.mojo. This has the latest information
-about RBN/Skimmer setup.
-
 === 0^RBN^The Reverse Beacon or Skimmer System
 DXSpider now has the ability to show spots from the Reverse Beacon Network
 or "Skimmers", if your sysop has enabled the feed(s) (and has the bandwidth
@@ -2066,16 +2062,12 @@ Conflicts with: SET/DXCQ, SET/DXITU
 
 Do a STAT/USER to see which flags you have set if you are confused.  
 
-=== 9^SET/WANTRBN^<call> [category ..]^Allow (some) RBN/Skimmer spots
-=== 9^SET/SKIMMER^<call> [category ..]^Allow (some) RBN/Skimmer spots
-This sysop only command allows you to set a user's RBN/Skimmer for them.
-
-It's also good for resetting a user's flags if they get into a muddle.
-
 === 0^SET/WANTRBN^[category ..]^Allow (some) RBN/Skimmer spots
 === 0^SET/SKIMMER^[category ..]^Allow (some) RBN/Skimmer spotsT
 === 0^UNSET/WANTRBN^Stop all RBN/Skimmer spots
 === 0^UNSET/SKIMMER^Stop all RBN/Skimmer spots
+=== 9^SET/WANTRBN^<call> [category ..]^Allow (some) RBN/Skimmer spots
+=== 9^SET/SKIMMER^<call> [category ..]^Allow (some) RBN/Skimmer spots
 This command allows curated Reverse Beacon Spots to come out on your
 terminal (or not).
 
@@ -2125,6 +2117,10 @@ The RBN filters completely override any spot filters for these
 spots. But the spot filters will continue to filter "manual" spots as
 before.
 
+NOTE: Filters and this command CAN interact with each other. If you
+don't get the results that you expect, check your filters with
+SHOW/FILTER.
+
 Please see HELP RBN for an explanation of the spot format. It is NOT
 the same as one would get directly from the RBN/Skimmers. But it is
 recommended that you SET/DXCQ and UNSET/DXITU and UNSET/DXGRID (unless
@@ -2638,9 +2634,10 @@ with the USER keyword)
 Show all the nodes connected to this node in the new format.
 
 === 1^SHOW/NODE [<callsign> ...]^Show the type and version number of nodes
+=== 1^SHOW/NODE ALL^Show the type,version number of ALL known nodes
 Show the type and version (if connected) of the nodes specified on the
 command line. If no callsigns are specified then a sorted list of all
-the non-user callsigns known to the system will be displayed.
+the non-user callsigns connected to node will be displayed.
 
 === 0^SHOW/PREFIX <callsign>^Interrogate the prefix database 
 This command takes the <callsign> (which can be a full or partial 
@@ -2708,6 +2705,16 @@ connected. It is a sort of inverse sh/config.
 
  sh/route n2tly
 
+=== 1^SHOW/RBN [<callsign> ...]^Show which connected users want RBN spots
+=== 1^SHOW/RBN ALL^Show ALL users that want RBN spots
+Show a list of the users that want RBN spots of any the callsigns
+specified on the command line. If no callsigns are specified then a
+sorted list of all connected users wanting RBN spots will be displayed
+
+SHOW/RBN ALL
+
+will go through the user file and display ALL users that want RBN spots.
+
 === 9^SHOW/RCMD [<n>][<from>-<to>][<call>] ...^Show log of rcmds
 Show the rcmds that have come in and their replies.