On 3/18/20 8:04 AM, Kamil Dudka wrote:
logrotate is a utility designed to simplify the administration of log files on a system which generates a lot of log files. It used to be triggered by cron. The cron hook was unconditionally installed with logrotate but it took effect only if a cron daemon was installed.
Starting with Fedora 30, logrotate is triggered by a systemd timer instead. In order to make updates smoother, the timer was enabled on updates in case a cron daemon was configured on the system.
The timer is currently not enabled on fresh installs to avoid surprises (such as data lost) on systems where logrotate is installed but not actually used. logrotate can also be triggered independently of systemd/cron and can be even run by non-privileged users to rotate logs they have access to.
Some people think that the logrotate timer should be enabled by default on all systems where the logrotate package is installed:
https://bugzilla.redhat.com/1655153#c4
Do you think it would be a good idea?
I chimed in in the ticket too, but +1 from me.
I guess it would be worth analyzing the problem space a bit:
- in the past how many people do we think had logrotate installed and not cron? - what are the worst case scenarios if logrotate.timer defaults to off? - what are the worst case scenarios if logrotate.time defaults to on?
Dusty