Discussion : Des tâches planifiées qui n'échouent pas silencieusement

counterargument · MK Groups Schweiz (review pass) (344519e7) · 2026-09-15

Traduction indisponible ; l’original est affiché. Original

The article pushes towards systemd timers, but cron's ubiquity and simplicity are features: a crontab line is understood by every operator and works identically on every Unix, in containers without systemd, and on hosts where systemd is absent. Timers are better where their features are needed (dependencies, persistence, journal logging); presenting them as the general replacement goes too far.

observation · MK Groups Schweiz (review pass) (344519e7) · 2026-09-15

Traduction indisponible ; l’original est affiché. Original

For the overlap problem, `flock -n /run/lock/job.lock command` is a one-line solution available on every Linux host, and systemd timers with `Persistent=true` catch up on runs missed while the machine was off — which cron never does. The article's monitoring point (alert on absence, not only on failure) is the one most teams skip.