<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Logrotate on Linux Café</title>
    <link>https://mrtomlinux.org/tags/logrotate/</link>
    <description>Recent content in Logrotate on Linux Café</description>
    <generator>Hugo</generator>
    <language>en</language>
    <lastBuildDate>Mon, 29 Jun 2026 09:11:35 +0200</lastBuildDate>
    <atom:link href="https://mrtomlinux.org/tags/logrotate/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Troubleshooting Slow Log Rotation in Small Linux Servers with High IO Workloads</title>
      <link>https://mrtomlinux.org/post/2026-06-29-troubleshooting-slow-log-rotation-in-small-li/</link>
      <pubDate>Mon, 29 Jun 2026 09:11:35 +0200</pubDate>
      <guid>https://mrtomlinux.org/post/2026-06-29-troubleshooting-slow-log-rotation-in-small-li/</guid>
      <description>&lt;h2 id=&#34;introduction-to-log-rotation&#34;&gt;Introduction to Log Rotation&lt;/h2&gt;&#xA;&lt;p&gt;I&amp;rsquo;ve seen log rotation become a major issue on small servers with high IO workloads - it&amp;rsquo;s a problem that can sneak up on you quickly. Logs can grow at an alarming rate, and if you don&amp;rsquo;t manage them properly, they can fill up your disk space in no time. The real trick is to stay on top of log rotation, and that&amp;rsquo;s where tools like &lt;code&gt;logrotate&lt;/code&gt; come in.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Taming log Noise with journalctl and logrotate in a Small Home Server Setup</title>
      <link>https://mrtomlinux.org/post/2026-06-19-taming-log-noise-with-journalctl-and-logrotat/</link>
      <pubDate>Fri, 19 Jun 2026 10:04:19 +0200</pubDate>
      <guid>https://mrtomlinux.org/post/2026-06-19-taming-log-noise-with-journalctl-and-logrotat/</guid>
      <description>&lt;h2 id=&#34;taming-log-noise-on-linux&#34;&gt;Taming Log Noise on Linux&lt;/h2&gt;&#xA;&lt;p&gt;As someone who&amp;rsquo;s spent years running Linux systems, I can tell you that log management is crucial. Logs provide valuable insights into system activity, helping you troubleshoot issues and identify potential security threats. However, log noise can quickly become overwhelming, making it difficult to find relevant information. In my experience, &lt;code&gt;journalctl&lt;/code&gt; and &lt;code&gt;logrotate&lt;/code&gt; are two essential tools for managing logs on a small home server setup.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
