Hide Forgot
Description of problem: irqbalance is filling the log files with useless information like this: Jan 17 15:07:29 ... /usr/sbin/irqbalance: Load average increasing, re-enabling all cpus for irq balancing Jan 17 15:08:29 ... /usr/sbin/irqbalance: Load average increasing, re-enabling all cpus for irq balancing Jan 17 15:08:39 ... /usr/sbin/irqbalance: Load average increasing, re-enabling all cpus for irq balancing Jan 17 15:09:29 ... /usr/sbin/irqbalance: Load average increasing, re-enabling all cpus for irq balancing Jan 17 15:11:59 ... /usr/sbin/irqbalance: Load average increasing, re-enabling all cpus for irq balancing Jan 17 15:12:19 ... /usr/sbin/irqbalance: Load average increasing, re-enabling all cpus for irq balancing Jan 17 15:12:29 ... /usr/sbin/irqbalance: Load average increasing, re-enabling all cpus for irq balancing Jan 17 15:12:59 ... /usr/sbin/irqbalance: Load average increasing, re-enabling all cpus for irq balancing Jan 17 15:15:29 ... /usr/sbin/irqbalance: Load average increasing, re-enabling all cpus for irq balancing Jan 17 15:16:09 ... /usr/sbin/irqbalance: Load average increasing, re-enabling all cpus for irq balancing Jan 17 15:16:19 ... /usr/sbin/irqbalance: Load average increasing, re-enabling all cpus for irq balancing Jan 17 15:16:39 ... /usr/sbin/irqbalance: Load average increasing, re-enabling all cpus for irq balancing Jan 17 15:17:29 ... /usr/sbin/irqbalance: Load average increasing, re-enabling all cpus for irq balancing Jan 17 15:17:49 ... /usr/sbin/irqbalance: Load average increasing, re-enabling all cpus for irq balancing Jan 17 15:18:09 ... /usr/sbin/irqbalance: Load average increasing, re-enabling all cpus for irq balancing Jan 17 15:18:59 ... /usr/sbin/irqbalance: Load average increasing, re-enabling all cpus for irq balancing Jan 17 15:20:09 ... /usr/sbin/irqbalance: Load average increasing, re-enabling all cpus for irq balancing Jan 17 15:20:29 ... /usr/sbin/irqbalance: Load average increasing, re-enabling all cpus for irq balancing Jan 17 15:23:39 ... /usr/sbin/irqbalance: Load average increasing, re-enabling all cpus for irq balancing Jan 17 15:26:59 ... /usr/sbin/irqbalance: Load average increasing, re-enabling all cpus for irq balancing Jan 17 15:32:49 ... /usr/sbin/irqbalance: Load average increasing, re-enabling all cpus for irq balancing Jan 17 15:33:39 ... /usr/sbin/irqbalance: Load average increasing, re-enabling all cpus for irq balancing Jan 17 15:35:59 ... /usr/sbin/irqbalance: Load average increasing, re-enabling all cpus for irq balancing Jan 17 15:39:19 ... /usr/sbin/irqbalance: Load average increasing, re-enabling all cpus for irq balancing Jan 17 15:39:29 ... /usr/sbin/irqbalance: Load average increasing, re-enabling all cpus for irq balancing Jan 17 15:41:29 ... /usr/sbin/irqbalance: Load average increasing, re-enabling all cpus for irq balancing Jan 17 15:44:59 ... /usr/sbin/irqbalance: Load average increasing, re-enabling all cpus for irq balancing Jan 17 15:46:49 ... /usr/sbin/irqbalance: Load average increasing, re-enabling all cpus for irq balancing Jan 17 15:48:09 ... /usr/sbin/irqbalance: Load average increasing, re-enabling all cpus for irq balancing Jan 17 15:51:19 ... /usr/sbin/irqbalance: Load average increasing, re-enabling all cpus for irq balancing Version-Release number of selected component (if applicable): irqbalance-1.0.3-1.fc16.x86_64 systemd-37-3.fc16.x86_64 How reproducible: always Additional info: see also bug 727315 for which such behaviour appears to be fixed now. Note that I think that such adjustments should be easy to be made by the end user nd _not_ require new versions of any packages to be installed. Think of the sysadmin who needs to turn on debugging here and turn it off there...
Should be fixed with 781578 *** This bug has been marked as a duplicate of bug 781578 ***
(In reply to comment #0) > Additional info: see also bug 727315 for which such behaviour appears to be > fixed now. Note that bug 727315 was a bug assigned to the systemd component because logind (the daemon with the bug) is shipped in the systemd package. But that does not imply that every buggy program that does syslog(LOG_INFO, "SPAM! SPAM! SPAM!\n") is systemd's fault. > Note that I think that such adjustments should be easy to be made by the end > user nd _not_ require new versions of any packages to be installed. Think of > the sysadmin who needs to turn on debugging here and turn it off there... I believe rsyslog provides configuration options for fine-tuned filtering of messages.