Skip to contentSkip to conversation

dmesg problem in 2.5.73

DISCUSSION John Covici 4 participants 4 messages Jul 3, 2003 – Dec 16, 2003

lore
Share & tools
lore
#0 lore raw

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.

Any assistance would be appreciated.

Signature · 2 lines
         John Covici
         [email protected]
#1 lore raw
Quoted 8 lines · John Covici

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.

Regards,

Signature · 1 line
Martin Schlemmer
#2 lore raw

On 03 Jul 2003 12:40:04 +0200 Martin Schlemmer <[email protected]> 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.

#3 lore raw
Quoted 16 lines · Randy.Dunlap

On 03 Jul 2003 12:40:04 +0200 Martin Schlemmer <[email protected]> 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.
Quoted 4 lines

Hi,

Is this still broken? How do you test it?

Nop, was fixed some time back (don't ask when, as I cannot remember).

Thanks,

Signature · 1 line
Martin Schlemmer