From: Alan Tam <Tam@SiuLung.com>
To: Stephen Hemminger <shemminger@osdl.org>
Cc: bridge@lists.osdl.org
Subject: Re: [Bridge] How to disable verbose kernel logs for linux ethernet bridge?
Date: Tue, 10 May 2005 08:55:42 +0800 [thread overview]
Message-ID: <4280068E.2070102@SiuLung.com> (raw)
In-Reply-To: <20050509105253.293e60b9@dxpl.pdx.osdl.net>
Stephen Hemminger wrote:
>On Sun, 08 May 2005 11:44:32 +0800
>Alan Tam <Tam@SiuLung.com> wrote:
>
>
>>This is part of my dmesg output which is generated whenever some network
>>topology changes. It is very annoying. Any ways for me to inhibit those
>>which are only informational but not warnings which I need to take care?
>>I am running the all bridges on tap* interfaces emulated by OpenVPN. I
>>am running stock 2.6.8 kernel from Debian sarge.
>>
>>
>The easiest way would be to change all those printk's you don't want to see
>in the br_stp_if.c from:
> printk(KERN_INFO "%s: port ...
>to
> printk(KERN_DEBUG "%s: port ...
>
>then they will show up only in /var/log/messages.
>
>
Yes, but recompiling the kernel is not a good thing to me. I think "echo
5 > /proc/sys/kernel/printk" is acceptable. The reason it isn't the
default is probably that most part of the kernel won't be so verbose.
--
Regards,
Alan
prev parent reply other threads:[~2005-05-10 0:55 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-08 3:44 [Bridge] How to disable verbose kernel logs for linux ethernet bridge? Alan Tam
2005-05-09 16:59 ` [Bridge] Port link status disconnect Jorge Lanza
2005-05-09 17:50 ` Stephen Hemminger
[not found] ` <6.1.2.0.2 .20050510115447.043b4c90@luna.tlmat.unican.es>
2005-05-10 9:59 ` Jorge Lanza
2005-05-10 21:52 ` Stephen Hemminger
2005-05-11 7:36 ` Jorge Lanza
2005-05-11 16:20 ` Stephen Hemminger
2005-05-14 8:01 ` Jorge Lanza
2005-05-09 17:52 ` [Bridge] How to disable verbose kernel logs for linux ethernet bridge? Stephen Hemminger
2005-05-10 0:55 ` Alan Tam [this message]
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=4280068E.2070102@SiuLung.com \
--to=tam@siulung.com \
--cc=bridge@lists.osdl.org \
--cc=shemminger@osdl.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.