Page MenuHomeFreeBSD

bsnmpget should print protocol errors to stderr
ClosedPublic

Authored by eugen_grosbein.net on Aug 1 2020, 9:08 AM.
Tags
None
Referenced Files
Unknown Object (File)
Thu, Apr 18, 11:52 PM
Unknown Object (File)
Mar 8 2024, 3:56 PM
Unknown Object (File)
Mar 8 2024, 3:56 PM
Unknown Object (File)
Mar 8 2024, 6:35 AM
Unknown Object (File)
Mar 8 2024, 6:23 AM
Unknown Object (File)
Jan 13 2024, 3:47 AM
Unknown Object (File)
Dec 20 2023, 5:20 AM
Unknown Object (File)
Nov 10 2023, 7:58 PM
Subscribers

Details

Summary

Currently it is hard to determine if remote SNMP agent supports needed OID/subtree using automated tools with bsnmpget(1) because it prints an error to stdout mixing it with received other data.

This change makes it print error to stderr, as well as bsnmpwalk/bsnmpset that is same tool really.

Test Plan

Try to check for IF-MIB::ifHCInMulticastPkts

bsnmpwalk -o quiet -n -r 3 -t 2 -s public@switch .1.3.6.1.2.1.31.1.1.1.8 > /dev/null

Diff Detail

Repository
rS FreeBSD src repository - subversion
Lint
Lint Not Applicable
Unit
Tests Not Applicable

Event Timeline

Looks good to me; let's wait if syrinx thinks the same.

The change looks reasonable to me, please commit

This revision is now accepted and ready to land.Aug 5 2020, 9:05 AM