kernel-packages team mailing list archive

[Chris J Arges <1274444@xxxxxxxxxxxxxxxxxx>]

Ok so the <N> is both the priority and facility numbers combined. Where
the lowest 3 bits are priority and any upper bits are facility. By
default any userspace log is 1, and only kernel messages originating
from the kernel can be 0.

http://www.mjmwired.net/kernel/Documentation/ABI/testing/dev-kmsg

So this sounds like something that needs to be patched in sysloggers and
not the kernel.

** Also affects: rsyslog (Ubuntu)
   Importance: Undecided
       Status: New

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1274444

Title:
  echo string to /dev/kmsg fails to appear on /var/log/syslog

Status in “linux” package in Ubuntu:
  In Progress
Status in “rsyslog” package in Ubuntu:
  New

Bug description:
  [Impact]
  In the precise 3.2 series kernel writing strings to /dev/kmsg appears and dmesg and /var/log/syslog, in 3.5 series kernel this does not happen properly even with the equivalent userspace packages.

  I've already done a coarse bisect,
  works v3.4
  fails in v3.5-rc1

  [Test Case]
  Run the following script as root:

  #!/bin/bash
  STRING=$(cat /dev/urandom | tr -dc 'a-zA-Z0-9' | head -c 32)
  > /var/log/syslog
  echo $STRING > /dev/kmsg
  sleep 5
  grep $STRING /var/log/syslog
  # This should return 0.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1274444/+subscriptions