All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jim Laurino <nfcan.x.jimlaur@dfgh.net>
To: netfilter@lists.netfilter.org
Subject: Re: OT: Logs on console (nfcan: addressed to exclusive sender for this address)
Date: Fri, 16 Jul 2004 14:52:14 -0400	[thread overview]
Message-ID: <20040716185214.GA17586@salty> (raw)
In-Reply-To: <40F7BB44.24155.3BC614@localhost> (from +nfcan+jimlaur+c5c49c4dd0.vwren_netfilter#timension.com@spamgourmet.com on Fri, Jul 16, 2004 at 15:25:56 -0400)

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


      parent reply	other threads:[~2004-07-16 18:52 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
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 ` Jim Laurino [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20040716185214.GA17586@salty \
    --to=nfcan.x.jimlaur@dfgh.net \
    --cc=netfilter@lists.netfilter.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
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.