From 23685502f3f923930cc9c24a1e2e99b5173d2a37 Mon Sep 17 00:00:00 2001
From: David Luevano Alvarado <david@luevano.xyz>
Date: Thu, 15 Jun 2023 04:26:29 -0600
Subject: fix typos on arch logs entry, add temp jellyfin entry
---
live/blog/a/arch_logs_flooding_disk.html | 7 ++++---
1 file changed, 4 insertions(+), 3 deletions(-)
(limited to 'live/blog/a')
diff --git a/live/blog/a/arch_logs_flooding_disk.html b/live/blog/a/arch_logs_flooding_disk.html
index 4b8bd19..8903f85 100644
--- a/live/blog/a/arch_logs_flooding_disk.html
+++ b/live/blog/a/arch_logs_flooding_disk.html
@@ -91,13 +91,13 @@
<p>It’s been a while since I’ve been running a minimal server on a VPS, and it is a pretty humble VPS with just 32 GB of storage which works for me as I’m only hosting a handful of services. At some point I started noticing that the disk keept filling up on each time I checked.</p>
<p>Turns out that out of the box, Arch has a default config for <code>systemd</code>‘s <code>journald</code> that keeps a persistent <code>journal</code> log, but doesn’t have a limit on how much logging is kept. This means that depending on how many services, and how aggresive they log, it can be filled up pretty quickly. For me I had around 15 GB of logs, from the normal <code>journal</code> directory, <code>nginx</code> directory and my now unused <code>prosody</code> instance.</p>
<p>For <code>prosody</code> it was just a matter of deleting the directory as I’m not using it anymore, which freed around 4 GB of disk space.
-For <code>journal</code> I did a combination of configuring <code>SystemMaxUse</code> and creating a <em>Namespace</em> for all “email” related services as mentioned in the <a href="https://wiki.archlinux.org/title/Systemd/Journal#Per_unit_size_limit_by_a_journal_namespace">Arch wiki: systemd/Journal</a>; basically just configuring <code>/etc/systemd/journald.conf</code> (and <code>/etc/systemd/journald@email.con</code> with the comment change) with:</p>
-<pre><code class="language-conf">[Journal]
+For <code>journal</code> I did a combination of configuring <code>SystemMaxUse</code> and creating a <em>Namespace</em> for all “email” related services as mentioned in the <a href="https://wiki.archlinux.org/title/Systemd/Journal#Per_unit_size_limit_by_a_journal_namespace">Arch wiki: systemd/Journal</a>; basically just configuring <code>/etc/systemd/journald.conf</code> (and <code>/etc/systemd/journald@email.conf</code> with the comment change) with:</p>
+<pre><code class="language-ini">[Journal]
Storage=persistent
SystemMaxUse=100MB # 50MB for the "email" Namespace
</code></pre>
<p>And then for each service that I want to use this “email” <em>Namespace</em> I add:</p>
-<pre><code class="language-conf">[Service]
+<pre><code class="language-ini">[Service]
LogNamespace=email
</code></pre>
<p>Which can be changed manually or by executing <code>systemctl edit service_name.service</code> and it will create an override file which will be read on top of the normal service configuration. Once configured restart by running <code>systemctl daemon-reload</code> and <code>systemctl restart service_name.service</code> (probably also restart <code>systemd-journald</code>).</p>
@@ -142,6 +142,7 @@ LogNamespace=email
<div class="article-info">
<p>By David Luévano</p>
<p>Created: Thu, Jun 15, 2023 @ 10:22 UTC</p>
+ <p>Modified: Thu, Jun 15, 2023 @ 10:24 UTC</p>
<div class="article-tags">
<p>Tags:
<a href="https://blog.luevano.xyz/tag/@code.html">code</a>, <a href="https://blog.luevano.xyz/tag/@english.html">english</a>, <a href="https://blog.luevano.xyz/tag/@server.html">server</a>, <a href="https://blog.luevano.xyz/tag/@short.html">short</a>, <a href="https://blog.luevano.xyz/tag/@tools.html">tools</a>, <a href="https://blog.luevano.xyz/tag/@tutorial.html">tutorial</a> </p>
--
cgit v1.2.3-70-g09d2