rpc.kstatd: Remote Kstat Access Service [PSARC/2008/502 FastTrack timeout 08/13/2008]

[James Carlson]

Garrett D'Amore writes:
> If the project team only wants a few kstats, and can arrange for 
> stability promises, then we should document that with an upleveling of 
> the commitment of those particular kstats.  (Are there any kstats that 
> have stability guarantees higher than Project Private?)

Yes, but they're the rare exception.  See PSARC 1997/198 ("MIB-II
kstats") for an example.

In general, kstats are added for things that a developer thinks are
"interesting," and thus are strongly tied to the implementation.
Nailing them down means (a) making the current implementation harder
to change [fewer possible release vehicles] and (b) requiring ARC
review for the things that change.

-- 
James Carlson, Solaris Networking              <james.d.carlson at sun.com>
Sun Microsystems / 35 Network Drive        71.232W   Vox +1 781 442 2084
MS UBUR02-212 / Burlington MA 01803-2757   42.496N   Fax +1 781 442 1677