diff options
| author | David Luevano Alvarado <david@luevano.xyz> | 2023-06-15 04:26:29 -0600 |
|---|---|---|
| committer | David Luevano Alvarado <david@luevano.xyz> | 2023-06-15 04:26:29 -0600 |
| commit | 23685502f3f923930cc9c24a1e2e99b5173d2a37 (patch) | |
| tree | 5c4681246c9fa40ccb6216ebcc41ad88a177acd6 /live/blog/rss.xml | |
| parent | 4299f2c21ff4e13a911f8b41d99d1fcef7823ec6 (diff) | |
fix typos on arch logs entry, add temp jellyfin entry
Diffstat (limited to 'live/blog/rss.xml')
| -rw-r--r-- | live/blog/rss.xml | 6 |
1 files changed, 3 insertions, 3 deletions
diff --git a/live/blog/rss.xml b/live/blog/rss.xml index 9c7de3e..d96d238 100644 --- a/live/blog/rss.xml +++ b/live/blog/rss.xml @@ -37,13 +37,13 @@ <content:encoded><![CDATA[<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> |