[mythtv-users] optimize before shut down

Stephen Worthington stephen_agent at jsw.gen.nz
Tue Apr 30 03:26:23 UTC 2019


On Mon, 29 Apr 2019 17:41:37 -0400, you wrote:

>On Wed, Apr 24, 2019 at 10:43 PM Stephen Worthington <
>stephen_agent at jsw.gen.nz> wrote:
>
>> On Wed, 24 Apr 2019 11:46:28 -0500, you wrote:
>>
>> >On 4/24/19 11:34 AM, Daryl McDonald wrote:
>> >> When I wrote out I wasn't offered the path I expected
>> >> (/etc/systemd/system/anacron.timer.d.) rather an alpha/numeric
>> sequence, I
>> >> now suspect they were the tailing sequence:
>> (#override.confd50a7936adc6c1fe)
>> >
>> >That's just a temporary file. Type: systemctl cat anacron.timer
>> >and you should see the original file (probably in /lib...) and
>> >the expected override.
>>
>> Yes, the editor is opened on a temporary file in the directory it has
>> just created:
>>
>> /etc/systemd/system/anacron.timer.d/
>>
>> When you save the file in the editor, it gets renamed to
>> "override.conf".
>> _______________________________________________
>>
>I can see that the override took effect, the third line below seems to
>indicate that nothing actually ran, am I reading this right?
>
> Apr 28 19:30:00 trieli systemd[1]: Started Run anacron jobs.
>Apr 28 19:30:00 trieli anacron[3999]: Anacron 2.3 started on 2019-04-28
>Apr 28 19:30:00 trieli anacron[3999]: Normal exit (0 jobs run)

Yes, that normally means that anacron had already been run that day,
so when the timer ran it, it checked its timestamps in
/var/spool/anacron and decided it should not be run again.  The next
day, it should run the jobs.


More information about the mythtv-users mailing list