<?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 Security</title><link>https://linuxtransfer.com/tags/logrotate/</link><description>Recent content in Logrotate on Linux Security</description><generator>Hugo</generator><language>en</language><lastBuildDate>Mon, 01 Jun 2026 10:10:58 +0200</lastBuildDate><atom:link href="https://linuxtransfer.com/tags/logrotate/index.xml" rel="self" type="application/rss+xml"/><item><title>Taming Disk-Hungry Logs with systemd-journald and logrotate</title><link>https://linuxtransfer.com/post/2026-06-01-taming-disk-hungry-logs-with-systemd-journald/</link><pubDate>Mon, 01 Jun 2026 10:10:58 +0200</pubDate><guid>https://linuxtransfer.com/post/2026-06-01-taming-disk-hungry-logs-with-systemd-journald/</guid><description>&lt;h2 id="introduction-to-log-management">Introduction to Log Management&lt;/h2>
&lt;p>I&amp;rsquo;ve seen log files grow out of control and consume disk space, affecting system performance. To tame disk-hungry logs, I recommend using &lt;code>systemd-journald&lt;/code> and &lt;code>logrotate&lt;/code>. These tools help manage log data, making it easier to troubleshoot, debug, and perform security audits.&lt;/p>
&lt;h2 id="understanding-systemd-journald">Understanding systemd-journald&lt;/h2>
&lt;p>&lt;code>systemd-journald&lt;/code> is a system service that collects and stores log messages from various sources. It provides a centralized logging system, which I find more efficient than traditional text-based log files. To view log messages, use the &lt;code>journalctl&lt;/code> command:&lt;/p></description></item></channel></rss>