Dave Halliday

That's the expected behavior. The walk() method uses get_next() not get() to retrieve data. I think this behavior is consistent with other tools.

Thanks. I'll think about adding an option to the walk method. I can see how the inconsistency with the snmpwalk command would be confusing.

You could try something like this (not tested): ``` ruby module SNMP class OctetString def to_date dt = self.unpack("ncccccc") sprintf "%04d-%02d-%02dT%02d:%02d:%02d", *dt end end end ``` The SNMP library doesn't...

Thanks for the pull request. Many people have asked for this feature in the past. It's especially nice to see some tests for the code change. Most people don't bother...

Under what circumstances does a deadlock occur? How does this patch fix it?