CentOS - Oct 2008 - What keeps logging to my console?

Hi folks,

I have lots of messages like these appearing on my local CentOS 5.2 
consoles:
> Oct 17 12:03:29 machine kernel: printk: 1 messages suppressed.
> Oct 17 12:03:29 machine kernel: pbond0: received packet with  own address 
as source address

I have disabled console logging in syslog.conf, and even if I shut down 
syslog and kernel logger, the messages keep coming on the local consoles 
(not on remote consoles).

So the question is: What process logs directly to the console bypassing 
syslog/kernel log facilities? How can I find where to stop that?

Thanks for any hint or help.


Dirk

On Fri, 2008-10-17 at 12:13 +0200, Dirk H. Schulz wrote:
> Hi folks,
> I have lots of messages like these appearing on my local CentOS 5.2 
> consoles:
> > Oct 17 12:03:29 machine kernel: printk: 1 messages suppressed.
> > Oct 17 12:03:29 machine kernel: pbond0: received packet with  own
address
> as source address
> I have disabled console logging in syslog.conf, and even if I shut down 
> syslog and kernel logger, the messages keep coming on the local consoles 
> (not on remote consoles).
	This has nothing to do with syslog.  These are kernel printk messages.
They also go to syslog for logging in files but they go straight to the
kernel console as defined at bootup.  Unless you have configured serial
consoles, the "console" for the kernel is the virtual terminals.
> So the question is: What process logs directly to the console bypassing 
> syslog/kernel log facilities? How can I find where to stop that?
	It's the kernel itself.

	In a VC:

	setterm --msg off

man setterm:

       -msg [on|off] (virtual consoles only)
              Enables or disables the sending of kernel printk()
              messages to the console.
> Thanks for any hint or help.
> 
> 
> Dirk
	Mike
-- 
Michael H. Warfield (AI4NB) | (770) 985-6132 |  mhw at WittsEnd.com
   /\/\|=mhw=|\/\/          | (678) 463-0932 |  http://www.wittsend.com/mhw/
   NIC whois: MHW9          | An optimist believes we live in the best of all
 PGP Key: 0xDF1DD471        | possible worlds.  A pessimist is sure of it!

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 307 bytes
Desc: This is a digitally signed message part
URL:
<http://lists.centos.org/pipermail/centos/attachments/20081017/3faa8dd9/attachment-0003.sig>

Hi folks,

--On 17. Oktober 2008 10:45:08 -0400 "Michael H. Warfield" 
<mhw at WittsEnd.com> wrote:
> On Fri, 2008-10-17 at 12:13 +0200, Dirk H. Schulz wrote:
>> Hi folks,
>
>> I have lots of messages like these appearing on my local CentOS 5.2
>> consoles:
>> > Oct 17 12:03:29 machine kernel: printk: 1 messages suppressed.
>> > Oct 17 12:03:29 machine kernel: pbond0: received packet with  own
>> > address
>> as source address
>
>> So the question is: What process logs directly to the console bypassing
>> syslog/kernel log facilities? How can I find where to stop that?
>
> 	It's the kernel itself.
>
> 	In a VC:
>
> 	setterm --msg off
That did the trick, many thanks.

But now I have 1000s of messages like
"printk: 4 messages suppressed" in my /var/log/messages.

Can I get rid of that, too?

Dirk