"Randy Presuhn" <[email protected]> writes:
> Keeping the amount of paperwork to a minimum, how about doing
> something that, while perfectly legal as far as I can tell,
> might *really* irk badly written code:
>
> hrExtStorageEntry OBJECT-TYPE
> SYNTAX HrExtStorageEntry
> MAX-ACCESS not-accessible
> STATUS current
> DESCRIPTION
> "A (conceptual) entry for one logical storage area on
> the host, containing extensions to the information
> contained in the corresponding hrStorageEntry."
> AUGMENTS { hrStorageEntry }
> ::= { hrStorageTable 2 }
>
> -- yes, that's a TWO!
Heh. I'd be more tempted to simply define the new column in a new MIB
module and import the existing entry spec and just place the new column
into the table from afar.
IE, just do this:
> hrExtStorageAvail OBJECT-TYPE
> SYNTAX Integer32 (0..2147483647)
> MAX-ACCESS read-only
> STATUS current
> DESCRIPTION
> "The amount of the storage represented
> by this entry that is available to
> non-superusers, in units of
> hrStorageAllocationUnits."
> ::= { hrExtStorageEntry 8 }
(which is actually a copy of what you put because you forgot to add the
2 to your OID clause in the first place)
--
Wes Hardaker
My Pictures: http://capturedonearth.com/
My Thoughts: http://pontifications.hardakers.net/
_______________________________________________
OPSAWG mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/opsawg
