I just saw these two integrations:
6542639 No console NOTICE messages about 'nxge' device link up/down
6519690 e1000g should not print the link up/down messages to console
They appear to be at odds with each other -- one adding new messages
where we had none, and the other removing messages.
Would it be possible to come up with a single policy for what drivers
ought to do with these sorts of events? My preference would be:
- External events (from outside the system, such as link status) by
default do not result in any log messages, unless the events
themselves are extraordinary and catastrophic in nature. Ethernet
link up/down isn't in that class. Fire might be.
- Drivers avoid logging to the console itself in all but exceptional
cases. There shouldn't be any need to do this.
- In cases where log messages are necessary and where they're driven
by events outside of administrative control (such as an I/O port
flapping in the breeze), drivers must throttle their logging rate
to avoid choking the system.
- Kstats, sysevents, ereports, and other programmatic interfaces are
strongly encouraged over any text-oriented interface, such as a
log message.
I'd like to see a day when the Ethernet drivers on my systems don't
just spam the logs. Am I alone in that?
--
James Carlson, Solaris Networking <[EMAIL PROTECTED]>
Sun Microsystems / 1 Network Drive 71.232W Vox +1 781 442 2084
MS UBUR02-212 / Burlington MA 01803-2757 42.496N Fax +1 781 442 1677
_______________________________________________
driver-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/driver-discuss
