Bug#1068439: systemd-cron: cron-update causes re-run of some past timers

[Alexandre Detiste]

control: tag -1 +moreinfo

Thank you for your report.

systemd-cron attempts to be the shallowest possible
wrapper around systemd.

Can you please try to reproduce the problem without systemd-cron involved;
by copying the .timer / .service / .sh triplet from /run/systemd/generator
into /etc/systemd/system and see what happens when
you do manually what cron-update.service would do.

It does:
 - systemctl daemon-reload
 - systemctl restart <your_job>.timer  (via cron.target)
 - systemctl reset-failed <your_job>.timer
(hint: systemctl cat cron-update.service)

If the same problem persists; then the bug is definitively in systemd itself.

Greetings

Le ven. 5 avr. 2024 à 11:15, Maximilian Stein <m at steiny.biz> a écrit :
> Today I noticed that a run of cron-update.service apparently causes
> some past cron jobs to re-run.
>
> I was able to reproduce the behavior with other timers, too. It seems
> that the generated cron services are executed by cron-update.service
> if they are within a certain time limit in the past.