[Xen-devel] [PATCH 3/3] docs: document CONTROL command of xenstore protocol

[Juergen Gross <jgross@xxxxxxxx>]

The CONTROL command (former DEBUG command) isn't specified in the
xenstore protocol doc. Add it.

Signed-off-by: Juergen Gross <jgross@xxxxxxxx>
---
 docs/misc/xenstore.txt | 29 +++++++++++++++++++++++------
 1 file changed, 23 insertions(+), 6 deletions(-)

diff --git a/docs/misc/xenstore.txt b/docs/misc/xenstore.txt
index fd38d781e2..074650f144 100644
--- a/docs/misc/xenstore.txt
+++ b/docs/misc/xenstore.txt
@@ -319,12 +319,29 @@ SET_TARGET                <domid>|<tdomid>|
 
 ---------- Miscellaneous ----------
 
-DEBUG                  print|<string>|??           sends <string> to debug log
-DEBUG                  print|<thing-with-no-nul>   EINVAL
-DEBUG                  check|??                    checks xenstored innards
-DEBUG                  <anything-else|>            no-op (future extension)
+CONTROL                        <command>|[<parameters>|]
+       Send a control command <command> with optional parameters
+       (<parameters>) to Xenstore daemon. <command> support is
+       implementation specific and might change in future.
 
-       These requests should not generally be used and may be
-       withdrawn in the future.
+       Current commands are:
+       check
+               checks xenstored innards
+       log|on
+               turn xenstore logging on
+       log|off
+               turn xenstore logging off
+       logfile|<file-name>
+               log to specified file
+       memreport|[<file-name>]
+               print memory statistics to logfile (no <file-name>
+               specified) or to specific file
+       print|<string>
+               print <string> to syslog (xenstore runs as daemon) or
+               to console (xenstore runs as stubdom)
+       help                    <supported-commands>
+               return list of supported commands for CONTROL
 
+DEBUG
+       Deprecated, now named CONTROL
 
-- 
2.12.0


_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxx
https://lists.xen.org/xen-devel