tree 20256a5b0d8abd6493e0dbb203b01b11ecdb2455
parent ea4efd0d233bec1306194e611c95e74f03c951e4
author mukesh agrawal <quiche@chromium.org> 1402449914 -0700
committer chrome-internal-fetch <chrome-internal-fetch@google.com> 1402547470 +0000

chromeos-init: improve kernel logging

Some messages were appearing in the kernel ring-buffer (as examined
by dmesg), but not in /var/log/messages. It turns out that rsyslogd
defaults to filtering messages read from /proc/kmsg, so that only
kernel messages are candidates for logging.

This default is bad for us, since init (upstart) logs to the kernel
ring buffer. Resolve the problem, by disabling rsyslogd's filtering
of these messages.

BUG=chromium:383075
TEST=platform_LogNonKernelKmsg
CQ-DEPEND=CL:203319

Change-Id: I73075dcb12e1a37ea93f9bb690c68862849bd9ba
Reviewed-on: https://chromium-review.googlesource.com/203332
Tested-by: mukesh agrawal <quiche@chromium.org>
Reviewed-by: Mike Frysinger <vapier@chromium.org>
Commit-Queue: mukesh agrawal <quiche@chromium.org>