Bug 7081
| Summary: | Log messages duplicates to console | ||
|---|---|---|---|
| Product: | IO/Storage | Reporter: | Paul (pauldrynoff) |
| Component: | Other | Assignee: | io_other |
| Status: | CLOSED CODE_FIX | ||
| Severity: | normal | CC: | akpm |
| Priority: | P2 | ||
| Hardware: | i386 | ||
| OS: | Linux | ||
| Kernel Version: | 2.6.18-rc5 | Subsystem: | |
| Regression: | --- | Bisected commit-id: | |
Presumably someone changed a printk facility level. Please identify the specific messages, so we can find them in the kernel source. This was fault of lock validator, and it was fixed, as I can see in release. |
Most recent kernel where this bug did not occur: 2.6.17 Distribution: Gentoo Hardware Environment: Software Environment: syslog-ng 1.6.9 Problem Description: After using 2.6.18-rc5 for while, I saw that some message that in 2.6.17 go to /var/log/*, in 2.6.18-rc5 go also to console. For example, I have such iptables rule: iptables -A INPUT -p tcp -j LOG --log-prefix "UNMATCHED TCP packet: " and such syslog-ng rule: destination security { file("/var/log/security"); }; filter f_security { facility(security) or match("UNMATCHED TCP... log { source(src); filter(f_security); destination(security); }; in 2.6.17 these message just go to /var/log/security in 2.6.18-rc5 they are also duplicates to current console, this is really annoing. Steps to reproduce: