summaryrefslogtreecommitdiff
path: root/docs
diff options
context:
space:
mode:
authorDaniil Fedotov <daniil@rabbitmq.com>2017-03-30 17:51:24 +0100
committerGerhard Lazu <gerhard@rabbitmq.com>2017-03-30 17:51:24 +0100
commitd2eb76a52c913b6f181f24ba13b7c315e4e0af83 (patch)
treed3f3621438d723eeb7ad08d83dff83d88c66409e /docs
parentf9f5b6a7a04bfe9dedaebdcfd2acf474055d641d (diff)
downloadrabbitmq-server-git-d2eb76a52c913b6f181f24ba13b7c315e4e0af83.tar.gz
Remove remote node shutdown behaviour from rabbitmqctl man
It's not accurate, we didn't play the story Signed-off-by: Gerhard Lazu <gerhard@rabbitmq.com> [#142699191]
Diffstat (limited to 'docs')
-rw-r--r--docs/rabbitmqctl.1.xml1
1 files changed, 0 insertions, 1 deletions
diff --git a/docs/rabbitmqctl.1.xml b/docs/rabbitmqctl.1.xml
index ef313ab012..f9d5f17511 100644
--- a/docs/rabbitmqctl.1.xml
+++ b/docs/rabbitmqctl.1.xml
@@ -148,7 +148,6 @@
Unlike the stop command, the shutdown command:
* does not require a pid_file to wait for the Erlang process to exit
* if RabbitMQ node is not running, it will return a non-zero exit code
- * it will refuse to stop a remote RabbitMQ node and return a non-zero exit code
</para>
<para role="example-prefix">For example:</para>
<screen role="example">rabbitmqctl shutdown</screen>