https://devops.sarmento.org/en/tags/timer-management/Recent content in Timer-Management on /var/log/janioHugoenSat, 11 Apr 2026 11:22:00 +0000https://devops.sarmento.org/en/posts/systemd-timers-time-to-retire-cron/Mon, 23 Mar 2026 06:21:00 +0000https://devops.sarmento.org/en/posts/systemd-timers-time-to-retire-cron/<p>If you have been managing Debian or Ubuntu servers for any length of time, you probably have a comfort relationship with cron. One line in the crontab, five scheduling fields, and the path to a script — done. cron has worked this way since the 1970s, and that simplicity is exactly what kept it relevant for so long.</p> <p>The problem is that &ldquo;it works&rdquo; and &ldquo;it works well in 2026&rdquo; are different things. When a job fails silently at three in the morning, when you need to figure out which of twenty crontabs scattered across the system contains that one specific task, or when the server reboots and simply misses the execution that should have happened during downtime — those are the moments when cron shows it was designed for an era with different expectations around observability and resilience.</p>