+++ This bug was initially created as a clone of Bug #1177286 +++
There is no need for logrotate to use cron.daily. The same can be accomplished with a systemd timer unit.
--- Additional comment from Jan Kaluža on 2015-07-23 03:12:45 EDT ---
That would be against Packaging Guidelines:
Packages which do not already depend or require systemd must not use timer units but instead depend and have requirement on crontabs, to avoid introducing unnecessary new dependencies on systemd directly.
Closing as WONTFIX.
--- Additional comment from Theodore Cowan on 2018-11-30 14:03:16 EST ---
It's time to re-evaluate this. crond isn't even installed on cloud images of Fedora 28+ and systemd is ubiquitous.
logrotate should take on cronie as a dependency or user systemd-timer.
Debian/Ubuntu has reportedly already made this change.
There is currently a pull request under review to address this:
As implemented today, this also means that logrotate isn't enabled on new installs; was that intentional?
Yes, it is a trade-off. logrotate used to unconditionally install the cron hook but it took effect only when cron was actually installed and enabled. We cannot use this logic with systemd any more because systemd is always installed. So we made our best to preserve the behavior on updates but the timer is not enabled on fresh Fedora installations now.
Are you suggesting that we enable logrotate timer by default whenever logrotate is installed?
There can be Fedora installations that include logrotate but trigger it by other means (or do not trigger it at all).
In any case, the first chance when we can safely change this is Fedora 32 I am afraid.