Github user dmabry commented on the issue:
https://github.com/apache/cloudstack/pull/1915
@ustcweizhou - Thanks for the +1 on cron.hourly move. From looking at the
code, it looks like non-redundant VRs are already moving to cron.hourly, but
vpcrouter isn't. In our case, we are using vpcrouter. I'm working on a PR
against master that will fix the vpcrouter flavor of this code. I'll link the
PR here when I'm done testing.
I'd also like to understand why you would prefer 'size' over 'maxsize'. I
know the difference is subtle and it really won't apply to anything that is set
to "hourly", but it could impact the dailys. In the VR case with a limited
/var/log partition size, I would think that the 'maxsize' option would be
preferable. It would keep run away log files in check by rotating them even
before their interval is reached.
```size size
Log files are rotated only if they grow bigger then size
bytes.
If size is followed by k, the size is assumed to be in
kilo-
bytes. If the M is used, the size is in megabytes, and if G
is
used, the size is in gigabytes. So size 100, size 100k,
size
100M and size 100G are all valid.
maxsize size
Log files are rotated when they grow bigger than size bytes
even before
the additionally specified time interval (daily, weekly,
monthly,
or yearly). The related size option is similar except
that it
is mutually exclusive with the time interval options, and it
causes
log files to be rotated without regard for the last rotation
time.
When maxsize is used, both the size and timestamp of a log
file are
considered.
```
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
