Am 29.06.2017 um 00:16 schrieb Michael Biebl:
> On Mon, 26 Jun 2017 23:50:51 +0200 "Francesco Poli (wintermute)"
> <invernom...@paranoici.org> wrote:
>> Package: anacron
>> Version: 2.3-24
>> Severity: normal
>> Tags: patch
>>
>> Hello,
>> I see that bug #744753 has been solved by changing the frequency at
>> which anacron checks whether there are jobs to be executed.
>> When systemd is PID 1, anacron performs this check hourly via
>> timer, rather than daily at 7:30, as done on boxes where systemd is
>> *not* PID 1 (/etc/cron.d/anacron).
>>
>> This behavior change has a significant side effect: if the box
>> is up and running at midnight, anacron may begin to execute
>> daily (and possibly also weekly or monthly) jobs shortly after.
>> Maybe it will (attempt to) start a backup or something like that,
>> after midnight, when it could be time to shut the box down...
> 
> If you run a backup via cron you should guard it against accidental
> shutdown in any case. systemd-inhibit is the tool you might want to look
> into.

I also want to add that in older releases anacron was triggered on
resume and AC changes (via the pm-utils hooks).

So you didn't necessarly have a fixed time when anacron (and possibly
such a backup script) runs.


-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?

Attachment: signature.asc
Description: OpenPGP digital signature

Reply via email to