Blog

An unknown variable error that would occur when adding a MIB if either a file with the same name was already added or if copying/linking the file into the mibs directory failed, rather than the intended dialog, and was corrected in this release.

Changes in this release:

• nmtrapd under Linux could max out CPU usage due to Linux-specific handling of select() timeouts.
• Newlines and carriage returns in OCTET STRING values were forcing conversion to hex (such as in varbind values in responses) as if they were non-printable characters.
• A crash could occur if the environment variable for pointing to the license key file were mistakenly set to a directory instead.

Changes affecting MIB Smithy:

• A “wrong # args” error could occur when previewing a single OBJECT-TYPE in SMI format (the error did not occur when previewing the whole module).

Changes affecting both MIB Smithy and MIB Smithy SDK:

• The “piberrors” type in the XML-SMI Schema document was not correct and did not match the implementation and has been corrected.
• Newlines and carriage returns in OCTET STRING values were forcing conversion to hex (such as in varbind values in responses) as if they were on-printable characters.
• A crash could occur if the environment variable for pointing to the license key file were mistakenly set to a directory instead.

There was another issue with the table SEQUENCE definition relocation change merged into 4.0.4 and not fixed in 4.0.5 that caused them to be generated twice rather than once. This could cause a module that was saved to fail to load back into MIB Smithy later.

Also, when such failure occurred due to the duplicate definition, double-clicking on the error in the compiler log should have opened the text file editor for manual correction, but instead caused an “invalid workspace type” error.

Both of these issues have been corrected in the 4.0.6 release.

I’ve made some changes to the feed structure for the blog to be more flexible and a little more standard.

While I expect all posts will be categorized under either “News” or “Articles” (with additional categories as appropriate), you’ll notice that the categories listed for posts now have feed icons next to them, which you can use to subscribe to more specific categories. The “News+Articles” feed is still the feed for the full blog.

If you’re already subscribed to a feed, you may wish to resubscribe as paths have been changed (e.g. the “News” feed is now “/blog/category/news/feed/” instead of “/news_feed.php”). Redirects are in place so your subscription should continue to operate as before even if you don’t, but resubscribing will reduce the number of requests your client needs to send.

My apologies if this causes any trouble. The dust is still settling a bit on the new systems.