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>

1 files changed, 52 insertions, 52 deletions

diff --git a/ctdb/doc/ctdbd.1.xml b/ctdb/doc/ctdbd.1.xml
index 4f6d482da90..6d20f595e6e 100644
--- a/ctdb/doc/ctdbd.1.xml
+++ b/ctdb/doc/ctdbd.1.xml
@@ -107,6 +107,18 @@
       </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>
 	  <para>
@@ -265,6 +277,30 @@
       </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>
 	  <para>
@@ -301,6 +337,22 @@
       </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>
 	  <para>
@@ -371,18 +423,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>
 	  <para>
@@ -394,46 +434,6 @@
       </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>
 	  <para>