why not upgrade rsyslogd? Using debian testing's 4.4.2 package fixed it for me.
On Wed, Feb 24, 2010 at 12:41 PM, Scott James Remnant
<email address hidden> wrote:
> Something like this seems the sanest approach.
>
> After opening /proc/kmsg, attempt a zero-byte read from it - if that
> fails with EPERM then we don't load the klog module
>
> ** Attachment added: "deroot.patchpatch"
> http://launchpadlibrarian.net/39737237/deroot.patchpatch
>
> --
> rsyslogd spins CPU on some kernels
> https://bugs.launchpad.net/bugs/523610
> You received this bug notification because you are a direct subscriber
> of a duplicate bug.
>
why not upgrade rsyslogd? Using debian testing's 4.4.2 package fixed it for me.
On Wed, Feb 24, 2010 at 12:41 PM, Scott James Remnant launchpadlibrar ian.net/ 39737237/ deroot. patchpatch /bugs.launchpad .net/bugs/ 523610
<email address hidden> wrote:
> Something like this seems the sanest approach.
>
> After opening /proc/kmsg, attempt a zero-byte read from it - if that
> fails with EPERM then we don't load the klog module
>
> ** Attachment added: "deroot.patchpatch"
> http://
>
> --
> rsyslogd spins CPU on some kernels
> https:/
> You received this bug notification because you are a direct subscriber
> of a duplicate bug.
>