Re: dmesg problem in 2.5.73

[Randy.Dunlap]

On 03 Jul 2003 12:40:04 +0200 Martin Schlemmer <azarah@xxxxxxxxxx> 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.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/