mirror of
https://gitlab.com/libvirt/libvirt.git
synced 2024-12-28 08:35:22 +00:00
975b004d07
The virtlogd config is set to rollover logs every 2 MB. Normally a logrotate config file is also installed to handle cases where virtlogd is disabled. This is set to rollover weekly with no size constraint. As a result logrotate can interfere with virtlogd's, rolling over files that virtlogd has already taken care of. This changes logrotate configs to rollover based on a max size constraint of 2 MB + 1 byte. When virtlogd is running the log files will never get this large, making logrotate a no-op. If the user changes the size in virtlogd's config to something larger, they are responsible for also changing the logrotate config suitably. The LXC/libxl drivers don't use virtlogd, but there logrotate config is altered to match the QEMU driver config, for the sake of consistency. Reviewed-by: Jim Fehlig <jfehlig@suse.com> Signed-off-by: Daniel P. Berrangé <berrange@redhat.com>
17 lines
551 B
Plaintext
17 lines
551 B
Plaintext
@localstatedir@/log/libvirt/qemu/*.log {
|
|
# The QEMU driver is configured to use virtlogd by
|
|
# default, which will perform log rollover.
|
|
# This logrotate config is still installed for cases
|
|
# where the user has switched off virtlogd.
|
|
#
|
|
# If virtlogd is active, ensure that size here is
|
|
# larger than 'max_size' in the virtlogd config
|
|
# so that logrotate becomes a no-op
|
|
size 2097153
|
|
missingok
|
|
rotate 4
|
|
compress
|
|
delaycompress
|
|
copytruncate
|
|
}
|