add sh/cmd_cache

[spider.git] / cmd / Commands_en.hlp

diff --git a/cmd/Commands_en.hlp b/cmd/Commands_en.hlp
index b1fdb80e26a3ef82e1abd801d7b2ce7da62cdcee..66f6db9b8fe27df9cb7bf9bf073ccb206a050f7c 100644 (file)
--- a/cmd/Commands_en.hlp
+++ b/cmd/Commands_en.hlp
@@ -915,7 +915,8 @@ will automatially be picked up by the cluster program. Sometimes it
 can get confused 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.
+was just after a cluster restart. To see what is in the command cache
+see SHOW/CMD_CACHE.
 
 === 9^LOAD/FORWARD^Reload the msg forwarding routing table
 Reload the /spider/msg/forward.pl file if you have changed it
@@ -1863,6 +1864,15 @@ occurred whilst you were away. SHOW/CHAT on its own will show data for
 all groups. If you use a group name then it will show only chat for
 that group.
 
+=== 9^SHOW/CMD_CACHE^Show the real source path of commands
+It is possible in DXSpider to define local versions of commands.
+Sometimes one forgets that one has these. This command will show you
+the source path where the node is getting each one of its commands.
+
+If you find a local command that you don't want then then simply
+delete it, run LOAD/CMD_CACHE to clear out the command cache and
+try again. You will now be using the standard version.
+
 === 0^SHOW/CONFIGURATION [<node>]^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.