Re: 5.8 testing status

On Fri, 4 May 2018 11:25:35 -0400 Bill wrote:
BF> I started writing a test for this, and found that it's seriously
BF> convoluted.  The combination of clientaddr + trap*sink results
BF> in the bind() attempting to use port 161 for the clientaddr, so
BF> it doesn't work as non-root (in the test context) and would
BF> either not work as root or intercept actual SNMP packets
BF> destined for the given address.  The same happens with the "-s"
BF> argument for the trap2sink command.
BF> 
BF> My proposed fix works for my trapsess case, so I guess that's
BF> something. Should I commit the broken tests so anyone else who
BF> wants to try to fix the trap*sink code has a starting point?
BF> Is the "specifying clientaddr and trap*sink together fails"
BF> regression a release blocker or just something to release-note?

I don't want to add any release blockers at this point. Maybe
commit the test to a branch? If you get it working before 5.8
final I'd vote for inclusion.

Robert

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot