Comment 13 for bug 1366829

Revision history for this message
Paul Donohue (s-launchpad-paulsd-com) wrote :

Test case:
* Install rsyslog 7.4.4-1ubuntu2.1 on an Ubuntu system that runs inside an OpenVZ container (If necessary, use ProxMox to quickly establish an OpenVZ container environment)
* Verify that '$KLogPermitNonKernelFacility on' is set in /etc/rsyslog.conf
* Restart rsyslog to make sure any changes to the binaries/config are picked up
* Run 'top' and observe that the rsyslogd process is running at 100% CPU. When working properly, the rsyslogd process should generally be idle.