From: "Victor Wren" <vwren@timension.com>
To: netfilter <netfilter@lists.netfilter.org>
Subject: Re: OT: Logs on console
Date: Fri, 16 Jul 2004 12:28:25 -0800 [thread overview]
Message-ID: <40F7C9E9.30435.74F90D@localhost> (raw)
In-Reply-To: <200407161942.32228.Antony@Soft-Solutions.co.uk>
> 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.
next prev parent reply other threads:[~2004-07-16 20:28 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 [this message]
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
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=40F7C9E9.30435.74F90D@localhost \
--to=vwren@timension.com \
--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.