On Fri, Apr 30, 2010 at 9:22 PM, Bart Van Assche
<bart.vanass...@gmail.com>wrote:

> On Sat, Apr 10, 2010 at 12:50 AM, Dave Shield 
> <d.t.shi...@liverpool.ac.uk>wrote:
>
>> New release candidate versions of the 5.4.x and 5.2.x packages
>> are now available  from the SourceForge download servers.
>> The main changes since the rc1 versions are:
>>
>>  - Proper handling of multiple matching VACM entries
>>      (using the "best match" rather than the first one seen)
>>     This could potentially affect the behaviour of existing
>>       access control configurations.
>>
>>  - Usage statistics for large disks are latched at 2Tb (2^31)
>>       rather than wrapping
>>
>>  - The default AgentX target for Windows systems will
>>       listen on the localhost interface only rather than on
>>       all network interfaces.   (5.4.3 only)
>>    This does not affect the default on Unix-based systems,
>>       which still use a named socket.
>>
>> The 5.2.6 release is envisaged as being the final version on the
>> 5.2.x line. No further development is planned for this branch.
>>
>> It is hoped that these candidates can be released as the full versions
>> as soon as possible, assuming no major issues come to light.  Please
>> test them out and report any problems that you might encounter.
>>
>> Download URLs:
>>
>> http://sourceforge.net/projects/net-snmp/files/net-snmp/5.2.6_pre-releases/
>>
>> http://sourceforge.net/projects/net-snmp/files/net-snmp/5.4.3_pre-releases/
>>
>
> The 5.4.3 pre-release didn't build on MinGW. This has been fixed in r18631.


Note: the 5.4 configure script fails to detect that recent MinGW versions
supports IPv6. This issue has been fixed on the 5.5 branch and on the trunk.

Bart.
------------------------------------------------------------------------------
_______________________________________________
Net-snmp-users mailing list
Net-snmp-users@lists.sourceforge.net
Please see the following page to unsubscribe or change other options:
https://lists.sourceforge.net/lists/listinfo/net-snmp-users

Reply via email to