summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorSimon MacMullen <simon@rabbitmq.com>2011-06-03 12:17:58 +0100
committerSimon MacMullen <simon@rabbitmq.com>2011-06-03 12:17:58 +0100
commita00dc3cc5975549198ddc91efc461fb76727beb8 (patch)
treee5c830ed4f0b9eed039ae81768c7586dafbe0b05
parent90d224ee4539c4b3209a9528afac5fda823eb9a3 (diff)
downloadrabbitmq-server-a00dc3cc5975549198ddc91efc461fb76727beb8.tar.gz
Reformat, rephrase the "diagnostic information" para and move it to the top since it always applies.
-rw-r--r--docs/rabbitmqctl.1.xml19
1 files changed, 10 insertions, 9 deletions
diff --git a/docs/rabbitmqctl.1.xml b/docs/rabbitmqctl.1.xml
index c2434770..51754895 100644
--- a/docs/rabbitmqctl.1.xml
+++ b/docs/rabbitmqctl.1.xml
@@ -59,6 +59,11 @@
RabbitMQ broker. It performs all actions by connecting to one of the
broker's nodes.
</para>
+ <para>
+ Diagnostic information is displayed if the broker was not
+ running, could not be reached, or rejected the connection due to
+ mismatching Erlang cookies.
+ </para>
</refsect1>
<refsect1>
@@ -183,15 +188,11 @@
<term><cmdsynopsis><command>status</command></cmdsynopsis></term>
<listitem>
<para>
- Displays broker status information such as the running applications
- on the current Erlang node, RabbitMQ and Erlang versions and OS name.
- (See the <command>cluster_status</command> command to find out which
- nodes are clustered and running.)
- </para>
- <para>
- Diagnostic information is displayed if the broker is not running,
- cannot be reached, or does not permit queries due to security
- constraints.
+ Displays broker status information such as the running
+ applications on the current Erlang node, RabbitMQ and
+ Erlang versions and OS name. (See
+ the <command>cluster_status</command> command to find
+ out which nodes are clustered and running.)
</para>
<para role="example-prefix">For example:</para>
<screen role="example">rabbitmqctl status</screen>