Skip to contentSkip to conversation

OT: Logs on console

DISCUSSION Victor Wren 5 participants 5 messages Jul 16, 2004 – Jul 17, 2004

lore
Share & tools
lore
#0 lore raw

This is off-topic, but IPTABLES is the only place I have this problem. I've tried several different configurations to try to stop it from logging dropped packets to my monitor. I've put "kern.none /dev/console" in my syslog.conf, and it is STILL throwing the logs entries to the monitor, even when nobody is logged in! I've got all my log entries set to --log-level info, and they're getting properly logged to an iptables logfile, but they are still showing up on the screen (the tutorials say this isn't an iptables issue, but ONLY the iptables logs are showing up on the screen). I've been searching the internet for days trying to STOP THE MADNESS!

Anybody got any suggestions?

Victor
sysadmin, Timension Inc.

#1 lore raw
Quoted 5 lines · Victor Wren

This is off-topic, but IPTABLES is the only place I have this problem.

I've got all my log entries set to --log-level
info, and they're getting properly logged to an iptables logfile, but they are still showing up on the screen

Show us the contents of your /etc/syslog.conf

Regards,

Antony.

Signature · 7 lines
"The problem with television is that the people must sit and keep their eyes 
glued on a screen; the average American family hasn't time for it."

 - New York Times, following a demonstration at the 1939 World's Fair.

                                                     Please reply to the list;
                                                           please don't CC me.
#2 lore raw
Quoted 11 lines · Victor Wren
Quoted 6 lines

This is off-topic, but IPTABLES is the only place I have this problem.

I've got all my log entries set to --log-level
info, and they're getting properly logged to an iptables logfile, but they are still showing up on the screen

Show us the contents of your /etc/syslog.conf

auth,authpriv.* -/var/log/auth
*.*;auth,authpriv.none -/var/log/messages
kern.none /dev/console
daemon.* -/var/log/daemon
kern.* -/var/log/kern
kern.=info -/var/log/iptables
mail.* -/var/log/mail
user.* -/var/log/user
cron.* -/var/log/cron
*.emerg *
local7.* /var/log/boot.log

I think I may have found a clue. kernel message logging is handled by klogd.
the manfile for klogd says that it defaults to putting all messages of
priority higher than 7 (debug) to the screen (info is 6) unless launched with "-c [level]" I see no mention of any use of a configuration file in klogd, and it appears to hand kernel messages to syslogd after prioritizing, but has the ability to send messages to the screen (or files) itself.

Ha. Changing it to klogd -c 3" seems to have cured it. Now to fix it on my home network!

Victor

Victor Wren
Designer,
Timension Inc.
1350 C Pear Ave
Mountain View CA 94043
(650) 564-9397
Fax: (650) 564-9398
Opinions stated in this letter are not necessarily those of Timension Inc. or the management. All Rights Reserved. No spitting.

#3 lore raw
In reply to Antony Stone

This is done by printk, and it can be changed via sysct, look what i have in sysctl to stop printk showing the logs to the monitor:
kernel.printk= 3 4 1 7
or:
echo "3 4 1 7" > /proc/sys/kernel/printk

Quoted 24 lines · Antony Stone
Quoted 5 lines · Victor Wren

This is off-topic, but IPTABLES is the only place I have this problem.

I've got all my log entries set to --log-level
info, and they're getting properly logged to an iptables logfile, but they are still showing up on the screen

Show us the contents of your /etc/syslog.conf

Regards,

Antony.

--
"The problem with television is that the people must sit and keep their eyes glued on a screen; the average American family hasn't time for it."

- New York Times, following a demonstration at the 1939 World's Fair.

Please reply to the list;
please don't CC me.

#4 lore raw

Re: OT: Logs on console (nfcan: addressed to exclusive sender for this address)

In reply to Victor Wren
Quoted 6 lines · On 2004.07.16 15:25, Victor Wren - [email protected] wrote:

This is off-topic, but IPTABLES is the only place I have this problem. I've tried several different configurations to try to stop it from logging dropped

packets to my monitor. I've put "kern.none /dev/console" in my syslog.conf, and it is STILL throwing the logs entries to the monitor, even when nobody is

Quoted 8 lines

logged in! I've got all my log entries set to --log-level info, and they're getting properly logged to an iptables logfile, but they are still showing up

on the screen (the tutorials say this isn't an iptables issue, but ONLY the iptables logs are showing up on the screen). I've been searching the internet for days trying to STOP THE MADNESS!

Anybody got any suggestions?

I had a problem like this too, and it also drove me nuts.

At least on my RH system, there is a file /etc/sysconfig/syslog. This file contains optional settings, including logging levels, for BOTH syslogd and klogd!
In this file are some lines like this:

# See klogd(8) for more details
KLOGD_OPTIONS="-x -c 1"

I added the -c 1 to KLOGD_OPTIONS so that
only high priority messages would print.
Look at the man page for more.

Hope this helps,

Jim