From: James Pattie <james@pcxperience.com>
To: "Hurley, Michael" <MHurley@law.uconn.edu>
Cc: "Netfilter (E-mail)" <netfilter@lists.netfilter.org>
Subject: Re: logging to console
Date: Tue, 16 Dec 2003 10:29:06 -0600 [thread overview]
Message-ID: <3FDF32D2.3010900@pcxperience.com> (raw)
In-Reply-To: <AD8D39C727CBD411BB2C0090273A727408F9ED49@mortimer.law.uconn.edu>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hurley, Michael wrote:
| Using iptables 1.2.8-8.72.3 on Red Hat Linux 7.3, kernel 2.4.20-20.7.
|
| Haven't found a solution to this so far: iptables LOG is logging to console.
| This only occurs on the consoles directly connected to the machine. Logging
| in remotely does not have this problem.
|
| Here's what I've tried so far, w/o success:
| set log-level to notice, added kern.=notice /var/log/firewall to
| syslog.conf, restarted syslogd.
| set log-level to warning, added kern.=warning /var/log/firewall to
| syslog.conf, restarted syslogd.
|
| Still keeps on logging to local consoles. (BTW, kern.* is not accounted for
| in syslog.conf).
|
| I haven't tried setting the printk values yet (at present, the values are 6
| 4 1 7)--unsure of what the consequences might be of tinkering with that.
|
| What is the best way to stop this irritating behavior? Thanks,
|
|
a temporary solution is to issue: dmesg -n 1
at the console. that stops it outputting on the active console, but it still
goes into dmesg, etc.
- --
James A. Pattie
james@pcxperience.com
Linux -- SysAdmin / Programmer
Xperience, Inc.
http://www.pcxperience.com/
http://www.xperienceinc.com/
GPG Key Available at http://www.pcxperience.com/gpgkeys/james.html
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.7 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQE/3zLRtUXjwPIRLVERAldvAJ9kFqRQDaEyDmRvG92w/2IVt+YpmQCg4UIz
PnS2BJ0oTdfIo01WqELk+Nk=
=zIRK
-----END PGP SIGNATURE-----
--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.
MailScanner thanks transtec Computers for their support.
next prev parent reply other threads:[~2003-12-16 16:29 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-16 15:59 logging to console Hurley, Michael
2003-12-16 16:23 ` Antony Stone
2003-12-16 16:29 ` James Pattie [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-12-16 16:45 Hurley, Michael
2003-12-16 17:10 ` Ben
2003-12-16 17:19 ` Antony Stone
2003-12-16 23:33 ` Laurence J. Lane
2003-12-17 18:14 Hurley, Michael
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=3FDF32D2.3010900@pcxperience.com \
--to=james@pcxperience.com \
--cc=MHurley@law.uconn.edu \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox