chiark / gitweb /
core: don't reset log level to NOTICE if we get quiet on the kernel cmdline
authorLennart Poettering <lennart@poettering.net>
Wed, 4 Feb 2015 00:42:49 +0000 (01:42 +0100)
committerLennart Poettering <lennart@poettering.net>
Wed, 4 Feb 2015 00:47:31 +0000 (01:47 +0100)
commit5e07a79e84ab8b045b9df1a2719f14fc84471a1d
tree39d8e28f093575939ced3e9a86d51672212ffa3b
parentb9be39bfb4ed8e43a7c445831131e44be998eb32
core: don't reset log level to NOTICE if we get quiet on the kernel cmdline

quiet should really just have an effect on the stuff we dump on the
console, not what we log elsewhere.

Hence:

        debug on kernel cmdline → interpreted by every tool, turns up
        log levels to "debug" everywhere.

        quiet on kernel cmdline → interpreted only by PID 1 (and
        obviously the kernel) no alteration of the max log level, but
        turns off status output.

http://lists.freedesktop.org/archives/systemd-devel/2014-December/026271.html
src/core/main.c
src/shared/log.c