diff options
| author | Alexey Lebedeff <alebedev@mirantis.com> | 2016-01-12 14:31:45 +0300 |
|---|---|---|
| committer | Alexey Lebedeff <alebedev@mirantis.com> | 2016-01-12 17:03:19 +0300 |
| commit | dbbe3d6e473fcfaa725e7aa0dda10601b63b9c27 (patch) | |
| tree | 32200abb039cb773039c3ae2ba3573eeaa649b61 /docs | |
| parent | 1dcaad8f4859a04d2e6e427e9aaf4e948bdd417e (diff) | |
| download | rabbitmq-server-git-dbbe3d6e473fcfaa725e7aa0dda10601b63b9c27.tar.gz | |
Fix 'rabbitmqctl rotate_logs' behaviour
When 'rabbitmqctl rotate_logs' is called without any parameters, it
clears logs unconditionally. And given that this form is used in
logrotate config files, this could result in data loss.
This could be reproduced with following scenario:
1) 'max_size' is set globally in lograte config
2) One of two rabbitmq logs is greater than that limit
3) Daily logrotate run was already performed today, and now we
are calling it manually. In this case logrotate will copy only file
that is bigger than max_size, but 'rabbitmqctl rotate_logs' will
clear both of them - leading to data loss.
Diffstat (limited to 'docs')
| -rw-r--r-- | docs/rabbitmqctl.1.xml | 7 |
1 files changed, 3 insertions, 4 deletions
diff --git a/docs/rabbitmqctl.1.xml b/docs/rabbitmqctl.1.xml index fb4959b276..c9b699d634 100644 --- a/docs/rabbitmqctl.1.xml +++ b/docs/rabbitmqctl.1.xml @@ -275,10 +275,9 @@ suffixed files. </para> <para> - When the target files do not exist they are created. - When no <option>suffix</option> is specified, the empty - log files are simply created at the original location; - no rotation takes place. + When the target files do not exist they are created. When + no <option>suffix</option> is specified, no rotation takes + place - log files are just re-opened. </para> <para role="example-prefix">For example:</para> <screen role="example">rabbitmqctl rotate_logs .1</screen> |