Stephen Hahn wrote:
> * Garrett D'Amore <[EMAIL PROTECTED]> [2007-03-06 14:03]:
>
>> This makes no sense to me. Its easy to iterate over all the stats and
>> dump them. The only time you have to change the code is when adding new
>> kstat types. (E.g. KSTAT_TYPE_INTR, etc.) This has only happened twice
>> since Solaris 2.5 that I'm aware of ... once to add 64-bit values, and
>> once again to provide a cleaner way to represent strings in kstats.
>>
>
> You are neglecting the interpretation of kstats of type
> KSTAT_TYPE_RAW, each of which can be filled with the contents of an
> arbitrary structure and need not be present on all platforms.
>
> Each kstat dumper (that can display all kstats) must have a catalog of
> the structure definitions that are published as raw kstats.
>
> - Stephen
>
>
To my knowledge, netstat -k never supported RAW kstats.
How does kstat(1) deal with RAW kstats? Can it? I've not looked at the
source for the Kstat perl module, but to my mind, if kstat(1) is going
to deal with raw kstats, then the perl module must have those structure
definitions, and we're just talking about semantics (since the knowledge
of them has to live _somewhere_, be it in a utility, a shared library,
or a perl module...)
>From looking at the output from kstat(1), I don't think it deals with
raw kstats either. At least I don't see any obvious ones in the output.
-- Garrett
_______________________________________________
opensolaris-code mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/opensolaris-code
