PSA: systemd-journald uses <i>shared</i> file-backed mappings via mmap() for its journal IO.<p>You must subtract its shared memory use from its resident memory use before judging how much memory it's consuming. The file-backed shared mappings are <i>reclaimable</i>, because they are file-backed. The kernel will just evict the mapped journal pages at will, since they can always be faulted back in from the filesystem.<p>TFA is much ado about nothing, learn to measure memory use properly before breaking out the pitch forks.<p>Full disclosure: I've hacked a bunch on journald upstream.
Would doing something like this work around the "journald drops the most important error messages" issue that has been known/outstanding for ten years (bug moved to GitHub six years ago), or is that more of a fundamental design mistake in systemd itself?<p><a href="https://github.com/systemd/systemd/issues/2913" rel="nofollow">https://github.com/systemd/systemd/issues/2913</a><p><a href="https://bugs.freedesktop.org/show_bug.cgi?id=50184" rel="nofollow">https://bugs.freedesktop.org/show_bug.cgi?id=50184</a>
systemd is incredibly useful and powerful.<p>If you are a developer on Linux then you really owe it to yourself to learn as much as you can about systemd.<p>If you really understand systemd then you'll find yourself architecting your software around its capabilities.<p>systemd, if you understand it, can mean you can completely avoid large chunks of development you might otherwise have assumed you need to do.<p>socket activated services,
nspawn,
traffic accounting,
the list of juicy goodness goes on and on....<p>Ignore the haters, they wouldn't hate if they dedicated their energy to understanding systemd instead of hating on it.<p>In 2022 you are a really an incomplete full stack developer if systemd is not one of the technologies you know very well.
I have but one word for this guy.<p>Devuan<p>I see no reason not to consider it.<p>He is a Debian user who hates the way systemd works.<p>Devuan is for you.
"when I needed systemd binary logs? - and I realized I never needed them."<p>that is my sentiment.<p>Linus was hesitant about binary logs.<p>I think they are just not unix. They are doing the wrong thing correctly (I would prefer doing the right thing poorly - or better yet doing it well)
Can we just admit jourald is a thorn in the side of people taking systems seriously. The default behaviour even on polished distros is just bad and it's mainly because of the mindsets behind it...