Package: syslog-ng Version: 2.0.9-1ubuntu5 Severity: wishlist When running as an unprivileged user there currently only exists the dd workaround I proposed in [1] (see [2] and [3] for a discussion of alternatives).
IMO it would be a lot cleaner to use klogd for kernel ringbuffer forwarding to a syslog-ng process running as a non-root user. Currently syslog-ng declares a conflict with kernel log providers. Is there any reason why this is necessary? Wouldn't it be better to provide a standard installation with: 1) klogd as kernel log provider, recommended (or even depended upon) by syslog-ng 2) syslog-ng running as a non-privileged user by default, pre-configured to receive kernel messages from klogd (if installed) or otherwise using the dd workaround. The problem is that klogd currently depends upon sysklogd package. No quick fix for that. Any ideas? Florian [1] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=503210 [2] https://lists.balabit.hu/pipermail/syslog-ng/2008-November/012236.html [3] https://lists.balabit.hu/pipermail/syslog-ng/2008-November/012241.html -- System Information: n/a -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
