On Mon, 2006-02-13 at 22:57 +0100, [EMAIL PROTECTED] wrote:
> > As we become more confident about the behaviour of these optional
> > modules, we can consider including them within the default build
> > configuration. We're moving towards including more and more by
> > default, but this has to be balanced against the risks involved,
> > particularly with relatively untested code.
>
> Ok i can understand that, but what apart new lines of developpment like
> disman, i don't see what could be unstable now in a linux host agent
Well, the 5.3 release has seen:
- a complete reworking of the DisMan code (for all architectures)
- a complete reworking of the ifTable code (for Linux, initially)
- the start of a complete reworking of hardware reporting
(which will eventually affect both the Host Resources
and much of the UCD-SNMP-MIB - currently Linux only)
- a major reworking of the access control internals
- a major reworking of the code for generating traps
The Net-SNMP project is most definitely not static. And whenever we
change things (hopefully to make them better, more functional and/or
more portable), then there's the danger of introducing instability.
Dave
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642
_______________________________________________
Net-snmp-users mailing list
[email protected]
Please see the following page to unsubscribe or change other options:
https://lists.sourceforge.net/lists/listinfo/net-snmp-users
