From: Jozsef Kadlecsik <kadlec@blackhole.kfki.hu>
To: "John A. Sullivan III" <john.sullivan@nexusmgmt.com>
Cc: bmcdowell@coxhealthplans.com, orlowscy@hotpop.com,
shrike-list@redhat.com, redhat-list@redhat.com,
netfilter@lists.netfilter.org
Subject: RE: help needed: clogged console
Date: Mon, 5 Jan 2004 13:31:55 +0100 (CET) [thread overview]
Message-ID: <Pine.LNX.4.33.0401051315050.15139-100000@blackhole.kfki.hu> (raw)
In-Reply-To: <1073059221.2993.10.camel@jasiiitosh.nexusmgmt.com>
On Fri, 2 Jan 2004, John A. Sullivan III wrote:
> > Search for 'dmesg -n 1' - I think that's what you're after.
^^^^^
> I've been really confused by this issue. I am also running iptables on
> RedHat 9.0. /etc/syslog.conf shows nothing being logged to the
> console. Yet, ever since applying the netfilter patch-o-matic
> tcp-window patch, all of its messages appear on my console. The
> netfilter mail lists say this is a misconfiguration of syslog but it
> sure looks correctly configured to me. No other iptables messages go to
> the console - just the tcp-window messages. How do I stop them!!! Thanks
Default the tcp-window-tracking patch uses extensive kernel logging,
while the other parts of netfilter keeps mouth shut. You can easily
disable the logging by
echo 0 > /proc/sys/net/ipv4/netfilter/ip_conntrack_tcp_log_invalid
Back to the console logging: klogd uses the console to display the kernel
log messages. You can alter it's default behaviour by issuing dmesg like
above or setting the proper command line switches for klogd. If you want
to send the kernel logs to other places (file/remote machine etc.), *then*
you have to configure syslogd properly.
Best regards,
Jozsef
-
E-mail : kadlec@blackhole.kfki.hu, kadlec@sunserv.kfki.hu
PGP key : http://www.kfki.hu/~kadlec/pgp_public_key.txt
Address : KFKI Research Institute for Particle and Nuclear Physics
H-1525 Budapest 114, POB. 49, Hungary
next prev parent reply other threads:[~2004-01-05 12:31 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-02 15:15 help needed: clogged console bmcdowell
2004-01-02 16:00 ` John A. Sullivan III
2004-01-05 12:31 ` Jozsef Kadlecsik [this message]
2004-01-06 1:42 ` John A. Sullivan III
2004-01-06 9:13 ` Jozsef Kadlecsik
-- strict thread matches above, loose matches on Subject: below --
2003-12-23 18:31 Slawomir Orlowski
2004-01-02 12:56 ` involved
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=Pine.LNX.4.33.0401051315050.15139-100000@blackhole.kfki.hu \
--to=kadlec@blackhole.kfki.hu \
--cc=bmcdowell@coxhealthplans.com \
--cc=john.sullivan@nexusmgmt.com \
--cc=netfilter@lists.netfilter.org \
--cc=orlowscy@hotpop.com \
--cc=redhat-list@redhat.com \
--cc=shrike-list@redhat.com \
/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.