From: Andreas Hilse <andreas.hilse@ipcomm.de>
To: buildroot@busybox.net
Subject: [Buildroot] sysklogd 1.6: messages from klogd are logged to user facility
Date: Mon, 10 Aug 2020 18:47:32 +0200 (CEST) [thread overview]
Message-ID: <00ee01d66f35$f1363620$d3a2a260$@ipcomm.de> (raw)
In-Reply-To: <20200810163629.2157d61e@windsurf.home>
Hello Thomas,
> BUSYBOX_DEPENDENCIES = \
> ...
> $(if $(BR2_PACKAGE_SYSKLOGD),sysklogd) \
>
> This way Busybox is installed *after* sysklogd, and Busybox installation
> process is careful enough to not overwrite already installed binaries.
> However, klogd being removed from sysklogd, I'm not sure how this will
> end up working: it is possible that Busybox will install its own klogd
> symlink anyway.
It does install its own klogd symlink, but its S02klogd script does not
get installed because BR2_PACKAGE_SYSKLOGD is selected, so it won't be
started.
I just checked: the same goes for rsyslog (busybox klogd link gets
installed). So it should be okay for sysklogd, too?
> What have you made selectable ?
The sysklogd logger utility; configure has an option:
--without-logger Build without extended logger tool, default:
enabled
In case of the logger utility both busybox link (/usr/bin/logger) and
sysklogd binary (/bin/logger) get installed.
Best regards
Andreas
prev parent reply other threads:[~2020-08-10 16:47 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
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 [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='00ee01d66f35$f1363620$d3a2a260$@ipcomm.de' \
--to=andreas.hilse@ipcomm.de \
--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.