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 protected]> 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.
** Changed in: rsyslog (Ubuntu)
Status: New => Triaged
** Changed in: rsyslog (Ubuntu)
Importance: Undecided => High
** Tags added: regression-potential
** Also affects: rsyslog (Ubuntu Lucid)
Importance: High
Status: Triaged
** Changed in: rsyslog (Ubuntu Lucid)
Assignee: (unassigned) => Scott James Remnant (scott)
** Changed in: rsyslog (Ubuntu Lucid)
Milestone: None => lucid-alpha-3
--
20100218 EC2 image (ami-0512fe6c): Cannot read proc file system: 1 - Operation
not permitted.
https://bugs.launchpad.net/bugs/523610
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
