summaryrefslogtreecommitdiff
path: root/docs
diff options
context:
space:
mode:
authorHubert Plociniczak <hubert@lshift.net>2008-08-14 14:26:44 +0100
committerHubert Plociniczak <hubert@lshift.net>2008-08-14 14:26:44 +0100
commit48e0f08f2f2c264bba63f7c3718c9a9b382efa1e (patch)
tree3d1bf8b4296d75385b63aca49d7d17547b663c3a /docs
parent68b6ccc11cdae470c04067625dd318f6cb6b1f05 (diff)
downloadrabbitmq-server-48e0f08f2f2c264bba63f7c3718c9a9b382efa1e.tar.gz
Added reopen_logs command to man pages
Diffstat (limited to 'docs')
-rw-r--r--docs/rabbitmqctl.pod5
1 files changed, 5 insertions, 0 deletions
diff --git a/docs/rabbitmqctl.pod b/docs/rabbitmqctl.pod
index db31b621..ebe0cd43 100644
--- a/docs/rabbitmqctl.pod
+++ b/docs/rabbitmqctl.pod
@@ -66,6 +66,11 @@ force_reset
It should only be used as a last resort if the database or cluster
configuration has been corrupted.
+reopen_logs
+ instruct the RabbitMQ node to close and reopen the log files.
+ This command might be helpful when you are e.g. writing your own
+ logrotate script and you do not want to restart the RabbitMQ node.
+
cluster I<clusternode> ...
instruct the node to become member of a cluster with the specified
nodes determined by I<clusternode> option(s).