summaryrefslogtreecommitdiff
path: root/docs
diff options
context:
space:
mode:
authorEmile Joubert <emile@rabbitmq.com>2011-08-17 14:24:52 +0100
committerEmile Joubert <emile@rabbitmq.com>2011-08-17 14:24:52 +0100
commitc97dbfd77b8e7edc4e4e26fef19c47f14f41a521 (patch)
treef9ad4f0c764994188dd9869c00524cc5b6c9e1cc /docs
parent0773289662059115ceb537fd9ca96f5f93bf3cba (diff)
downloadrabbitmq-server-git-c97dbfd77b8e7edc4e4e26fef19c47f14f41a521.tar.gz
Detail about units of numbers reported by 'rabbitmqctl status'
Diffstat (limited to 'docs')
-rw-r--r--docs/rabbitmqctl.1.xml5
1 files changed, 3 insertions, 2 deletions
diff --git a/docs/rabbitmqctl.1.xml b/docs/rabbitmqctl.1.xml
index a92a105674..f0e1dc38c1 100644
--- a/docs/rabbitmqctl.1.xml
+++ b/docs/rabbitmqctl.1.xml
@@ -1300,8 +1300,9 @@
In this context <varname>vm_memory_high_watermark</varname>
indicates to the fraction of memory at which flow control is
triggered. <varname>vm_memory_limit</varname> refers to the
- absolute memory threshhold (in bytes) at which flow control
- is triggered. (See the <command>cluster_status</command>
+ absolute memory threshhold at which flow control is triggered.
+ The unit of this number and those listed in the <varname>memory</varname>
+ section is bytes. (See the <command>cluster_status</command>
command to find out which nodes are clustered and running.)
</para>
<para role="example-prefix">For example:</para>