After more investigation, it seems that tail -f is not the right way to
reproduce this. Using cat or dd shows that messages are actually getting
out of /proc/kmsg. Strace shows that klogd is actually reading them, and
is doing a sendto() to send them to syslog.
However, the problem is that they ar
The most recent message (in /var/log/kern.log.0) on my system is:
Jul 11 09:16:49 mizar kernel: Kernel log daemon terminating.
and I was running 2.6.26-2.6 at that time, so this has been broken for
quite a while.
--
No messages in /proc/kmsg
https://bugs.launchpad.net/bugs/255635
You received t
I've reproduced this. Working through the motions...
** Changed in: linux (Ubuntu Intrepid)
Assignee: Ubuntu Kernel Team (ubuntu-kernel-team) => Ben Collins
(ben-collins)
Status: Triaged => In Progress
Target: None => intrepid-alpha-5
--
No messages in /proc/kmsg
https://bugs
I used this to reliably and conveniently produce kernel messages and
verify that dmesg has new stuff:
$ sudo dmesg -c
$ sudo /etc/init.d/apparmor restart
Reloading AppArmor profiles : done.
$ sudo dmesg -c
[68804.887693] type=1505 audit(1218098412.816:494): operation="profile_replace"
name="/usr/
