<?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>Fri, 19 Jun 2026 10:04:19 +0200</lastBuildDate>
    <atom:link href="https://mrtomlinux.org/tags/logrotate/index.xml" rel="self" type="application/rss+xml" />
    <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>
