[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20160426110905.GR3448@twins.programming.kicks-ass.net>
Date: Tue, 26 Apr 2016 13:09:05 +0200
From: Peter Zijlstra <peterz@...radead.org>
To: Bjørn Mork <bjorn@...k.no>
Cc: Ingo Molnar <mingo@...nel.org>,
Steven Rostedt <rostedt@...dmis.org>,
Linus Torvalds <torvalds@...ux-foundation.org>,
LKML <linux-kernel@...r.kernel.org>,
Borislav Petkov <bp@...en8.de>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
Andrew Morton <akpm@...ux-foundation.org>,
Uwe Kleine-König
<u.kleine-koenig@...gutronix.de>
Subject: Re: [PATCH v2] printk: Add kernel parameter to disable writes to
/dev/kmsg
On Tue, Apr 26, 2016 at 12:43:49PM +0200, Bjørn Mork wrote:
> Ingo Molnar <mingo@...nel.org> writes:
>
> > static int parse_proc_cmdline_item(const char *key, const char *value) {
> >
> > /*
> > * The systemd.log_xyz= settings are parsed by all tools, and
> > * so is "debug".
> > *
> > * However, "quiet" is only parsed by PID 1, and only turns of
> > * status output to /dev/console, but does not alter the log
> > * level.
> > */
> >
> > if (streq(key, "debug") && !value)
> > log_set_max_level(LOG_DEBUG);
> >
> > else if (streq(key, "systemd.log_target") && value) {
> >
> > Why systemd does this fully knowing that other software (such as the kernel)
> > already uses 'debug', while systemd already has the 'system.*' parameter namespace
> > is left up to the reader...
>
> A couple of links to save that reader from making futile comments:
> https://lkml.org/lkml/2014/4/2/415
> https://bugs.freedesktop.org/show_bug.cgi?id=76935
Thanks for providing the links, I did remember all that.
Its one of the many reasons why I recommend against running
systemd(isease).
Powered by blists - more mailing lists