Bug#78317: marked as done (paket-filter, isdn and dynip messages on the console)
Your message dated Wed, 29 Nov 2000 18:39:24 +0100
with message-id <20001129183924.A12068@cistron.nl>
and subject line Bug#78317: paket-filter, isdn and dynip messages on the console
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere. Please contact me immediately.)
Darren Benham
(administrator, Debian Bugs database)
--------------------------------------
Received: (at submit) by bugs.debian.org; 29 Nov 2000 14:15:12 +0000
>From Nikolaus@rath.org Wed Nov 29 08:15:12 2000
Return-path: <Nikolaus@rath.org>
Received: from news.uni-x.net [195.60.111.51]
by master.debian.org with esmtp (Exim 3.12 1 (Debian))
id 14180t-00089d-00; Wed, 29 Nov 2000 08:15:11 -0600
Received: from uucp (helo=nikratio.lc.rath.org)
by news.uni-x.net with local-bsmtp (Exim 3.16 #1)
id 14180v-0002Rn-00; Wed, 29 Nov 2000 15:15:13 +0100
Received: from nikratio by nikratio.lc.rath.org with local (Exim 3.16 (Debian))
id 1417v9-0006Ak-00; Wed, 29 Nov 2000 15:09:15 +0100
From: Nikolaus Rath <Nikolaus@rath.org>
To: Debian Bug Tracking System <submit@bugs.debian.org>
Subject: paket-filter, isdn and dynip messages on the console
X-Reportbug-Version: 1.4
X-Mailer: reportbug 1.4
Date: Wed, 29 Nov 2000 15:09:15 +0100
Message-Id: <[🔎] E1417v9-0006Ak-00@nikratio.lc.rath.org>
Delivered-To: submit@bugs.debian.org
Package: general
Version: N/A; reported 2000-11-29
Severity: important
Hello!
I know, this is probably my fault, but in the Usenet nobody could tell
me, where it is situated. I receive some Kernelmessages always on the
active tty. The syslog configuration is correct. I've also tried
different syslogd's.
The Kernel messages are from the paketfilter (denied pakets), the isdn
subsystem (connection, disconnection, triggering paket) and the dynip
Patch ("shifting sk_addr from .. to ..").
Who can help?
-- System Information
Debian Release: woody
Architecture: i386
Kernel: Linux nikratio 2.2.17 #1 Mon Nov 27 23:54:01 CET 2000 i686
---------------------------------------
Received: (at 78317-done) by bugs.debian.org; 29 Nov 2000 18:37:16 +0000
>From wichert@cistron.nl Wed Nov 29 12:37:16 2000
Return-path: <wichert@cistron.nl>
Received: from cabal.wiggy.net (fog.mors.wiggy.net) [195.64.66.141]
by master.debian.org with esmtp (Exim 3.12 1 (Debian))
id 141C6U-0005FG-00; Wed, 29 Nov 2000 12:37:15 -0600
Received: (from wichert@localhost)
by fog.mors.wiggy.net (8.11.1/8.11.1/Debian 8.11.0-6) id eATHdOZ12078;
Wed, 29 Nov 2000 18:39:24 +0100
Date: Wed, 29 Nov 2000 18:39:24 +0100
From: Wichert Akkerman <wichert@cistron.nl>
To: Nikolaus Rath <Nikolaus@rath.org>, 78317-done@bugs.debian.org
Subject: Re: Bug#78317: paket-filter, isdn and dynip messages on the console
Message-ID: <20001129183924.A12068@cistron.nl>
References: <[🔎] E1417v9-0006Ak-00@nikratio.lc.rath.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.5i
In-Reply-To: <[🔎] E1417v9-0006Ak-00@nikratio.lc.rath.org>; from Nikolaus@rath.org on Wed, Nov 29, 2000 at 03:09:15PM +0100
Delivered-To: 78317-done@bugs.debian.org
Previously Nikolaus Rath wrote:
> I know, this is probably my fault, but in the Usenet nobody could tell
> me, where it is situated.
So why file a bugreport? It's not a bug at all. What happens is that
the kernel produces output with printk(KERN_DEBUG "...."). Using
an option to klogd or by insterting values in /proc/sys/kernel/printk
you can configure if those are displayed on the console as well.
>From Documentation/sysctl/kernel.txt:
> printk:
>
> The four values in printk denote: console_loglevel,
> default_message_loglevel, minimum_console_level and
> default_console_loglevel respectively.
>
> These values influence printk() behavior when printing or
> logging error messages. See 'man 2 syslog' for more info on
> the different loglevels.
>
> - console_loglevel: messages with a higher priority than
> this will be printed to the console
> - default_message_level: messages without an explicit priority
> will be printed with this priority
> - minimum_console_loglevel: minimum (highest) value to which
> console_loglevel can be set
> - default_console_loglevel: default value for console_loglevel
A quick look at /usr/include/linux/kernel.h will reveal what the
possible numbers used are:
#define KERN_EMERG "<0>" /* system is unusable */
#define KERN_ALERT "<1>" /* action must be taken immediately */
#define KERN_CRIT "<2>" /* critical conditions */
#define KERN_ERR "<3>" /* error conditions */
#define KERN_WARNING "<4>" /* warning conditions */
#define KERN_NOTICE "<5>" /* normal but significant condition */
#define KERN_INFO "<6>" /* informational */
#define KERN_DEBUG "<7>" /* debug-level messages */
Wichert.
--
_________________________________________________________________
/ Nothing is fool-proof to a sufficiently talented fool \
| wichert@cistron.nl http://www.liacs.nl/~wichert/ |
| 1024D/2FA3BC2D 576E 100B 518D 2F16 36B0 2805 3CB8 9250 2FA3 BC2D |
Reply to: