All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] sysklogd 1.6: messages from klogd are logged to user facility
Date: Wed, 5 Aug 2020 22:51:53 +0200	[thread overview]
Message-ID: <20200805225153.7e4bb864@windsurf.home> (raw)
In-Reply-To: <01bd01d66b51$a7eba690$f7c2f3b0$@ipcomm.de>

Hello Andreas,

On Wed, 5 Aug 2020 19:55:50 +0200 (CEST)
Andreas Hilse <andreas.hilse@ipcomm.de> wrote:

> there is an issue with sysklogd 1.6 (buildroot 2020.02.3).
> 
> The package includes its own implementation of openlog/syslog/vsyslog in
> src/syslog.c to be able to log kernel messages to the kern facility.
> The included syslog/vsyslog functions are not the ones getting executed,
> thus kernel messages are marked with the user facility when they arrive in
> syslogd.
> I guess there was a change in the Makefile or glibc 2.22-2.29 which
> results in taking precedence for these functions compared to sysklogd
> 1.5.1 (buildroot 2016.08).
> 
> Can you suggest a workaround/patch for this or are there plans to move to
> a newer version of sysklogd?
> Or should we just switch to rsyslog/syslog-ng?

I am not really familiar with the internals of sysklogd, but there are
definitely newer versions available:

  https://github.com/troglobit/sysklogd/releases

Have you tried if version >= 2.0 would fix your issue ? It seems like
version 2.0 is really a major rewrite.

In any case, we would very much welcome Buildroot patches to update
sysklogd to a newer version.

Best regards,

Thomas
-- 
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com

  reply	other threads:[~2020-08-05 20:51 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-05 17:55 [Buildroot] sysklogd 1.6: messages from klogd are logged to user facility Andreas Hilse
2020-08-05 20:51 ` Thomas Petazzoni [this message]
2020-08-06  9:46   ` Andreas Hilse
2020-08-10  8:39     ` Andreas Hilse
2020-08-10 14:36       ` Thomas Petazzoni
2020-08-10 16:47         ` Andreas Hilse

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=20200805225153.7e4bb864@windsurf.home \
    --to=thomas.petazzoni@bootlin.com \
    --cc=buildroot@busybox.net \
    /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.