Comment 8 for bug 523610

Revision history for this message
Matt Zimmerman (mdz) wrote : Re: 20100218 EC2 image (ami-0512fe6c): Cannot read proc file system: 1 - Operation not permitted.

The changelog says this should work with newer kernels:

rsyslog (4.2.0-2ubuntu6) lucid; urgency=low

  * debian/rsyslog.rsyslog-kmsg.upstart:
    - Drop this additional job; kernel changes have meant that rsyslog
      may read from /proc/kmsg directly after dropping privileges.
      LP: #517773
  * debian/rsyslog.preinst:
    - Remove on upgrade
  * debian/rsyslog.conf:
    - Restore to reading from /proc/kmsg

 -- Scott James Remnant <email address hidden> Wed, 17 Feb 2010 12:23:01 +0000

I'm running 2.6.32-12-generic #16-Ubuntu and it definitely does not work there. Even if it works in the latest kernels, this will be a problem for upgrades from Karmic, because rsyslog gets restarted before the kernel is upgraded.