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.

0 files changed, 0 insertions, 0 deletions