Darren J Moffat writes: > We can argue this indefinitely but regardless of what some PSARC members > think admins, developers on Solaris and other platforms act differently.
Regardless of how they act, we don't apply any engineering towards making their actions supportable. Like debug printfs, nobody ever demands that changes in syslog messages be run past ARC. That's just life. They change all the time, including in patches. Unless we start doing the engineering necessary to make what those users are doing actually supportable in some way, it really doesn't matter what they're doing. The message contents are not documented, and what they're doing is clearly in the realm of hackery. > 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. Sorry, no. I see no plausible way that we could get there, and I don't think making such an assertion should be part of this case. I completely agree that we've got huge holes in the system here, but nailing syslog messages to the wall isn't a reasonable way to fill them. -- James Carlson, Solaris Networking <james.d.carlson at sun.com> 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
