<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<div class="moz-cite-prefix">On 1/8/20 2:33 AM,
<a class="moz-txt-link-abbreviated" href="mailto:yanfei.xu@windriver.com">yanfei.xu@windriver.com</a> wrote:<br>
</div>
<blockquote type="cite"
cite="mid:1578468806-411330-1-git-send-email-yanfei.xu@windriver.com">
<pre class="moz-quote-pre" wrap="">From: Yanfei Xu <a class="moz-txt-link-rfc2396E" href="mailto:yanfei.xu@windriver.com"><yanfei.xu@windriver.com></a>
klogd and syslogd's type has been changed from "forking" to "simple"
in service file used by systemd. It causes klogd will boot on the
heels of syslogd in a very short time and result in a empty kern.log.
Adding a delay before klogd connecting syslogd can solve this.
--------------------------
steps to reproduce:
Bitbake core-image-minimal with configuration as follow：
MACHINE ??= "genericx86-64"
DISTRO_FEATURES_append = " systemd"
VIRTUAL-RUNTIME_init_manager = "systemd"
VIRTUAL-RUNTIME_base-utils-syslog = "sysklogd"
After your system booting successfully, you will find /var/log/kern.log
is empty.
-------------------------
Signed-off-by: Yanfei Xu <a class="moz-txt-link-rfc2396E" href="mailto:yanfei.xu@windriver.com"><yanfei.xu@windriver.com></a>
---
meta/recipes-extended/sysklogd/sysklogd.inc | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/meta/recipes-extended/sysklogd/sysklogd.inc b/meta/recipes-extended/sysklogd/sysklogd.inc
index 774d23b..ff8188d 100644
--- a/meta/recipes-extended/sysklogd/sysklogd.inc
+++ b/meta/recipes-extended/sysklogd/sysklogd.inc
@@ -21,7 +21,7 @@ SRC_URI = <a class="moz-txt-link-rfc2396E" href="git://github.com/troglobit/sysklogd.git;nobranch=1\">"git://github.com/troglobit/sysklogd.git;nobranch=1 \
"</a>
S = "${WORKDIR}/git"
-EXTRA_OECONF = "--with-systemd=${systemd_system_unitdir} --with-klogd --without-logger"
+EXTRA_OECONF = "--with-systemd=${systemd_system_unitdir} --with-klogd --with-klogd-delay=1 --without-logger"
do_install_append () {
install -d ${D}${sysconfdir}
</pre>
</blockquote>
<p>This might be a sensible work-around for the 3.0/zeus releaese
but<br>
for the master branch it is not acceptable.</p>
<p>A delay is often a work-around especially if it's a round number
like 1 second.<br>
A slower machine may not be fixed by a 2 second delay and so we'd
be <br>
tempted to delay 2 or 10 seconds, soon enough your system is only
fully<br>
initialized after a fortnight. ;-)<br>
</p>
<p>Also and more importantly we should be looking at what upstream
is doing and<br>
for sysklogd, they are _removing_ klogd:</p>
<p><a class="moz-txt-link-freetext" href="https://github.com/troglobit/sysklogd/commits/6bb6672ebf797078d1c31c83dcf960f767808557">https://github.com/troglobit/sysklogd/commits/6bb6672ebf797078d1c31c83dcf960f767808557</a></p>
Remove klogd from the sysklogd project
<div class="commit-desc">
<pre class="moz-signature" cols="72"> This patch removes one of the traditionally key pieces of the sysklogd
project, klogd. Now that syslogd performs logging of kernel messages
we no longer require a separate daemon for that.
Signed-off-by: Joachim Nilsson <a class="moz-txt-link-rfc2396E" href="mailto:troglobit@gmail.com"><troglobit@gmail.com></a>
The question to answer is, do all the syslog daemons:
- syslogd
- rsyslogd
- systemd/journald
- others?
have the support that we klogd provides.
--
# Randy MacLeod
# Wind River Linux
</pre>
</div>
</body>
</html>