On 24.06.2022 15:21, Felix Miata wrote:
^^^^ Re: [support][TW] logrotate zypper.log
Andrei Borzenkov composed on 2022-06-24 08:04 (UTC-0400)
Felix Miata wrote:
On a PC that sees only occasional use, I'm using what appears to be default files in /etc/logrotate.d/, timestamped Oct 2018. zypper.lr there specifies size 10M. After a reboot with its size exceeding 10M, e.g. 25,000K, it remains the same size until some later unknown time or number of boots when it finally gets rotated and shrunk. Why? How can rotating and compressing it be made to happen when on boot it is found to exceed the configured limit. Is it simply that logrotate needs to be forced to run other than via a daily cron job? If yes, what is a good method? If not, how?
You could start with telling you openSUSE version.
It changes most days: 20220623, 20220622, 20220619, 20220618, 20220617....
On Tumbleweed logrotate is controlled by logrotate.timer which by default runs every day and has Persistent option which means, if it missed run (because system was not up) it should immediately activate service during boot. Check logrotate.timer (is it enabled, when was the last time it run etc).