<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Scheduling on LinuxHosted.com</title><link>https://www.linuxhosted.com/tags/scheduling/</link><description>Recent content in Scheduling on LinuxHosted.com</description><generator>Hugo -- gohugo.io</generator><language>en</language><copyright>LinuxHosted.com</copyright><lastBuildDate>Wed, 17 Jun 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://www.linuxhosted.com/tags/scheduling/index.xml" rel="self" type="application/rss+xml"/><item><title>Systemd Timers: Replace Cron Jobs on a Linux VPS</title><link>https://www.linuxhosted.com/post/systemd-timers-replace-cron-vps/</link><pubDate>Wed, 17 Jun 2026 00:00:00 +0000</pubDate><guid>https://www.linuxhosted.com/post/systemd-timers-replace-cron-vps/</guid><description>
&lt;p&gt;Cron has scheduled Unix jobs for forty years and it still works, but on a systemd-based VPS it is no longer the only option — and for anything you need to &lt;em&gt;operate&lt;/em&gt; rather than just fire-and-forget, systemd timers are the better tool. The difference is not nostalgia versus novelty; it is that a cron job is invisible until it fails silently, while a timer is a first-class systemd unit with status, logs, dependency ordering, and a built-in answer to the classic cron weakness: jobs missed while the machine was off. This guide converts a cron job to a systemd timer step by step and explains, at each point, what the timer gives you that the crontab line could not.&lt;/p&gt;</description></item></channel></rss>