ctdb-docs: Move some ctdbd options out of the debug section

ctdbd -i might be useful with systemd or similar, so should be
documented.

--nosetsched and --script-log-level options are valid user-level
options.

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

diff --git a/ctdb/doc/ctdbd.1.xml b/ctdb/doc/ctdbd.1.xml
index 4f6d482da907eb18da6fbc3ad3720d112902d6b0..6d20f595e6ed7bd78455a8b57af2e4066da744c0 100644 (file)
--- a/ctdb/doc/ctdbd.1.xml
+++ b/ctdb/doc/ctdbd.1.xml
@@ -106,6 +106,18 @@
        </listitem>
       </varlistentry>
 
+      <varlistentry>
+       <term>-i, --interactive</term>
+       <listitem>
+         <para>
+           Enable interactive mode.  This will make ctdbd run in the
+           foreground and not detach from the terminal.  By default
+           ctdbd will detach itself and run in the background as a
+           daemon.
+         </para>
+       </listitem>
+      </varlistentry>
+
       <varlistentry>
        <term>--listen=<parameter>IPADDR</parameter></term>
        <listitem>
@@ -264,6 +276,30 @@
        </listitem>
       </varlistentry>
 
+      <varlistentry>
+       <term>--nosetsched</term>
+       <listitem>
+         <para>
+           Normally ctdbd will change its scheduler to run as a
+           real-time process. This is the default mode for a normal
+           ctdbd operation to gurarantee that ctdbd always gets the CPU
+           cycles that it needs.
+         </para>
+         <para>
+           This option is used to tell ctdbd to
+           <emphasis>not</emphasis> run as a real-time process and
+           instead run ctdbd as a normal userspace process.  This can
+           be used on a platform where real-time scheduling is not
+           supported.
+         </para>
+         <para>
+           This is also useful for debugging and when you want to run
+           ctdbd under valgrind or gdb. (You don't want to attach
+           valgrind or gdb to a real-time process.)
+         </para>
+       </listitem>
+      </varlistentry>
+
       <varlistentry>
        <term>--notification-script=<parameter>FILENAME</parameter></term>
        <listitem>
@@ -300,6 +336,22 @@
        </listitem>
       </varlistentry>
 
+      <varlistentry>
+       <term>--script-log-level=<parameter>DEBUGLEVEL</parameter></term>
+       <listitem>
+         <para>
+           This option sets the debug level of event script output to
+           DEBUGLEVEL.  The default is ERR.
+         </para>
+         <para>
+           See the <citetitle>DEBUG LEVELS</citetitle> section in
+           <citerefentry><refentrytitle>ctdb</refentrytitle>
+           <manvolnum>7</manvolnum></citerefentry> for more
+           information.
+         </para>
+       </listitem>
+      </varlistentry>
+
       <varlistentry>
        <term>--start-as-disabled</term>
        <listitem>
@@ -370,18 +422,6 @@
 
     <variablelist>
 
-      <varlistentry>
-       <term>-i, --interactive</term>
-       <listitem>
-         <para>
-           Enable interactive mode.  This will make ctdbd run in the
-           foreground and not detach from the terminal.  By default
-           ctdbd will detach itself and run in the background as a
-           daemon.
-         </para>
-       </listitem>
-      </varlistentry>
-
       <varlistentry>
        <term>--nopublicipcheck</term>
        <listitem>
@@ -393,46 +433,6 @@
        </listitem>
       </varlistentry>
 
-      <varlistentry>
-       <term>--nosetsched</term>
-       <listitem>
-         <para>
-           This is a debugging option. This option is only used when
-           debugging ctdbd.
-         </para>
-         <para>
-           Normally ctdbd will change its scheduler to run as a
-           real-time process. This is the default mode for a normal
-           ctdbd operation to gurarantee that ctdbd always gets the CPU
-           cycles that it needs.
-         </para>
-         <para>
-           This option is used to tell ctdbd to
-           <emphasis>not</emphasis> run as a real-time process and
-           instead run ctdbd as a normal userspace process.  This is
-           useful for debugging and when you want to run ctdbd under
-           valgrind or gdb. (You don't want to attach valgrind or gdb
-           to a real-time process.)
-         </para>
-       </listitem>
-      </varlistentry>
-
-      <varlistentry>
-       <term>--script-log-level=<parameter>DEBUGLEVEL</parameter></term>
-       <listitem>
-         <para>
-           This option sets the debug level of event script output to
-           DEBUGLEVEL.  The default is ERR.
-         </para>
-         <para>
-           See the <citetitle>DEBUG LEVELS</citetitle> section in
-           <citerefentry><refentrytitle>ctdb</refentrytitle>
-           <manvolnum>7</manvolnum></citerefentry> for more
-           information.
-         </para>
-       </listitem>
-      </varlistentry>
-
       <varlistentry>
        <term>--sloppy-start</term>
        <listitem>