diff options
| author | Matthias Radestock <matthias@rabbitmq.com> | 2011-09-05 16:48:56 +0100 |
|---|---|---|
| committer | Matthias Radestock <matthias@rabbitmq.com> | 2011-09-05 16:48:56 +0100 |
| commit | db44b9327945acb82f518ac182854aa87fa1f282 (patch) | |
| tree | 516ed1311ec27fadad1998b555cc6cf0480c3341 /docs | |
| parent | c74d6ceb4d578d741aa71f7783f07cc0f8b26c4b (diff) | |
| download | rabbitmq-server-git-db44b9327945acb82f518ac182854aa87fa1f282.tar.gz | |
cosmetic: don't delve into details of what's in the output of 'status'
Diffstat (limited to 'docs')
| -rw-r--r-- | docs/rabbitmqctl.1.xml | 11 |
1 files changed, 3 insertions, 8 deletions
diff --git a/docs/rabbitmqctl.1.xml b/docs/rabbitmqctl.1.xml index 29d9032b97..9305d68971 100644 --- a/docs/rabbitmqctl.1.xml +++ b/docs/rabbitmqctl.1.xml @@ -1268,14 +1268,9 @@ <para> Displays broker status information such as the running applications on the current Erlang node, RabbitMQ and - Erlang versions, OS name and memory statistics. - In this context <varname>vm_memory_high_watermark</varname> - indicates the fraction of memory at which flow control is - triggered. <varname>vm_memory_limit</varname> refers to the - 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.) + Erlang versions, OS name and memory statistics. (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> |