busybox-initscripts: klogd should not provide logger
On Mon, 7 Jul 2014 21:19:09 –0700
Isaac Dunham wrote:
I noticed a week or two ago that
service crond start
would start klogd and not syslogd; since klogd only logs kernel messages and
syslogd logs application messages, I decided to investigate.
It appears that both the klogd and syslog services provide logger, but
syslog needs klogd.
So I’m wondering: shouldn’t syslog be the only service providing logger,
since klogd doesn’t listen to applications?
I think you are right. This is a bug.
(from redmine: issue id 3156, created on 2014-07-08, closed on 2014-07-30)
- Revision 1df4005f by Natanael Copa on 2014-07-15T16:40:28Z:
main/busybox-initscripts: klogd should not provide logger ref #3156
- Revision 206ee8a8 by Natanael Copa on 2014-07-16T09:45:12Z:
main/busybox-initscripts: klogd should not provide logger fixes #3156 (cherry picked from commit 1df4005f5d3df7e9b28540a43616124bfcad9e85)