Gary Winiger wrote: > John, > >>> Hmm... good point. I hope SunMC isn't using this information (kstat >> >> The point is that syslog is an event notifier, while >> kstat is a polling mechanism. We certainly don't want >> a bunch of daemons in forever loops cycling thru long >> lists of kstats when watching syslog is sufficient... > > I disagree with the implication that there's anything > that can be relied on as syslog messages. They are all > Non-An-Interface. If humans wish to consume syslog > messages, that's up to the human.
We can argue this indefinitely but regardless of what some PSARC members think admins, developers on Solaris and other platforms act differently. While some may claim that syslog messages are not intended to be interfaces the fact of the matter is that they are because sometimes thats the only interface that gives that critical information in a timely manner. I'd go further and assert that some messages logged by certain parts of Solaris are so well known that they are effectively Committed interfaces. The messages that this case talks about are ones I'd put in this set. Unless this case intends to provide all of the same information for the drivers that will be changed then I believe this is an unacceptable regression regardless of what better tools are out there. As I read it the intent of this case is to centralise the logging not to deprecated it or reduce it, so it should provide identical information and as close as possible the exact same format of message. -- Darren J Moffat
