Date: Tue, 28 Jul 2015 16:18:11 +0200
From: Natanael Copa <ncopa@alpinelinux.org>
To: =?ISO-8859-1?B?U/ZyZW4=?= Tempel <soeren+git@soeren-tempel.net>
Cc: alpine-aports@lists.alpinelinux.org
Subject: Re: [alpine-aports] [PATCH] main/busybox: disable syslog to kernel
 printk buffer
Message-ID: <20150728161811.389a8f50@ncopa-desktop.alpinelinux.org>
In-Reply-To: <1438033228-25433-1-git-send-email-soeren+git@soeren-tempel.net>
References: <1438033228-25433-1-git-send-email-soeren+git@soeren-tempel.net>
Precedence: list
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

On Mon, 27 Jul 2015 23:40:28 +0200
S=F6ren Tempel <soeren+git@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
logrotation.

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
fine.

We normally don't try prevent users from shooting themselves in the
foot.

Are there other good reason to apply it? Maybe I am missing something...

-nc


---
Unsubscribe:  alpine-aports+unsubscribe@lists.alpinelinux.org
Help:         alpine-aports+help@lists.alpinelinux.org
---