Stopping "Link down - cable problem?" Messages

I'm pretty sure this should be a FAQ, but heck if I can Google it
today. I want to shut up the,

Apr 21 13:14:30 qfe: [ID 775809 kern.notice] NOTICE: SUNW,qfe4: No response from Ethernet network : Link Down - cable problem?

Messages, but I don't want to bring down the interfaces. It's a lab
setup and I'm moving cables around constantly, bringing systems and
network equipment up and down, etc. I just want the interfaces up and
ready all of the time, but the messages are sooooo annoying on the
console. Is there an easy way to do this? Something in /etc/system,
or an ndd(1M) setting, or qfe.conf? Or will I need to filter in syslogd(1M)
(yuck)?

Which brings me to a related syslogd(1M) question. Why are these annoying
messages only going to the console and not /var/adm/messages? The two
lines of interest in /etc/syslog.conf are,

*.err;kern.notice;auth.notice /dev/sysmsg
*.err;kern.debug;daemon.notice;mail.crit /var/adm/messages

If I run syslogd(1M) in debug mode, I see the output (heavily edited for
space) attached below. So why are the messages, that syslogd(1M) indicates
are kern.notice going to the console, /dev/sysmsg, and not /var/adm/messages
too? The priority for /dev/adm/messages is all the way down at "debug" so
all "kern" messages should be logged.

Just wondering why this is the way it is at the moment. Right now it is
a nice feature to not have those cluttering my logs.

main(1): Started at time Fri Apr 21 13:14:06 2006
hnc_init(1): hostname cache configured 128 entry ttl:600
getnets(1): found 1 addresses, they are: 0.0.0.0.2.2
amiloghost(1): testing 127.0.0.1.2.2
conf_init(1): I am loghost
cfline(1): (*.err;kern.notice;auth.notice /dev/sysmsg)
cfline(1): (*.err;kern.debug;daemon.notice;mail.crit /var/adm/messages)

syslogd: version 1.99
Started: Fri Apr 21 13:14:06 2006
Input message count: system 0, network 0
# Outputs: 6

------------------------ priority = [file, facility] ------------------------

0 0 0 0 0 0 0 0 0 0 1 1 1 1 1 1 1 1 1 1 2 2 2 2 2
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4
--------------------------------------------------
5 3 3 3 5 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 X CONSOLE: /dev/sysmsg
7 3 2 5 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 X FILE: /var/adm/messages

Facilities:
[00] kern: 0
[01] user: 8
[02] mail: 16
[03] daemon: 24
[04] auth: 32
[05] security: 32
[06] mark: 192
[07] syslog: 40
[08] lpr: 48
[09] news: 56
[10] uucp: 64
[11] cron: 120
[12] local0: 128
[13] local1: 136
[14] local2: 144
[15] local3: 152
[16] local4: 160
[17] local5: 168
[18] local6: 176
[19] local7: 184

Priorities:
[00] panic: 0
[01] emerg: 0
[02] alert: 1
[03] crit: 2
[04] err: 3
[05] error: 3
[06] warn: 4
[07] warning: 4
[08] notice: 5
[09] info: 6
[10] debug: 7
[11] none: 16

writemsg(2): Logging msg 'Apr 21 13:14:08 qfe: [ID 775809 kern.notice] NOTICE: SUNW,qfe1: No response from Ethernet network : Link Down - cable problem?' to CONSOLE /dev/sysmsg
writemsg(2): Logging msg 'Apr 21 13:14:08 qfe: [ID 775809 kern.notice] NOTICE: SUNW,qfe2: No response from Ethernet network : Link Down - cable problem?' to CONSOLE /dev/sysmsg
writemsg(2): Logging msg 'Apr 21 13:14:08 qfe: [ID 775809 kern.notice] NOTICE: SUNW,qfe4: No response from Ethernet network : Link Down - cable problem?' to CONSOLE /dev/sysmsg
writemsg(2): Logging msg 'Apr 21 13:14:08 qfe: [ID 775809 kern.notice] NOTICE: SUNW,qfe5: No response from Ethernet network : Link Down - cable problem?' to CONSOLE /dev/sysmsg
writemsg(2): Logging msg 'Apr 21 13:14:08 qfe: [ID 775809 kern.notice] NOTICE: SUNW,qfe6: No response from Ethernet network : Link Down - cable problem?' to CONSOLE /dev/sysmsg
writemsg(2): Logging msg 'Apr 21 13:14:08 qfe: [ID 775809 kern.notice] NOTICE: SUNW,qfe7: No response from Ethernet network : Link Down - cable problem?' to CONSOLE /dev/sysmsg

--
Crist J. Clark crist.clark@xxxxxxxxxxxxxx
Globalstar Communications (408) 933-4387
_______________________________________________
sunmanagers mailing list
sunmanagers@xxxxxxxxxxxxxxx
http://www.sunmanagers.org/mailman/listinfo/sunmanagers

Relevant Pages

  • Re: serial console oddity
    ... >> see syslogd output to the console get corrupted. ... >> syslogd writes seems to get truncated or otherwise corrupted. ... > This is a longstanding bug in ttymsg(). ... > last close of the console affects the underlying tty. ...
    (freebsd-current)
  • serial console oddity
    ... output to the console and userland writes to /dev/console. ... syslogd writes seems to get truncated or otherwise corrupted. ... the first character of the month, or sometimes just a space, or ... When the syslogd output is being corrupted, I can cat a file to ...
    (freebsd-current)
  • RE: how do I suppress system messages?
    ... System messages print out to the console on tty0 only, ... syslogd, via /etc/rc.conf. ...
    (freebsd-newbies)
  • Re: how do I suppress system messages?
    ... > System messages print out to the console on tty0 only, ... Simply put a # in front, save the file, and restart syslogd by doing ...
    (freebsd-questions)
  • Re: syslogd logs to console, syslog.conf has no /dev/console entries
    ... This behavior stops ... each time I make a change I restart syslogd and send it ... HUP using kill but each time the console still gets warning messages ... Weird - the first thing that comes to mind would be that Postfix ...
    (comp.unix.bsd.freebsd.misc)