Dave Howorth wrote:
On Sat, 07 Jul 2018 10:24:21 +0200 Per Jessen <per@computer.org> wrote:
Carlos E. R. wrote:
As you can see, it did not run since January, when I updated the machine to Leap 42.3
It is supposed to be a systemd timer now, and it was disabled.
Yes, on an upgrade it is not enabled. It is a well-known issue, to me anyway :-) I think it's been mentioned a few times before.
Hmm, it's not well-known to me.
Yeah, I wanted to be careful - I'm not sure if it's the release notes either. I searched bugzilla: https://bugzilla.opensuse.org/show_bug.cgi?id=1064303 https://bugzilla.opensuse.org/show_bug.cgi?id=908279
I too see that I have a whole bunch of messages-*.xz files with the last one being at 20180111 and a single large messages file, so I presume I have the same problem.
Sounds much like it.
I don't understand why an upgrade should stop a system process from working. If it was migrated to a new mechanism then the migration should have migrated the settings.
I agree. On a new installation it would have, courtesy of systemd presets (or whatever it is called).
[snip]
What is missing? Should I also enable the service? start the timer and/or the service?
Unless you have rebooted, you have to start the timer, definitely.
What timer is this? There's only one systemd timer listed on my machine.
logrotate.timer -- Per Jessen, Zürich (21.8°C) http://www.cloudsuisse.com/ - your owncloud, hosted in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org