Hi.
Yes. [*]
I will keep this one bug open here if in any case someone stumble on the
same problems.
[*]: this mean checking the Debian & upstream bug tracker for a possible
duplicate, this might take a while; do you want to have a look ?
At times I audit system/cronie/vixie cron for bugs/feat
So, should this issue be forwarded/moved to systemd then?
Thanks for your quick reply.
Am 06.04.24 um 06:37 schrieb Alexandre Detiste:
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 w
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
Package: systemd-cron
Version: 2.3.4-1
Severity: normal
Dear Maintainer,
Today I noticed that a run of cron-update.service apparently causes
some past cron jobs to re-run.
In particular, I have a cron job of "5 5 5 * *" which correctly
executed this morning at 2024-04-05T05:05:08.401635+02:00.
5 matches
Mail list logo
