Add logrotate configuration to rotate /var/log/messages #89
Conversation
Could somebody write a little more to the motivation? Current Suggestion: Rotate yearly, and do not compress. |
Motivation: Rotating logs is a good thing. Monthly rotation was the result of a lengthy, hard and very emotional discussion. Blood has been shed and wounds are healing. Please do not reach out for salt. Compression is a waste of CPU. |
Yes. https://github.com/logrotate/logrotate/tree/master/examples
Yes. And it takes ages to grep something. And an ever-growing /var/log/messages can not be deduplicated on the backup storage, unlike read-only monthly archives. |
|
force-pushed, just because I didn't forgot ti commit my last chnage ( rotate 11 -> rotate 12 ) |
Add logrotate.conf, logrotate.service and logrotate.timer to rotate and purge /var/log/messages. With this logrotate.conf, we rotate every month and keep 12 rotated files. So on Jun 1, 2019, /var/log/messages is rotated to /var/log/messages.2019-05 and /var/log/messages.2018-05 would be deleted, if it existed.
|
So one voice not to compress and no vetos. I merge w/o compression. Let's see, what happens on Jun 1st. |
PR open for discussion of the policy, too. Don't merge, until everyone had a chance to throw in his 5 cent.