It has a /etc/cron.daily/logrotate that exits early in favor of the systemd timer if systemd is present.
And the timer looks normal to me:
Sat 2019-11-09 00:00:00 UTC 15h left Fri 2019-11-08 00:00:30 UTC 8h ago logrotate.timer logrotate.service
It is using:
OnCalendar=daily
It has no config for onBoot or such.
I think that makes it trigger if the boot is the first activity of a given day per [1][2]
As Andreas said, Let's see what debian has to say on that MR.
It has a /etc/cron. daily/logrotate that exits early in favor of the systemd timer if systemd is present.
And the timer looks normal to me:
Sat 2019-11-09 00:00:00 UTC 15h left Fri 2019-11-08 00:00:30 UTC 8h ago logrotate.timer logrotate.service
It is using:
OnCalendar=daily
It has no config for onBoot or such.
I think that makes it trigger if the boot is the first activity of a given day per [1][2]
As Andreas said, Let's see what debian has to say on that MR.
[1]: https:/ /www.freedeskto p.org/software/ systemd/ man/systemd. time.html# Calendar% 20Events /www.freedeskto p.org/software/ systemd/ man/systemd. timer.html#
[2]: https:/