All of lore.kernel.org
 help / color / mirror / Atom feed
From: "involved" <involved@netcabo.pt>
To: netfilter@lists.netfilter.org
Subject: RE: help needed: clogged console
Date: Fri, 2 Jan 2004 12:56:48 -0000	[thread overview]
Message-ID: <!~!UENERkVCMDkAAQACAAAAAAAAAAAAAAAAABgAAAAAAAAAxa3KUG+UK0em3rAEUPYkD8KAAAAQAAAAz4YdOTCj00+AsRsqWsG/wQEAAAAA@netcabo.pt> (raw)
In-Reply-To: <00ea01c3c982$fe3196a0$4900a8c0@cympak.com>

Hi,

I also had that problem.. I use "dmesg -n 1" to avoid getting those kernel
messages on active consoles

Bye
i.

-----Original Message-----
From: netfilter-admin@lists.netfilter.org
[mailto:netfilter-admin@lists.netfilter.org] On Behalf Of Slawomir Orlowski
Sent: terça-feira, 23 de Dezembro de 2003 18:32
To: shrike-list@redhat.com; redhat-list@redhat.com
Cc: netfilter@lists.netfilter.org
Subject: help needed: clogged console

Hello,

I have Linux RH 9.0 configured as filtering firewall, and getting a lot of
(kernel, iptables) messages on active consoles.
I have thought that putting in /etc/syslog.conf:

# *.kern /dev/console
kern.* /var/log/kernel
kern.* /dev/tty8

would free me from this, but it did not.
How can I force kernel message to appear only in /var/log/kernel log and on
tty8 only?

Best Regards
I hope that somebody will be able to help me.
When  I'm getting a lot of dropped packages it is not possible even to log.

Slawomir Orlowski




  reply	other threads:[~2004-01-02 12:56 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-12-23 18:31 help needed: clogged console Slawomir Orlowski
2004-01-02 12:56 ` involved [this message]
2004-01-02 15:15 bmcdowell
2004-01-02 16:00 ` John A. Sullivan III
2004-01-05 12:31   ` Jozsef Kadlecsik
2004-01-06  1:42     ` John A. Sullivan III
2004-01-06  9:13       ` Jozsef Kadlecsik

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=''\!'~'\!'UENERkVCMDkAAQACAAAAAAAAAAAAAAAAABgAAAAAAAAAxa3KUG+UK0em3rAEUPYkD8KAAAAQAAAAz4YdOTCj00+AsRsqWsG/wQEAAAAA@netcabo.pt' \
    --to=involved@netcabo.pt \
    --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.