This bug was fixed in the package rsyslog - 4.2.0-1ubuntu1
---------------
rsyslog (4.2.0-1ubuntu1) karmic; urgency=low
* Run as rsyslog:rsyslog (LP: #250827, LP: #388608)
- debian/control: Depend on adduser
- debian/rsyslog.postinst: Create syslog user
- debian/rsyslog.postrm: Delete syslog user on purge
- debian/rsyslog.conf: Use DropPriv config fields
* Allow reading /proc/kmsg when non-root
- debian/rsyslog.init: Spawn a dd instance that shovels the /proc/kmsg
data to a pipe that rsyslog can read (based on Martin Pitt's similar
change to sysklogd).
- debian/patches/deroot.patch: Support a KLogPath config field
to change where the klog plugin looks and only start input modules
after we drop privileges, as reading when root interferes with
future reads as syslog.
- debian/rsyslog.conf: Use KLogPath field to point to dd pipe
* Cleanly upgrade from sysklogd
- debian/default.conf, debian/rsyslog.conf:
Break out the default rules into their own config file
- debian/rsyslog.install: Install it in /usr/share/rsyslog
- debian/rsyslog.postinst: If present, copy /etc/syslog.conf into
/etc/rsyslog.d/default.conf. Then merge our own default.conf
-- Michael Terry <michael.te...@canonical.com> Mon, 29 Jun 2009
08:37:43 -0400
** Changed in: rsyslog (Ubuntu)
Status: New => Fix Released
--
rsyslog does not create a system user like sysklogd
https://bugs.launchpad.net/bugs/250827
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
