Those of you who follow activity on the CVS main branch may have
noticed that I've been working on a re-implementation of the old
UCD-SNMP-MIB::extTable - taking the same basic idea but making it
somewhat more flexible.
Up to now, this has been a completely new MIB (NET-SNMP-EXTEND-MIB),
but I've just committed some changes to provide an implementation
of the extTable as well (if the original code wasn't configured in).
This effectively makes the original module redundent (modulo bugs
in my code, naturally!)
The reason I'm mentioning it here, is to float the idea of dropping
the 'ucd-snmp/extensible' module completely - as from v5.2
The advantage of doing so is that it avoids the need to have two
parallel configure directives ("exec" and "exec2", etc). The agent
would simply continue to provide the same 'UCD-SNMP-MIB::extTable'
but this would be duplicated by the (fuller) NET-SNMP-EXTEND-MIB
information.
The disadvantage of doing this is that the output of the "relocatable"
form of the exec directive (i.e. "exec .1.2.3.4.5 ....") would change
(to match the full NET-SNMP-EXTEND-MIB structure, rather than the
current variant form of the UCD-SNMP-MIB::extTable)
Normally, I wouldn't even contemplate suggesting this before v6,
but the current output does not actually form a legal MIB structure,
so I'm much less worried about {breaking|fixing} this at a
minor-release point.
But what do other people think?
Dave
-------------------------------------------------------
This SF.Net email is sponsored by: GNOME Foundation
Hackers Unite! GUADEC: The world's #1 Open Source Desktop Event.
GNOME Users and Developers European Conference, 28-30th June in Norway
http://2004/guadec.org
_______________________________________________
Net-snmp-coders mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/net-snmp-coders
