For the record, though the error message from klogd is both misleading
and (for some) a bit scary, the fact that klogd isn't loading System.map
appears to be completely harmless for us.

Our kernels are built with KALLSYMS=y, so we're getting symbol names in
stack traces anyway, despite klogd's inability to do the lookups itself.

-- 
sysklogd cannot find map file
https://bugs.launchpad.net/bugs/277924
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to