<?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 ShieldedBytes</title>
    <link>https://linuxeries.org/tags/logrotate/</link>
    <description>Recent content in Logrotate on ShieldedBytes</description>
    <generator>Hugo</generator>
    <language>en</language>
    <lastBuildDate>Fri, 22 May 2026 10:03:35 +0200</lastBuildDate>
    <atom:link href="https://linuxeries.org/tags/logrotate/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Taming Noisy System Logs with journalctl and Logrotate Filters</title>
      <link>https://linuxeries.org/post/2026-05-22-taming-noisy-system-logs-with-journalctl-and-/</link>
      <pubDate>Fri, 22 May 2026 10:03:35 +0200</pubDate>
      <guid>https://linuxeries.org/post/2026-05-22-taming-noisy-system-logs-with-journalctl-and-/</guid>
      <description>&lt;h2 id=&#34;introduction-to-system-logs&#34;&gt;Introduction to System Logs&lt;/h2&gt;&#xA;&lt;p&gt;I&amp;rsquo;ve been working with Linux systems for years, and I can tell you that system logs are a crucial part of any setup. They provide valuable information about system events, errors, and security incidents. However, with the increasing complexity of modern systems, log files can become overwhelming, making it difficult to identify important issues. This is where tools like &lt;code&gt;journalctl&lt;/code&gt; and &lt;code&gt;logrotate&lt;/code&gt; come in - they help you tame noisy system logs and focus on what really matters.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
