All of lore.kernel.org
 help / color / mirror / Atom feed
* Re: OT: Logs on console
  2004-07-16 19:25 OT: Logs on console Victor Wren
@ 2004-07-16 18:42 ` Antony Stone
  2004-07-16 20:28   ` Victor Wren
  2004-07-17  2:24   ` George Alexandru Dragoi
  2004-07-16 18:52 ` OT: Logs on console (nfcan: addressed to exclusive sender for this address) Jim Laurino
  1 sibling, 2 replies; 5+ messages in thread
From: Antony Stone @ 2004-07-16 18:42 UTC (permalink / raw)
  To: netfilter

On Friday 16 July 2004 8:25 pm, Victor Wren wrote:

> 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.



^ permalink raw reply	[flat|nested] 5+ messages in thread

* Re: OT: Logs on console (nfcan: addressed to exclusive sender for this address)
  2004-07-16 19:25 OT: Logs on console Victor Wren
  2004-07-16 18:42 ` Antony Stone
@ 2004-07-16 18:52 ` Jim Laurino
  1 sibling, 0 replies; 5+ messages in thread
From: Jim Laurino @ 2004-07-16 18:52 UTC (permalink / raw)
  To: netfilter

On 2004.07.16 15:25, Victor Wren  - vwren_netfilter@timension.com 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
> 
> 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


^ permalink raw reply	[flat|nested] 5+ messages in thread

* OT: Logs on console
@ 2004-07-16 19:25 Victor Wren
  2004-07-16 18:42 ` Antony Stone
  2004-07-16 18:52 ` OT: Logs on console (nfcan: addressed to exclusive sender for this address) Jim Laurino
  0 siblings, 2 replies; 5+ messages in thread
From: Victor Wren @ 2004-07-16 19:25 UTC (permalink / raw)
  To: netfilter

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.


^ permalink raw reply	[flat|nested] 5+ messages in thread

* Re: OT: Logs on console
  2004-07-16 18:42 ` Antony Stone
@ 2004-07-16 20:28   ` Victor Wren
  2004-07-17  2:24   ` George Alexandru Dragoi
  1 sibling, 0 replies; 5+ messages in thread
From: Victor Wren @ 2004-07-16 20:28 UTC (permalink / raw)
  To: netfilter



> On Friday 16 July 2004 8:25 pm, Victor Wren wrote:
> 
> > 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.



^ permalink raw reply	[flat|nested] 5+ messages in thread

* Re: OT: Logs on console
  2004-07-16 18:42 ` Antony Stone
  2004-07-16 20:28   ` Victor Wren
@ 2004-07-17  2:24   ` George Alexandru Dragoi
  1 sibling, 0 replies; 5+ messages in thread
From: George Alexandru Dragoi @ 2004-07-17  2:24 UTC (permalink / raw)
  To: netfilter

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

On Fri, 16 Jul 2004 19:42:32 +0100, Antony Stone
<antony@soft-solutions.co.uk> wrote:
> On Friday 16 July 2004 8:25 pm, Victor Wren wrote:
> 
> > 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.
> 
>


^ permalink raw reply	[flat|nested] 5+ messages in thread

end of thread, other threads:[~2004-07-17  2:24 UTC | newest]

Thread overview: 5+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2004-07-16 19:25 OT: Logs on console Victor Wren
2004-07-16 18:42 ` Antony Stone
2004-07-16 20:28   ` Victor Wren
2004-07-17  2:24   ` George Alexandru Dragoi
2004-07-16 18:52 ` OT: Logs on console (nfcan: addressed to exclusive sender for this address) Jim Laurino

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.