Re: snmptrapd - avoiding ambiguity in log files
| Newsgroups | gmane.network.net-snmp.user |
|---|---|
| Message-ID | <[email protected]> |
Hi Don, Am 06.09.2005 um 05:54 Uhr haben Sie geschrieben: [...] > For instance, a string variable containing tabs (or commas or > newlines) could cause output that could be parsed as a shorter > string along with a set of extra variables. > example: > > snmptrap ... SNMPv2-MIB::sysLocation.0 s $'XXX \t .1.2.3.4 = > INTEGER: 1234' > vs > snmptrap ... SNMPv2-MIB::sysLocation.0 s $'XXX' .1.2.3.4 i 1234 > > I'd like a way to generate output that can be reliably parsed > correctly. We use perl to parse the syslog file, I can't see anything unusable strings in my logs... All informations I want, I got it from my logfile! The perl regex are very powerful to do anything with the output... > If I am correct that there is currently no way to do this, then I'd > like to suggest that such a facility be provided. If that's not > correct then I'd appreciate instructions for doing it (or a pointer > to > such). I don't know where is the problem;( Ciao Andre Mit freundlichen Grüssen Andre Heine ------------------------------------------------------- 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 [email protected] Please see the following page to unsubscribe or change other options: https://lists.sourceforge.net/lists/listinfo/net-snmp-users