dmesg problem in 2.5.73

dmesg problem in 2.5.73

[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.

Any assistance would be appreciated.

-- 
         John Covici
         covici@ccs.covici.com

Re: dmesg problem in 2.5.73

[Martin Schlemmer]

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.


Regards,

-- 
Martin Schlemmer

Re: dmesg problem in 2.5.73

[Randy.Dunlap]

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.

Re: dmesg problem in 2.5.73

[Martin Schlemmer]

[-- Attachment #1: Type: text/plain, Size: 910 bytes --]

On Tue, 2003-12-16 at 22:05, Randy.Dunlap wrote:
> 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?
> 

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


Thanks,

-- 
Martin Schlemmer

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]