summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorHubert Plociniczak <hubert@lshift.net>2008-08-29 16:35:08 +0100
committerHubert Plociniczak <hubert@lshift.net>2008-08-29 16:35:08 +0100
commit95b30ad6494ff6d686d6f29afb4f243d2ffe070a (patch)
tree26996f28ebb8867bfc7eb7ad0e94ad9e77986ef3
parent32af9f32ba07f59d69f55f759c97696617e665cc (diff)
downloadrabbitmq-server-95b30ad6494ff6d686d6f29afb4f243d2ffe070a.tar.gz
More info about the behaviour of rotate_logs command
-rw-r--r--docs/rabbitmqctl.pod7
1 files changed, 5 insertions, 2 deletions
diff --git a/docs/rabbitmqctl.pod b/docs/rabbitmqctl.pod
index 6c84cbb1..3a33e20f 100644
--- a/docs/rabbitmqctl.pod
+++ b/docs/rabbitmqctl.pod
@@ -71,8 +71,11 @@ rotate_logs [suffix]
broker will attempt to append the current contents of the log file
to the file with the name composed of the original name and the
suffix. It will create a new file if such a file does not already
- exist. When no I<suffix> is specified, the log file is simply
- reopened; no rotation takes place.
+ exist. When no I<suffix> is specified, the empty log file is
+ simply created at the original location; no rotation takes place.
+ When an error occurs while appending the contents of the old log
+ file, operation behaves in the same way as if no I<suffix> was
+ specified.
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.