<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Systemadministration on ShieldedBytes</title>
    <link>https://linuxeries.org/tags/systemadministration/</link>
    <description>Recent content in Systemadministration on ShieldedBytes</description>
    <generator>Hugo</generator>
    <language>en</language>
    <lastBuildDate>Tue, 16 Jun 2026 10:56:33 +0200</lastBuildDate>
    <atom:link href="https://linuxeries.org/tags/systemadministration/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Taming Disk-Hungry Log Files on Small Linux Servers with Log Rotation and Compression</title>
      <link>https://linuxeries.org/post/2026-06-16-taming-disk-hungry-log-files-on-small-linux-s/</link>
      <pubDate>Tue, 16 Jun 2026 10:56:33 +0200</pubDate>
      <guid>https://linuxeries.org/post/2026-06-16-taming-disk-hungry-log-files-on-small-linux-s/</guid>
      <description>&lt;h2 id=&#34;introduction-to-log-rotation-and-compression&#34;&gt;Introduction to Log Rotation and Compression&lt;/h2&gt;&#xA;&lt;p&gt;I&amp;rsquo;ve seen log files grow out of control on many Linux systems, causing performance issues and security headaches. In my experience, effective log rotation and compression strategies are crucial for maintaining system health. The &lt;code&gt;logrotate&lt;/code&gt; utility is a powerful tool for managing log files, but it requires careful configuration to get the most out of it.&lt;/p&gt;&#xA;&lt;h2 id=&#34;understanding-log-rotation&#34;&gt;Understanding Log Rotation&lt;/h2&gt;&#xA;&lt;p&gt;Log rotation is the process of periodically switching out log files to prevent them from growing too large. I usually start with the &lt;code&gt;logrotate&lt;/code&gt; configuration file, typically located at &lt;code&gt;/etc/logrotate.conf&lt;/code&gt;, to specify the rotation schedule, log file locations, and other settings. Here&amp;rsquo;s an example configuration snippet:&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
