<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Systemd on ilikeorangutans</title><link>https://kuelzer.ca/tags/systemd/</link><description>Recent content in Systemd on ilikeorangutans</description><generator>Hugo</generator><language>en</language><copyright>© 2026 Jakob Külzer</copyright><lastBuildDate>Thu, 29 Oct 2026 14:11:11 -0400</lastBuildDate><atom:link href="https://kuelzer.ca/tags/systemd/index.xml" rel="self" type="application/rss+xml"/><item><title>journald Volatile Storage</title><link>https://kuelzer.ca/posts/2026/10/29/journald-volatile-storage/</link><pubDate>Thu, 29 Oct 2026 14:11:11 -0400</pubDate><guid>https://kuelzer.ca/posts/2026/10/29/journald-volatile-storage/</guid><description>&lt;p&gt;I&amp;rsquo;m in the process of moving my homelab servers to NixOS. I moved a few machines over and was monitoring them when I noticed that one of the machines was constantly writing 400-500 kB/s to disk. After some digging I found that journald was the culprit for the IO; well, technically the culprit is another service that was spamming the logs, but that&amp;rsquo;s not important right now. I didn&amp;rsquo;t want the constant writes for logs to add to the wear and tear of the storage because with the current prices for anything memory that&amp;rsquo;s just wasting money. I now collect logs centrally via alloy/loki, so there&amp;rsquo;s not really a reason to keep them on the machine&amp;rsquo;s disk itself. After some research I found that journald can &lt;a href="https://www.freedesktop.org/software/systemd/man/latest/journald.conf.html#Storage="&gt;write logs to a in-memory location instead of disk&lt;/a&gt;: Setting &lt;code&gt;Storage&lt;/code&gt; to &lt;code&gt;volatile&lt;/code&gt; will enable that behaviour. By default it&amp;rsquo;s set to &lt;code&gt;persistent&lt;/code&gt; in nixos meaning&lt;/p&gt;</description></item></channel></rss>