mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Randy.Dunlap" <rddunlap@osdl.org>
To: Martin Schlemmer <azarah@gentoo.org>
Cc: covici@ccs.covici.com, linux-kernel@vger.kernel.org
Subject: Re: dmesg problem in 2.5.73
Date: Tue, 16 Dec 2003 12:05:47 -0800	[thread overview]
Message-ID: <20031216120547.0d3b77e2.rddunlap@osdl.org> (raw)
In-Reply-To: <1057228803.5499.243.camel@workshop.saharacpt.lan>

On 03 Jul 2003 12:40:04 +0200 Martin Schlemmer <azarah@gentoo.org> wrote:

| On Thu, 2003-07-03 at 10:52, John Covici wrote:
| > Hi.  I have a weird problem -- maybe its iptables, but I am using the
| > log target and they print at legvel 4, but I only want level 3 or
| > less to print on the console, so I did 'dmesg -n 3' but I am still
| > getting the iptables messages.
| > 
| > I thought I could do this all with syslog.conf, but that has never
| > worked.
| > 
| 
| Changing DEFAULT_CONSOLE_LOGLEVEL (?) has been broken since
| 2.5.70 or 2.5.71.  I checked kernel/printk.c, etc, but could
| not see anything that was causing this.

Hi,

Is this still broken?  How do you test it?

In 2.6.0-testN I can change [current] console_loglevel via:

echo 7 > /proc/sysrq-trigger
or
Alt-SysRq-8
or
echo "9 4 1 7" > /proc/sys/kernel/printk

The latter form can also change any of
  (current console_loglevel, default_message_loglevel,
   minimum_console_loglevel, default_console_loglevel}
and is the only way that I know of to change the latter 3 of these.


--
~Randy
MOTD:  Always include version info.

  reply	other threads:[~2003-12-16 20:06 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-03  8:52 John Covici
2003-07-03 10:40 ` Martin Schlemmer
2003-12-16 20:05   ` Randy.Dunlap [this message]
2003-12-16 22:57     ` Martin Schlemmer

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=20031216120547.0d3b77e2.rddunlap@osdl.org \
    --to=rddunlap@osdl.org \
    --cc=azarah@gentoo.org \
    --cc=covici@ccs.covici.com \
    --cc=linux-kernel@vger.kernel.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

all inboxes | Powered by JetHome®