Erratic behaviour when mythtv-backend starts before ntp updates and hardware clock is unsynced

[onthelist@…]

Due to running ACPI startup/shutdown configuration, my hardware clock does not get automatically saved and after a few weeks reports dramatically inaccurate times on startup, before ntp has updated.

I have just been manually setting hardware clock and restarting for a long time as I thought it was probably my motherboard. The mythtv I set up for my dad exhibits the same fault except less frequently.

If the clock has drifted into the future, upcoming recordings vanish and cannot be reprogrammed due to database saying the have been recorded or failed. If the clock drifts into the past I get loads of empty recordings, and sometimes a non-empty one if the time happens to coincide. These are always the same set of recordings and not all past recordings.

I can't find anyone else describing this behaviour, but it seems repeatable to me.

My solution is to put

exec /usr/sbin/ntp-wait

into the upstart pre-start script after it checks for mysql and that seems to be working.

Perhaps this is a useful (or at least not harmful) to add by default.

[onthelist@…]

patch

[Frank Phillips <fphillips81@…>]

Patch is for a file that Mythbuntu distributes in it's mythtv-backend package, wrong project. Close it or move to packaging.

[Raymond Wagner]

Technically downstream. I'll forward this to Mythbuntu's attention.