On Sat, Jun 24, 2006 at 12:58:42AM +0200, Erik Persson wrote: > I tried with klogd -c 0 but the messages just kept on coming. It seems > that the minimal allowed log level for kernel messages was set to 4 on > the router and klogd -c 0 thus didn't change the kernel log level as I > thought. This solves the problem since I now know what caused it. I will > probably change the iptables log level to debug to get rid of the messages. Did you restart klogd? I don't believe it will change unless you stop the old running klogd and restart it. If you didn't stop the previously running one, the new one you started won't do anything, except exit with an error message, "Already running." There might be a slightly easier way... The dmesg command, in addition to dumping the kernel's message buffer to the screen, can set the maximum priority (number) of messages which get logged to the console. For example: dmesg -n 1 This will log only panic messages to the console. IIRC the default level of iptables messages is 5 (warn), so this will prevent the messages from being printed to the console. You can add it to your init scripts somewhere, or your script for starting your iptables rules... If you want to receive kernel messages on the console for priorities higher than warn, you should be able to use up to dmesg -n 4 and still eliminate the messages from being printed. In practice, I find that having the messages logged to syslog is enough, so logging only critical messages works out fine. -- Derek D. Martin http://www.pizzashack.org/ GPG Key ID: 0x81CFE75D
Attachment:
pgpGaRUH189uV.pgp
Description: PGP signature