> I asked this because the variable I was having problems with was defined > as displayString... > The value send over was:"Thu Sep 9 12:51:24 2004." > > Don't know why it got printed out as hex...
Hmmm.... nope - neither do I. If the MIB file was being loaded, then the "DisplayString" should have been recognised and hence triggered the use of the DISPLAY HINT. And even without this, that particular string should be regarded as printable. Sudden thought - Unless there's a trailing new-line character that confused the hex-check. If you use '-Ox' to force a hex output, what's the last character of this value? 0x2e or something else? > SYNTAX DisplayString (SIZE (0..50)) I'm not sure offhand whether it's legal to sub-type Textual Conventions in this way. I have a sneaking suspicion that DisplayString is fixed as being (0..255), and if you need a shorter limit, then you'd either have to mention this in the DESCRIPTION clause, or define a new TC "DisplayString50" with the shorter length. But again, our MIB parser probably won't complain. Dave ------------------------------------------------------- This SF.Net email is sponsored by: YOU BE THE JUDGE. Be one of 170 Project Admins to receive an Apple iPod Mini FREE for your judgement on who ports your project to Linux PPC the best. Sponsored by IBM. Deadline: Sept. 13. Go here: http://sf.net/ppc_contest.php _______________________________________________ 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
