On Mon, 27 Jul 2015 23:40:28 +0200
Sören Tempel <soeren+git_at_soeren-tempel.net> wrote:
> I quote the .config file: "klogd should not be used together with syslog
> to kernel printk buffer."
> main/busybox/APKBUILD | 8 ++++----
> main/busybox/busyboxconfig | 10 +++-------
> 2 files changed, 7 insertions(+), 11 deletions(-)
Thanks for the patch.
As I understand, the problem is that klogd will grab kernel messages
(from /dev/klog) and send them to syslog, while syslog -K does the
opposite, makes syslog write log as kernel messages instead of writing
to a file.
This is trick to use 'dmesg' for you syslog and avoid logfile and
So basically, if you enable syslog -K and run klogd, then you will
create a loop, kernel messages -> syslog -> kernel message.
I don't know if its worth disable the feature at compile time. As long
as you don't run klogd and syslogd -K at the same time you should be
We normally don't try prevent users from shooting themselves in the
Are there other good reason to apply it? Maybe I am missing something...
Received on Tue Jul 28 2015 - 16:18:11 GMT