<feed xmlns='http://www.w3.org/2005/Atom'>
<title>vyos-1x.git/src/etc/systemd/journald.conf.d, branch rolling</title>
<subtitle>VyOS command definitions, scripts, and utilities (mirror of https://github.com/vyos/vyos-1x.git)
</subtitle>
<id>https://git.amelek.net/vyos/vyos-1x.git/atom?h=rolling</id>
<link rel='self' href='https://git.amelek.net/vyos/vyos-1x.git/atom?h=rolling'/>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/vyos-1x.git/'/>
<updated>2026-09-17T20:59:55+00:00</updated>
<entry>
<title>journald: T9183: stop forwarding journal entries to syslog</title>
<updated>2026-09-17T20:59:55+00:00</updated>
<author>
<name>Robert Navarro</name>
<email>crshman@gmail.com</email>
</author>
<published>2026-09-17T20:59:55+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/vyos-1x.git/commit/?id=011b53cbfe8a273a931069ea592ace7a5aa18dbc'/>
<id>urn:sha1:011b53cbfe8a273a931069ea592ace7a5aa18dbc</id>
<content type='text'>
rsyslog reads the journal directly through imjournal (rsyslog.conf.j2 loads
it alongside imuxsock), so journald forwarding the same entries to /dev/log
delivers every non-kernel message twice. Both copies land in /var/log files
and go to every remote syslog target, differing only in PID formatting.

Ship the setting as a journald drop-in here rather than as a full
journald.conf in vyos-build, so the image carries only the settings VyOS
actually overrides. MaxLevelSyslog=debug comes across from that file; the
rest of it was commented-out systemd defaults.

Tested on a live 2026.09.11 router: with the drop-in in place a single
logger event produces one entry, remote targets receive one copy, and
kernel messages (imklog) and HAProxy's own socket are unaffected.
</content>
</entry>
</feed>
