<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Systemd on Locodigital</title><link>https://locodigital.com.br/en/tags/systemd/</link><description>Recent content in Systemd on Locodigital</description><generator>Hugo</generator><language>en-US</language><lastBuildDate>Wed, 24 Jun 2026 00:00:00 -0300</lastBuildDate><atom:link href="https://locodigital.com.br/en/tags/systemd/index.xml" rel="self" type="application/rss+xml"/><item><title>Crontab on Linux: how to schedule tasks automatically</title><link>https://locodigital.com.br/en/technology/crontab-on-linux-how-to-schedule-tasks/</link><pubDate>Wed, 24 Jun 2026 00:00:00 -0300</pubDate><guid>https://locodigital.com.br/en/technology/crontab-on-linux-how-to-schedule-tasks/</guid><description>&lt;p&gt;A backup that should run every day at 3am, but only runs when somebody remembers to execute the script by hand. A log that grows without rotation until it fills the disk. A certificate that expires because nobody automated the renewal. All of these problems share the same cause: a task that ought to be automatic still depends on a human remembering. &lt;code&gt;crontab&lt;/code&gt; has existed since the earliest Unix systems for exactly this — and most sysadmins use only a fraction of what it offers.&lt;/p&gt;</description></item></channel></rss>