All of lore.kernel.org
 help / color / mirror / Atom feed
From: ecordonnier@snap.com
To: openembedded-core@lists.openembedded.org
Cc: Etienne Cordonnier <ecordonnier@snap.com>
Subject: [PATCH 2/2] systemd-conf: stop forwarding journal to syslog by default
Date: Mon, 16 Nov 2026 10:21:03 +0100	[thread overview]
Message-ID: <20261116092104.3160433-2-ecordonnier@snap.com> (raw)
In-Reply-To: <20261116092104.3160433-1-ecordonnier@snap.com>

From: Etienne Cordonnier <ecordonnier@snap.com>

ForwardToSyslog=yes was added in 2014 (67ddca4a55) as a stopgap
because systemd 216 stopped forwarding by default and the oeqa tests
then expected a syslog daemon to receive messages. The tests now fall
back to journalctl, so the override is no longer needed.

On images without a syslog daemon, journald still formats and tries to
forward every message to syslog for nothing, wasting CPU. Images running
a syslog daemon that reads /dev/log must now enable ForwardToSyslog
themselves.

AI-Generated: Uses Claude Code (claude-sonnet-5-5)
Signed-off-by: Etienne Cordonnier <ecordonnier@snap.com>
---
 meta/recipes-core/systemd/systemd-conf/journald.conf | 1 -
 1 file changed, 1 deletion(-)

diff --git a/meta/recipes-core/systemd/systemd-conf/journald.conf b/meta/recipes-core/systemd/systemd-conf/journald.conf
index fd4d969fa7..750fb2f5e8 100644
--- a/meta/recipes-core/systemd/systemd-conf/journald.conf
+++ b/meta/recipes-core/systemd/systemd-conf/journald.conf
@@ -1,3 +1,2 @@
 [Journal]
-ForwardToSyslog=yes
 RuntimeMaxUse=64M
-- 
2.43.0


      reply	other threads:[~2026-11-16  9:21 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-16  9:21 [PATCH 1/2] sysklogd: enable journal forwarding to syslog.socket ecordonnier
2026-11-16  9:21 ` ecordonnier [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20261116092104.3160433-2-ecordonnier@snap.com \
    --to=ecordonnier@snap.com \
    --cc=openembedded-core@lists.openembedded.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.