Difference between revisions of "5.4.1 open issues"
From Net-SNMP Wiki
(Initial list of 5.4.1 open issues) |
m |
||
| Line 48: | Line 48: | ||
|} | |} | ||
| − | == Documentation and testing work for 5.4 final == | + | == Documentation and testing work for 5.4.1 final == |
{| width=100% | {| width=100% | ||
Revision as of 14:39, 9 May 2007
We try to collect significant open issues for the 5.4.1 release cycle here. Please add your contributions/comments and fix as much as you can!
Open issues for 5.4.1
| Issue | Bug/patch | Comment | Assigned to |
| snmptrap/trapsess send to port 161 | Patch 1620424 | snmptrap and trapsess send to port 161 instead of port 162 by default. Patch from magfr available. | ? |
| Python build | - | There's a Debian patch (#38) to allow for in-tree building of the Python modules. | marz? |
| error on subcontainer 'ia_addr' insert (-1) | Bug 1693039, Patch 1712645 | Provide a more meaningful log message for duplicate IP addresses instead of spamming the log continuously. | rstory? |
| OSX embedded perl broken | Bug 1377478 | Embedded perl (and sometimes even the perl modules) seem to fail silently (and for unknown reasons) on OSX for some people, but not all. | ? |
| 64bit nlist | Bugs 148532, 1484814, 1388562 | nlist fails on 64bit systems (AIX, IRIX, Tru64). We need 64bit capable auto_nlist replacement routines. Every system has its own variant and changes are needed all over the net-snmp code. Stop-gap fix is specifying --without-kmem-usage which is now possible since 5.4.rc2. | tanders |
| Solaris perl<->host issues (due to largefiles) | Bug 1486366 | Solaris system-supplied Perl is compiled with largefile support. The very same options break the build of the host module, though. (Wes: This will not be fixed by 5.4.) At least detected (and embedded perl disabled) in pre3. |
? |
| ifTable transient interface handling | Bug 1238981, Patch 1513191 | offer an (per-interface) config option how transient interfaces are handled in ifTable (same or different). A List FAQ. This feels like a new feature, and not appropriate for 5.4.x? |
rstory? |
| disman/event crash | Bug 1556259 | Reported crashes in mteTrigger.c This is a race condition between (typically high-volume) request handling and trap generation. Not realistic to address for 5.4.1? |
dts12 |
| Suppress error messages on SIGHUP | ? | Remove the likely harmless, but annoying error messages on SIGHUP. A List FAQ Handled for "extend" and "monitor" directives. What others? |
rstory?/dts12 |
| library layering | Bug 1565496 (OSX), Patches 1398873 1493522 | Consensus seems to be to extend --enable-as-needed for 5.4.1 rather than 5.4 and come up with a proper configure test for 5.5. --Thomas. Full analysis / Work in progress | hardaker/tanders |
| Linux CPU stats | Bug 1600261 | Broken for Montavista Linux on XScale/ARM and possibly others. See bug description. Regression over 5.3.x. Appears to be very hardware-specific. Fixed in 5.4.x SVN (r15839). |
dts12 |
| fix perl compiler warnings | - | There are a number of nasty compiler warnings for the perl modules that needs to be dealt with. List provided to hardaker. (http://pastebin.ca/196857) Dave has flagged three issues as potentially important after review (see list). Full fixes for SNMP.pm are in 5.4.x CVS. | tanders |
| OSX CPU stats | Patch 1600522 | Neither cpu_sysctl (preferrable?) nor cpu_nlist compile on Darwin. rc1/rc2 ship cpu_null for Darwin. To be investigated! At least it doesn't seem to be a regression over 5.3.x, based on rstory's snmpwalk output for darwin7/8. <P/>A new cpu_mach.c has been supplied as a patch after rc3! Too late for 5.4. Now in 5.4.x CVS. |
dts12/rstory/jalbert |
Documentation and testing work for 5.4.1 final
| Item | Comment | Assigned to |
| manual pages | quite a few manual pages currently ship with explicit XXX - to be filled in for 5.4 final. | ? |
| missing tests | We're currently missing tests for at least: disman/event monitoring, snmpvacm extensions, snmptranslate, snmpusm DH stuff, snmptrapd walk, ... | ? |
