On 4/14/26 8:04 AM, Vincent Lefevre wrote:
Running anacron on upgrades is not a big problem, but it makes the start time of the daily jobs less regular without any good reason when an upgrade is done between midnight and 07:30. For instance, if an upgrade is done on day 3 at 00:10,Day 1: 07:30 (with a delay of up to 5 minutes) Day 2: 07:30 (with a delay of up to 5 minutes) Day 3: 00:10 Day 4: 07:30 (with a delay of up to 5 minutes) So I would say that it would be better to avoid that.
If you want a job to run at 7:30 every day, you should be using cron. If you want a job to run some time every day, you should use anacron.
anacron does not check the hours since the last job was run. If a job was unable to start until 21:30, it will still try to run at 7:30 the next day.
With all of the other ways anacron jobs can be run that I listed before, running jobs outside of the timer window should not be an issue and since the upgrade time and the job scheduler is decided by the user, please choose what works best for your use case.
If there is an actual issue with the install section, I will debug this via a new issue since this one will close with the next release of anacron 2.3-50.I confirm that upgrading to anacron 2.3-49 between midnight and 07:30 did not hang:
Thank you for testing. The 2.3-50 should be in unstable soon. -- Lance Lin GPG Fingerprint: 4A31 DB5A 1EE4 096C 8739 9880 9036 4929 4C33 F9B7
OpenPGP_0x903649294C33F9B7.asc
Description: OpenPGP public key
OpenPGP_signature.asc
Description: OpenPGP digital signature
