fosstodon.org is one of the many independent Mastodon servers you can use to participate in the fediverse.
Fosstodon is an invite only Mastodon instance that is open to those who are interested in technology; particularly free & open source software. If you wish to join, contact us for an invite.

Administered by:

Server stats:

8.8K
active users

#journald

0 posts0 participants0 posts today
Klaus Frank<p>Oh adding these TTY options into the sddm.service didn't work because it the parent process blocks the sddm-helper child process. It does not appear to be within that services cgroup.</p><p>I think, it lives too short to actually have a closer look at it. All I can tell is when it fails to access the tty it writes an error into <a href="https://chaos.social/tags/journald" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>journald</span></a>, but in a way that it doesn't show up when filtering for the sddm.service unit specifically the other sddm-helper processes do...</p>
Habr<p>Сбор событий Linux: есть цель – ищем путь</p><p>Приветствую всех, кто заглянул на огонек! Меня зовут Роман, и я занимаюсь исследованием безопасности Linux (и всякого другого, связанного с ним) в экспертном центре безопасности в Positive Technologies. Мне периодически приходится сталкиваться с вопросами клиентов или коллег из смежных отделов по поводу оптимизации работы различных компонентов журналирования внутри Linux. Поэтому в какой-то момент возникла идея обрисовать как минимум для самого себя целостную картину их взаимодействия и влияния друг на друга. Результатом работы стала довольно компактная схема, которая помогает оперативнее и эффективнее отвечать на возникающие вопросы для решения проблем. В статье я постараюсь вкратце описать каждый ее блок. Не ручаюсь за то, что будут затронуты все тонкости, известные лишь узкому кругу специалистов. Но на большую часть вопросов я отвечу.</p><p><a href="https://habr.com/ru/companies/pt/articles/925894/" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">habr.com/ru/companies/pt/artic</span><span class="invisible">les/925894/</span></a></p><p><a href="https://zhub.link/tags/linux" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>linux</span></a> <a href="https://zhub.link/tags/siem" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>siem</span></a> <a href="https://zhub.link/tags/auditd" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>auditd</span></a> <a href="https://zhub.link/tags/syslog" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>syslog</span></a> <a href="https://zhub.link/tags/journald" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>journald</span></a> <a href="https://zhub.link/tags/%D0%B0%D0%B4%D0%BC%D0%B8%D0%BD%D0%B8%D1%81%D1%82%D1%80%D0%B8%D1%80%D0%BE%D0%B2%D0%B0%D0%BD%D0%B8%D0%B5_linux%D1%81%D0%B8%D1%81%D1%82%D0%B5%D0%BC" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>администрирование_linuxсистем</span></a></p>
Марков Дмитрий<p>Не знал что так можно:</p><pre><code>sudo systemctl start systemd-journal-gatewayd.{socket,service} curl -s http://127.0.0.1:19531/entries curl -s "http://127.0.0.1:19531/entries?UNIT=sshd.service" curl -s -H "Accept: application/json" "http://127.0.0.1:19531/entries?UNIT=sshd.service" </code></pre><p>А ещё там есть вебморда по пути /browse.</p><p><a href="https://gts.itrus.su/tags/systemd" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>systemd</span></a> <a href="https://gts.itrus.su/tags/http" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>http</span></a> <a href="https://gts.itrus.su/tags/web" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>web</span></a> <a href="https://gts.itrus.su/tags/logs" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>logs</span></a> <a href="https://gts.itrus.su/tags/journald" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>journald</span></a></p><p>UPD: работает шустрее чем Filebeat, FluentBit, FluentD и syslog-ng и не грузит систему излишне, вопрос только чем пушить, но это вопрос решаемый.</p>
France | République française<p><a href="https://www.europesays.com/fr/131404/" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://www.</span><span class="">europesays.com/fr/131404/</span><span class="invisible"></span></a> Les meilleurs romans de Virginie Grimaldi <a href="https://pubeurope.com/tags/Books" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Books</span></a> <a href="https://pubeurope.com/tags/Divertissement" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Divertissement</span></a> <a href="https://pubeurope.com/tags/Entertainment" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Entertainment</span></a> <a href="https://pubeurope.com/tags/FeelGood" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>FeelGood</span></a> <a href="https://pubeurope.com/tags/FR" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>FR</span></a> <a href="https://pubeurope.com/tags/France" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>France</span></a> <a href="https://pubeurope.com/tags/JournalD" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>JournalD</span></a>'unLibraire <a href="https://pubeurope.com/tags/litt%C3%A9rature" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>littérature</span></a> <a href="https://pubeurope.com/tags/Livres" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Livres</span></a> <a href="https://pubeurope.com/tags/SelectionLivre" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>SelectionLivre</span></a></p>
Habr<p>lazyjournal — ленивый интерфейс для поиска и анализа логов</p><p>Ранее, я уже писал статью о различных способах, которые мне приходилось использовать для чтения логов, и к какому решению в итоге пришел. Хотя прошло не так много времени, с тех пор приложение не переставало развиваться. Узнав о том, что на Хабре проходит сезон Open source , мне показалось это отличным поводом подчеркнуть, что именно стало причиной для создания данного инструмента, а также рассказать немного подробнее про основные и новые функции.</p><p><a href="https://habr.com/ru/articles/899750/" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="">habr.com/ru/articles/899750/</span><span class="invisible"></span></a></p><p><a href="https://zhub.link/tags/%D1%81%D0%B5%D0%B7%D0%BE%D0%BD_open_source" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>сезон_open_source</span></a> <a href="https://zhub.link/tags/golang" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>golang</span></a> <a href="https://zhub.link/tags/tui" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>tui</span></a> <a href="https://zhub.link/tags/journalctl" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>journalctl</span></a> <a href="https://zhub.link/tags/journald" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>journald</span></a> <a href="https://zhub.link/tags/auditd" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>auditd</span></a> <a href="https://zhub.link/tags/docker" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>docker</span></a> <a href="https://zhub.link/tags/%D0%BB%D0%BE%D0%B3%D0%B8" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>логи</span></a> <a href="https://zhub.link/tags/%D0%BC%D0%BE%D0%BD%D0%B8%D1%82%D0%BE%D1%80%D0%B8%D0%BD%D0%B3" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>мониторинг</span></a></p>
uhurusystemctl works with -both- 'ssh.service' + 'sshd.service'<br>journalctl only works for 'ssh.service' . "no entries" for 'sshd.service' ..<br>(<a href="https://snac.el-hoyo.net/social?t=debian" class="mention hashtag" rel="nofollow noopener" target="_blank">#Debian</a> stable fully upgraded)<br><br><a href="https://snac.el-hoyo.net/social?t=systemd" class="mention hashtag" rel="nofollow noopener" target="_blank">#systemd</a> + <a href="https://snac.el-hoyo.net/social?t=journald" class="mention hashtag" rel="nofollow noopener" target="_blank">#journald</a> , go figure. :)<br>
Habr<p>LXC теряли память и падали. И при чем же здесь tmpfs и journald?</p><p>Старый добрый Proxmox с его контейнерами и виртуалками - по-прежнему рабочая лошадка многих компаний. И если нарезать много-много мелких контейнеров, то может случиться, что память куда-то девается со временем, а контейнеры падают в OOM без очевидной причины. Причем не все. Причем иногда. И зачастую проще перезапустить и ехать дальше чем разбираться. А причина есть, и она оказалось довольно проста.</p><p><a href="https://habr.com/ru/articles/883562/" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="">habr.com/ru/articles/883562/</span><span class="invisible"></span></a></p><p><a href="https://zhub.link/tags/proxmox" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>proxmox</span></a> <a href="https://zhub.link/tags/lxc" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>lxc</span></a> <a href="https://zhub.link/tags/tmpfs" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>tmpfs</span></a> <a href="https://zhub.link/tags/journald" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>journald</span></a> <a href="https://zhub.link/tags/oom" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>oom</span></a> <a href="https://zhub.link/tags/oom_killer" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>oom_killer</span></a> <a href="https://zhub.link/tags/systemd" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>systemd</span></a></p>
Habr<p>Простой и универсальный способ чтения логов в терминале</p><p>Существует достаточно много решений для локального и удаленного чтения и сбора логов с различных систем, но некоторые из них могут быть сложны в своей конфигурации и достаточно тяжеловесные для мониторинга одного или двух микросервисов, особенно, если не стоит вопрос удаленного хранения логов. У меня есть небольшой проект, который в процессе своей работы пишет логи, по этому на примере него расскажу, какие решения для их чтения использовал, и к чему в итоге пришел.</p><p><a href="https://habr.com/ru/articles/872536/" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="">habr.com/ru/articles/872536/</span><span class="invisible"></span></a></p><p><a href="https://zhub.link/tags/%D0%BB%D0%BE%D0%B3%D0%B8" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>логи</span></a> <a href="https://zhub.link/tags/%D0%BB%D0%BE%D0%B3%D0%B8%D1%80%D0%BE%D0%B2%D0%B0%D0%BD%D0%B8%D0%B5" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>логирование</span></a> <a href="https://zhub.link/tags/%D0%BC%D0%BE%D0%BD%D0%B8%D1%82%D0%BE%D1%80%D0%B8%D0%BD%D0%B3" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>мониторинг</span></a> <a href="https://zhub.link/tags/journald" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>journald</span></a> <a href="https://zhub.link/tags/journalctl" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>journalctl</span></a> <a href="https://zhub.link/tags/docker" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>docker</span></a> <a href="https://zhub.link/tags/podman" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>podman</span></a></p>
Lambda :neofox_flag_nb:<p>TIL - from journalctl(1):</p><p>&gt; It is also possible to filter the entries by specifying an absolute file path as an argument. [...] If a file path refers to a device node, "_KERNEL_DEVICE=" matches for the kernel name of the device and for each of its ancestor devices is added to the query.</p><p>Try `sudo journalctl /dev/input/mouse0`, pretty cool!</p><p><a href="https://chaosfurs.social/tags/systemd" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>systemd</span></a> <a href="https://chaosfurs.social/tags/journald" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>journald</span></a> <a href="https://chaosfurs.social/tags/journalctl" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>journalctl</span></a> <a href="https://chaosfurs.social/tags/linux" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>linux</span></a></p>
ferricoxide<p><span>I used to hate the switch to </span><code>journald</code><span>, but, when you actually make use of its controls, it can be easier than massaging the wholly text-based files that (r)syslog spits out. This morning, I was adding DNS records to make it easier for me to relay my MTA's messages through AWS's SES. Didn't want to find that mail had stopped working because of a botch in the formatting of content I'd added to my zone files, so:</span></p><pre><code>journalctl --no-pager --since "2024-09-11 15:20:30" -u named _PID=5080</code></pre><span><br>Gave me </span><i><span>just</span></i><span> the log entries I needed in order to validate that I had no zone-breaking errors in the new content.<br><br></span><a href="https://evil.social/tags/linux" rel="nofollow noopener" target="_blank">#linux</a><span><br></span><a href="https://evil.social/tags/dns" rel="nofollow noopener" target="_blank">#dns</a><span><br></span><a href="https://evil.social/tags/journald" rel="nofollow noopener" target="_blank">#journald</a><p></p>
Peter Czanik<p><span class="h-card" translate="no"><a href="https://fosstodon.org/@shuLhan" class="u-url mention">@<span>shuLhan</span></a></span> <span class="h-card" translate="no"><a href="https://mindly.social/@cazabon" class="u-url mention">@<span>cazabon</span></a></span> Well, based on my experiences with <a href="https://fosstodon.org/tags/journald" class="mention hashtag" rel="tag">#<span>journald</span></a> as a <a href="https://fosstodon.org/tags/syslog_ng" class="mention hashtag" rel="tag">#<span>syslog_ng</span></a> guy, my expectation is that around 5-10 years of security nightmares are about to come with <a href="https://fosstodon.org/tags/run0" class="mention hashtag" rel="tag">#<span>run0</span></a>:</p><p><a href="https://www.syslog-ng.com/community/b/blog/posts/systemd-journald-vs-syslog-ng" target="_blank" rel="nofollow noopener" translate="no"><span class="invisible">https://www.</span><span class="ellipsis">syslog-ng.com/community/b/blog</span><span class="invisible">/posts/systemd-journald-vs-syslog-ng</span></a></p><p>Yes, a decade later after journald arrived, I have no problem recommending it. But the first 7-8 years were catastrophic both for users and developers.</p>
Habr<p>Библия systemD: как управлять системой</p><p>Что бы кто не говорил, systemD остается стандартом систем инициализацией в линуксе. И с 100% вероятностью все сервера будут с systemD. И поэтому знать как работать с данной системой инициализации должен знать каждый сисадмин и просто программист. В этой статье мы разберем создание сервисов и юнитов, как облегчить работу при помощи systemd, отслеживать состояние системы и управлять системой.</p><p><a href="https://habr.com/ru/articles/817701/" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="">habr.com/ru/articles/817701/</span><span class="invisible"></span></a></p><p><a href="https://zhub.link/tags/linux" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>linux</span></a> <a href="https://zhub.link/tags/%D1%8F%D0%B4%D1%80%D0%BE" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>ядро</span></a> <a href="https://zhub.link/tags/systemd" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>systemd</span></a> <a href="https://zhub.link/tags/systemctl" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>systemctl</span></a> <a href="https://zhub.link/tags/journald" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>journald</span></a> <a href="https://zhub.link/tags/journalctl" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>journalctl</span></a> <a href="https://zhub.link/tags/%D0%B0%D0%B4%D0%BC%D0%B8%D0%BD%D0%B8%D1%81%D1%82%D1%80%D0%B8%D1%80%D0%BE%D0%B2%D0%B0%D0%BD%D0%B8%D0%B5_linux%D1%81%D0%B8%D1%81%D1%82%D0%B5%D0%BC" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>администрирование_linuxсистем</span></a> <a href="https://zhub.link/tags/%D0%B0%D0%B4%D0%BC%D0%B8%D0%BD%D0%B8%D1%81%D1%82%D1%80%D0%B8%D1%80%D0%BE%D0%B2%D0%B0%D0%BD%D0%B8%D0%B5" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>администрирование</span></a> <a href="https://zhub.link/tags/%D1%81%D0%B8%D1%81%D1%82%D0%B5%D0%BC%D0%B0_%D0%B8%D0%BD%D0%B8%D1%86%D0%B8%D0%B0%D0%BB%D0%B8%D0%B7%D0%B0%D1%86%D0%B8%D0%B8" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>система_инициализации</span></a> <a href="https://zhub.link/tags/pid_1" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>pid_1</span></a> <a href="https://zhub.link/tags/sysvinit" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>sysvinit</span></a> <a href="https://zhub.link/tags/runit" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>runit</span></a> <a href="https://zhub.link/tags/dinit" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>dinit</span></a></p>
Miek Gieben<p>apt-get remove rsyslog <a href="https://mastodon.cloud/tags/journald" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>journald</span></a></p>
GNU/Linux.ch<p>Video: Logdateien unter Linux anzeigen und Fehler analysieren</p><p>Logdateien können wichtige Systemmeldungen enthalten. Ich erkläre dir, wie du unter Linux den Kernel-Ringpuffer und das Journal anzeigen und durchsuchen kannst. </p><p><a href="https://social.anoxinon.de/tags/Log" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Log</span></a> <a href="https://social.anoxinon.de/tags/Journal" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Journal</span></a> <a href="https://social.anoxinon.de/tags/JournalD" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>JournalD</span></a> <a href="https://social.anoxinon.de/tags/systemd" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>systemd</span></a> <a href="https://social.anoxinon.de/tags/Analyse" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Analyse</span></a> <a href="https://social.anoxinon.de/tags/Terminal" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Terminal</span></a> <a href="https://social.anoxinon.de/tags/Bash_Shell" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Bash_Shell</span></a> <a href="https://social.anoxinon.de/tags/Linux" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Linux</span></a></p><p><a href="https://gnulinux.ch/logdateien-unter-linux-anzeigen-und-fehler-analysieren" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">gnulinux.ch/logdateien-unter-l</span><span class="invisible">inux-anzeigen-und-fehler-analysieren</span></a></p>
Elias Probst<p><span class="h-card" translate="no"><a href="https://fosstodon.org/@kernellogger" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>kernellogger</span></a></span> and use "journalctl -k -b-1" to see the Kernel messages of the previous boot.</p><p>Replace "-1" with any of the boot IDs provided by "journalctl --list-boots" (requires the journal to be configured as Storage=persistent in /etc/systemd/journald.conf)</p><p><a href="https://mastodon.social/tags/systemd" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>systemd</span></a> <a href="https://mastodon.social/tags/journald" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>journald</span></a></p>
Peter Czanik<p>My latest syslog-ng git snapshot RPMs for <span class="h-card" translate="no"><a href="https://fosstodon.org/@opensuse" class="u-url mention">@<span>opensuse</span></a></span> / <a href="https://fosstodon.org/tags/SLES" class="mention hashtag" rel="tag">#<span>SLES</span></a> are now available:</p><p><a href="https://www.syslog-ng.com/community/b/blog/posts/rpm-packages-from-syslog-ng-git-head/" target="_blank" rel="nofollow noopener" translate="no"><span class="invisible">https://www.</span><span class="ellipsis">syslog-ng.com/community/b/blog</span><span class="invisible">/posts/rpm-packages-from-syslog-ng-git-head/</span></a></p><p>It enhances <a href="https://fosstodon.org/tags/journald" class="mention hashtag" rel="tag">#<span>journald</span></a> and <a href="https://fosstodon.org/tags/mqtt" class="mention hashtag" rel="tag">#<span>mqtt</span></a> support and adds support for yet another broken <span class="h-card" translate="no"><a href="https://fosstodon.org/@cisco" class="u-url mention">@<span>cisco</span></a></span> timestamp format.</p>
Peter Czanik<p>Even if most people ask me to compare <a href="https://fosstodon.org/tags/systemd" class="mention hashtag" rel="tag">#<span>systemd</span></a>-<a href="https://fosstodon.org/tags/journald" class="mention hashtag" rel="tag">#<span>journald</span></a> vs. syslog-ng, I would say that they complement each other. Combining the two gives you the most flexibility.</p><p><a href="https://www.syslog-ng.com/community/b/blog/posts/systemd-journald-vs-syslog-ng" target="_blank" rel="nofollow noopener" translate="no"><span class="invisible">https://www.</span><span class="ellipsis">syslog-ng.com/community/b/blog</span><span class="invisible">/posts/systemd-journald-vs-syslog-ng</span></a></p><p><a href="https://fosstodon.org/tags/LogManagement" class="mention hashtag" rel="tag">#<span>LogManagement</span></a></p>
Elias Probst<p><span class="h-card"><a href="https://macaw.social/@april" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>april</span></a></span> it's really a shame, barely anyone uses systemd's built-in support for logging structured data to the journal.<br>It's been there for over a decade - I wonder what keeps people/projects from using it? The additional effort, since it's not portable to other systems means traditional means of logging have to be maintained as well?</p><p><a href="https://systemd.io/JOURNAL_NATIVE_PROTOCOL/" rel="nofollow noopener" target="_blank"><span class="invisible">https://</span><span class="ellipsis">systemd.io/JOURNAL_NATIVE_PROT</span><span class="invisible">OCOL/</span></a></p><p><a href="https://mastodon.social/tags/systemd" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>systemd</span></a> <a href="https://mastodon.social/tags/journald" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>journald</span></a> <a href="https://mastodon.social/tags/logging" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>logging</span></a></p>
Peter Czanik<p>Last week I was on sick leave, but today I just finished building my syslog-ng git snapshot packages for <span class="h-card" translate="no"><a href="https://fosstodon.org/@opensuse" class="u-url mention">@<span>opensuse</span></a></span> / <a href="https://fosstodon.org/tags/SLES" class="mention hashtag" rel="tag">#<span>SLES</span></a> &amp; <span class="h-card" translate="no"><a href="https://fosstodon.org/@fedora" class="u-url mention">@<span>fedora</span></a></span> / <a href="https://fosstodon.org/tags/RHEL" class="mention hashtag" rel="tag">#<span>RHEL</span></a>:</p><p><a href="https://www.syslog-ng.com/community/b/blog/posts/rpm-packages-from-syslog-ng-git-head/" target="_blank" rel="nofollow noopener" translate="no"><span class="invisible">https://www.</span><span class="ellipsis">syslog-ng.com/community/b/blog</span><span class="invisible">/posts/rpm-packages-from-syslog-ng-git-head/</span></a></p><p>The <a href="https://fosstodon.org/tags/syslog_ng" class="mention hashtag" rel="tag">#<span>syslog_ng</span></a> master branch mainly received bug fixes (including for <a href="https://fosstodon.org/tags/journald" class="mention hashtag" rel="tag">#<span>journald</span></a>) and cosmetic changes.</p>
Elias Probst<p><span class="h-card"><a href="https://im-in.space/@julian" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>julian</span></a></span> I'm trying to understand, why you would want to store them separately? </p><p>You can split up journals by namespace or UIDs.<br>Alternatively, you can forward your journal to conventional logging services like syslog(-ng) if you need something special like "different retention periods per service".</p><p>See also: <a href="https://www.freedesktop.org/software/systemd/man/journald.conf.html" rel="nofollow noopener" target="_blank"><span class="invisible">https://www.</span><span class="ellipsis">freedesktop.org/software/syste</span><span class="invisible">md/man/journald.conf.html</span></a></p><p><a href="https://mastodon.social/tags/systemd" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>systemd</span></a> <a href="https://mastodon.social/tags/logging" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>logging</span></a> <a href="https://mastodon.social/tags/journald" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>journald</span></a></p>