diff options
| author | Daniil Fedotov <daniil@rabbitmq.com> | 2017-03-30 11:31:22 +0100 |
|---|---|---|
| committer | Gerhard Lazu <gerhard@rabbitmq.com> | 2017-03-30 11:31:22 +0100 |
| commit | 0f47ca0424e0b80f7c33b6a92c5fd6c7ccff9c45 (patch) | |
| tree | 9fd8e818aa1260807a5bf767027b7cd9d63d7835 /docs | |
| parent | e607e57f6675298486c10c621fc88661146fbf79 (diff) | |
| download | rabbitmq-server-git-0f47ca0424e0b80f7c33b6a92c5fd6c7ccff9c45.tar.gz | |
Add shutdown command to rabbitmqctl documentation
[#142699191]
Signed-off-by: Gerhard Lazu <gerhard@rabbitmq.com>
Diffstat (limited to 'docs')
| -rw-r--r-- | docs/rabbitmqctl.1.xml | 23 |
1 files changed, 23 insertions, 0 deletions
diff --git a/docs/rabbitmqctl.1.xml b/docs/rabbitmqctl.1.xml index 0465db02fd..ef313ab012 100644 --- a/docs/rabbitmqctl.1.xml +++ b/docs/rabbitmqctl.1.xml @@ -135,6 +135,29 @@ </listitem> </varlistentry> + <varlistentry> + <term><cmdsynopsis><command>shutdown</command></cmdsynopsis></term> + <listitem> + <para> + Shuts down the Erlang process on which RabbitMQ is running. The + command is blocking and will return after the Erlang process + exits. If RabbitMQ fails to stop, it will return a non-zero exit + code. + </para> + <para> + 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> + <para role="example"> + This command shuts down the Erlang process on which RabbitMQ is running. + </para> + </listitem> + </varlistentry> + <varlistentry id="stop_app"> <term><cmdsynopsis><command>stop_app</command></cmdsynopsis></term> <listitem> |