Bug 5373

Summary: Fixes for mythdb-optimize.timer
Product: Fedora Reporter: Stefan Becker <chemobejk>
Component: mythtvAssignee: Richard <hobbes1069>
Status: RESOLVED FIXED    
Severity: normal CC: jarod
Priority: P1    
Version: f30   
Hardware: x86_64   
OS: GNU/Linux   
namespace:

Description Stefan Becker 2019-08-31 20:51:05 CEST
Looking at git HEAD:

    https://pkgs.rpmfusion.org/cgit/free/mythtv.git/tree/mythdb-optimize.timer?id=f25cca2deb50bed76036c5b5dc7be9d1de0c2829

The Install section is broken, therefore the timer is never started even when it is enabled. The section should read:

    [Install]
    WantedBy=timers.target

The timer currently only works for systems that are permanently running. This can easily be fixed by adding one line to the Timer section:

    [Timer]
    OnCalendar=daily
    Persistent=yes
Comment 1 Richard 2019-08-31 21:01:37 CEST
Thanks for the report, I have made the correction to timers.target.

However, the downside to persistence is that it may do a "catch up" run at a very bad time...

Perhaps WakeSystem would be a better option?
Comment 2 Stefan Becker 2019-08-31 21:15:34 CEST
WakeSystem only wakes up a system from suspension. My system does a shutdown after programming the ACPI wakeup timer, so it won't work.
Comment 3 Stefan Becker 2019-08-31 21:42:07 CEST
... and of course WakeSystem would clash with the wakeup events programmed by mythtv. So in short: bad idea :-)
Comment 4 Richard 2019-09-04 20:44:26 CEST
Bah, one thing I wish systemd would do is mesh the system and user unit files, i.e., you would only put what you want to override/add in /etc/systemd/system instead of it being all or nothing.
Comment 5 Richard 2019-09-04 20:59:40 CEST
I went ahead and committed the persistence option as well... it was about time for new fixes builds so I'll work on those over the next day or so.
Comment 6 Richard 2019-09-10 14:47:02 CEST
Packages for f32 have been built and f31/30 are building now.