Again, I think the core problem the problem is not intrinsically with rsyslogd.
While I agree that there ought to be a flooding failsafe in rsyslogd, the base problem here is the CPU temperature sensors algorithm in the kernel and the reporting of errant messages. I earlier thought this was due to lm-sensors/libsensors3/libsensors4, but those aren't loaded at the initial install. HAL now does those functions, so it seems to me that a module such as hal-addon-acpi is the culprit for the aberrant message stream. The root problem is the enforced checking of motherboard/CPU sensors. Because there are is many motherboards/CPUs that do not have sensor drivers in Linux for their fan speeds and temperature sensors, the sensor checking algorithm must be optional. It is not, in the current kernel, and instead of a single message that sensors are unable to be polled (due to lack of drivers), the kernel module instead returns repeated "temperature out of range" messages. This is the bug. Jaunty did not rely on HAL in this manner (and Jaunty did not mandate CPU sensor monitoring). This serious bug is giving Linux (and by extension Ubuntu) a big black eye with the Karmic release. This should be upgraded to urgent. -- /var/log fills up with "all normal" messages @ about 575/sec fill up the available space https://bugs.launchpad.net/bugs/453444 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
