On 2015-05-20 21:34, Felix Miata wrote:
Carlos E. R. composed on 2015-05-20 20:33 (UTC+0200):
Andrei Borzenkov wrote:
logrotate.timer has 12 hours accuracy with daily run which means system must be on some time between 00:00 and 12:00. The possible problem for those who *updated* to 13.2 was that systemd.timer did not get activated on update. This is unfortunate situation that was discussed on systemd list but I do not think any resolution is available - there is no way to know whether unit is not active because it simply was not activated or because it was intentionally not or deactivated. So even though defaults are changed to enable service, these defaults are not reapplied on update.
Then Felix has to check that :-)
Check what how? My TW test systems are often run between 00:00 and 05:00, infrequently between 05:00 and 12:00, and usually less than an hour at a time.
Check that the timer is enabled. I understand the name is "systemd.timer". -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar)