From: <mingli.yu@windriver.com>
To: <openembedded-core@lists.openembedded.org>
Subject: [PATCH] busybox: fix for syslog service in systemd
Date: Tue, 26 Jul 2016 15:33:17 +0800 [thread overview]
Message-ID: <1469518399-22052-1-git-send-email-mingli.yu@windriver.com> (raw)
commit 9943ffeeed5c612d1bc44a12607d553f7704dc7e
Author: Chen Qi <Qi.Chen@windriver.com>
Date: Thu Sep 11 04:55:35 2014 -0400
busybox: fix for syslog service in systemd
This patch includes the following changes:
1. Explicitly set StandardOutput of the log daemon to null.
This would avoid creating a feedback loop of the syslog service.
See link below for more information.
http://www.freedesktop.org/wiki/Software/systemd/syslog/
2. Use ALTERNATIVE machanism to manage the syslog service file.
This is because that other package may also provide a syslog
implementation.
3. Make the syslog daemon socket activated only. Otherwise, things
would crash if we install busybox-syslog and other syslog packages
together in one image.
Signed-off-by: Chen Qi <Qi.Chen@windriver.com>
Signed-off-by: Mingli Yu <mingli.yu@windriver.com>
commit 425d7b8605612cdc65daf2c1ef6cf5655ad8f227
Author: Yadi.hu <yadi.hu@windriver.com>
Date: Wed Jun 1 17:54:17 2016 -0700
busybox: handle syslog
If CONFIG_KLOGD is not enabled, then the related service file should
not be installed, The error message is below:
Cannot add dependency job for unit busybox-klogd.service,
ignoring: Unit busybox-klogd.service failed to load:
No such file or directory.
So we should first check the configuration before we install these
service files.
Signed-off-by: Yadi.hu <yadi.hu@windriver.com>
Signed-off-by: Mingli Yu <mingli.yu@windriver.com>
next reply other threads:[~2016-07-26 7:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-26 7:33 mingli.yu [this message]
2016-07-26 7:33 ` [PATCH 1/2] busybox: fix for syslog service in systemd mingli.yu
2016-07-29 16:44 ` Aníbal Limón
2016-07-26 7:33 ` [PATCH 2/2] busybox: handle syslog mingli.yu
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=1469518399-22052-1-git-send-email-mingli.yu@windriver.com \
--to=mingli.yu@windriver.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox