[mythtv-users] can't set wakealarm

[Stephen Worthington]

On Fri, 10 Aug 2018 21:43:30 -0700, you wrote:

>On 08/10/2018 09:04 PM, Stephen Worthington wrote:
>> On Fri, 10 Aug 2018 19:56:39 -0700, you wrote:
>>
>>> On 08/10/2018 06:59 AM, Peter Bennett wrote:
>>>>
>>>> On 08/10/2018 12:39 AM, Douglas Peale wrote:
>>>>> On 08/09/2018 09:34 PM, Douglas Peale wrote:
>>>>>> I was going to update the wiki with that change, but I found someone beat me too it.
>>>>>>
>>>>>>
>>>>> Hmm, there were two copies of those instructions in the wiki, I was following the second set. The first set had the sudo bash
>>>>> stuff in it, the second set did not.
>>>>> The page has not been modified since 2016.
>>>>>
>>>>>
>>>> Newer versions of Ubuntu, and other distributions,  have systemd. If you have Linux with systemd you need to use a command
>>>> like this
>>>>
>>>> sudo rtcwake -m no -a -t $biostime
>>>>
>>>> Look at the man page for rtcwake. Also see the wiki page at https://www.mythtv.org/wiki/ACPI_Wakeup#Ubuntu
>>>>
>>>> Peter
>>> The problem is not systemd. MythTV was working fine with Mint 18 through 18.3, and those versions also had systemd.
>>>
>>> I have finally identified the problem. MythTV does not call setwakeup.sh if it does not find anything to record.
>>>
>>> This is a problem because if nothing else wakes up the backend system, mythfilldatabase will not be run, and the system will not
>>> notice new items in the schedule because it has an out of date schedule.
>>>
>>> MythTV should schedule a wakeup to run mythfilldatabase when it does not find anything else in its schedule. It should schedule
>>> a wakeup for mythfilldatabase anyway if the scheduled event would happen after it runs out of schedule for any channel.
>>>
>> The sounds like you need to schedule the next wakeup yourself when the
>> shutdown happens if there is not going to be wakeup before the next
>> mythfilldatabase time.  You can use the API to find out when the next
>> recording time will be.  Take a look at what my Python "gaps" program
>> does:

>When would I run this? The proper time to do that check is when the system is shutting down. That would be setwakeup.sh, but
>that does not get run when there is no recording. Exactly the time I would need to run this.

You could just run it as a cron job every hour, or however often you
need it.