<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Bash on Lead DevOps</title><link>https://lead-devops.blackdevhub.online/en/tags/bash/</link><description>Recent content in Bash on Lead DevOps</description><generator>Hugo</generator><language>en-US</language><lastBuildDate>Mon, 31 Aug 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://lead-devops.blackdevhub.online/en/tags/bash/index.xml" rel="self" type="application/rss+xml"/><item><title>Cron setup: a practical walkthrough</title><link>https://lead-devops.blackdevhub.online/en/posts/cron-setup/</link><pubDate>Mon, 31 Aug 2026 00:00:00 +0000</pubDate><guid>https://lead-devops.blackdevhub.online/en/posts/cron-setup/</guid><description>&lt;p&gt;Cron is the standard job scheduler in Linux, found in every infrastructure. Jobs pile up, logs accumulate, and the environment breaks things. Let&amp;rsquo;s walk through how to configure cron reliably and where it falls short.&lt;/p&gt;&#10;&lt;h2 id="when-to-use-cron-and-when-to-avoid-it"&gt;When to Use Cron and When to Avoid It&#10;&lt;/h2&gt;&#10;&lt;p&gt;Cron fits simple recurring tasks: backups, log rotation, temp file cleanup, periodic notifications. It&amp;rsquo;s a daemon that sleeps between runs — no resource consumption.&lt;/p&gt;</description></item></channel></rss>