"Jamin W.Collins" <[EMAIL PROTECTED]> writes: > On 01 May 2002 14:58:21 -0600 > "Gary Hennigan" <[EMAIL PROTECTED]> wrote: > > > Since I got no responses to my query about stopping iptables from > > logging crud to the ring buffer (dmesg output) > > Not sure if this pertains to the dmesg output too, but to stop the > iptables log entries from spewing out the console, I needed to add a "-c > 4" to the KLOGD setting in "/etc/init.d/klogd" and restart the klogd > script. > > (snip) > > > I can > > replace ULOG with LOG and get output (to just about everything, dmesg > > output, console, syslog, etc., > > Looks like you too were getting messages to the console. So, the above > change may help.
I've tried everything! The console messages I could live with, but losing the important stuff in dmesg output was the killer. So much stuff from iptables that the important stuff in dmesg output was pushed off the top. Unfortunately *nothing* I tried would get rid of it. I changed to "-c 4" a while ago, but output was still going to the ring buffer (what's apparently shown in the output of dmesg). In fact I killed klogd entirely and *still* got the iptables output shoved into dmesg output. I decided to surrender and use ULOG instead, but now I get nothing. I've installed the testing "ulogd" package and tried installing the original source, with the same result, no output. There's a Debian bug filed against this behavior (#132675 & #1356688) but I'm not hopeful since the bugs are pretty old. Gary -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
