ctdb-docs: Move remaining test options to README

Test options do not belong in the user documentation.  Move them to
the README file in the tests/ subdirectory.

Signed-off-by: Martin Schwenke <martin@meltin.net>
Reviewed-by: Amitay Isaacs <amitay@gmail.com>

diff --git a/ctdb/doc/ctdbd.conf.5.xml b/ctdb/doc/ctdbd.conf.5.xml
index 13bcc3c9848eaa88d505b0d57f98182e40121915..d0b25c1eab2e5fafc6817bbfbc96d4a71a76d695 100644 (file)
--- a/ctdb/doc/ctdbd.conf.5.xml
+++ b/ctdb/doc/ctdbd.conf.5.xml
@@ -1499,78 +1499,6 @@ CTDB_PER_IP_ROUTING_TABLE_ID_HIGH=9000
 
   </refsect1>
 
-  <refsect1>
-    <title>
-      TEST OPTIONS
-    </title>
-
-    <para>
-      Variable in this section are for testing CTDB.  They should not
-      generally be needed.
-    </para>
-
-    <variablelist>
-
-      <varlistentry>
-       <term>CTDB_DEBUG_HUNG_SCRIPT_LOGFILE=<parameter>FILENAME</parameter></term>
-       <listitem>
-         <para>
-           FILENAME specifies where log messages should go when
-           debugging hung eventscripts.  This is a testing option.
-           See also <citetitle>CTDB_DEBUG_HUNG_SCRIPT</citetitle>.
-         </para>
-         <para>
-           No default.  Messages go to stdout/stderr and are logged
-           to the same place as other CTDB log messages.
-         </para>
-       </listitem>
-      </varlistentry>
-
-      <varlistentry>
-       <term>CTDB_SYS_ETCDIR=<parameter>DIRECTORY</parameter></term>
-       <listitem>
-         <para>
-           DIRECTORY containing system configuration files.  This is
-           used to provide alternate configuration when testing and
-           should not need to be changed from the default.
-         </para>
-         <para>
-           Default is <filename>/etc</filename>.
-         </para>
-       </listitem>
-      </varlistentry>
-
-      <varlistentry>
-       <term>CTDB_RUN_TIMEOUT_MONITOR=yes|no</term>
-       <listitem>
-         <para>
-           Whether CTDB should simulate timing out monitor events.
-           This uses the <filename>99.timeout</filename> eventscript.
-         </para>
-         <para>
-           Default is no.
-         </para>
-       </listitem>
-      </varlistentry>
-
-      <varlistentry>
-       <term>CTDB_VARDIR=<parameter>DIRECTORY</parameter></term>
-       <listitem>
-         <para>
-           DIRECTORY containing CTDB files that are modified at
-           runtime.
-         </para>
-         <para>
-           Defaults to <filename>/usr/local/var/lib/ctdb</filename>.
-         </para>
-       </listitem>
-      </varlistentry>
-
-    </variablelist>
-
-  </refsect1>
-
-
   <refsect1>
     <title>FILES</title>
 

diff --git a/ctdb/tests/README b/ctdb/tests/README
index c9eec4d48ba65e617ceadad444c9299960002538..1cbd7658daac701b224c8a03c9df19a743b079e2 100644 (file)
--- a/ctdb/tests/README
+++ b/ctdb/tests/README
@@ -137,3 +137,29 @@ Test and debugging variable options
             expense of some consistency checking
 
           * Disables real-time scheduling
+
+       CTDB_DEBUG_HUNG_SCRIPT_LOGFILE=FILENAME
+          FILENAME specifies where log messages should go when
+          debugging hung eventscripts. This is a testing option. See
+          also CTDB_DEBUG_HUNG_SCRIPT.
+
+          No default. Messages go to stdout/stderr and are logged to
+          the same place as other CTDB log messages.
+
+       CTDB_SYS_ETCDIR=DIRECTORY
+          DIRECTORY containing system configuration files. This is
+          used to provide alternate configuration when testing and
+          should not need to be changed from the default.
+
+          Default is /etc.
+
+       CTDB_RUN_TIMEOUT_MONITOR=yes|no
+          Whether CTDB should simulate timing out monitor
+          events. This uses the 99.timeout eventscript.
+
+          Default is no.
+
+       CTDB_VARDIR=DIRECTORY
+          DIRECTORY containing CTDB files that are modified at runtime.
+
+          Defaults to /usr/local/var/lib/ctdb.