Re: snmptrapd - avoiding ambiguity in log files

Thomas Anders writes:

> What you're seeing is the difference between:
>
> 1) objects of type OCTET STRING defined as SYNTAX SnmpAdminString or
> DisplayString (e.g. the SNMPv2-MIB::sysLocation.0 you tested with)
> 2) objects of type OCTET STRING defined as SYNTAX OCTET STRING or
> without a known MIB object definition
>
> snmptrapd displays (consistently in 5.1.x, 5.2.x and CVS MAIN):
> 1) as STRING: XXXX (w/o quotes)
> 2) as STRING: "XXXX" (w/ quotes)
>
> I'm not in the mood to comment on whether this behaviour is the most
> sensible. Anyone else?

I argue that there should be SOME way to avoid all ambiguities of the
sort I described. My preference would be that this should happen
without any special configuration or command line arguments. I would
also prefer something that is relatively easy to parse.


-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf
_______________________________________________
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/...net-snmp-users