[issue16338] pysnmp/asyncore - timeout ineffective?

Changes by Charles-François Natali : -- resolution: -> invalid stage: -> committed/rejected status: open -> closed ___ Python tracker ___ __

[issue16338] pysnmp/asyncore - timeout ineffective?

Charles-François Natali added the comment: It's a little too vague :-) You should probably report this on pysnmp mailing list. If you want to debug this, you should perform a tcpdump/wireshark capture while running your script, and see what happens (according to your description, it may simply

[issue16338] pysnmp/asyncore - timeout ineffective?

Trenton Craig added the comment: So, in testing, we reset retries to 1 instead of 0, and on our ubuntu environment this allows it to function. So issue is not with timeout, but with the retries variable. -- ___ Python tracker

[issue16338] pysnmp/asyncore - timeout ineffective?

New submission from Trenton Craig: I have an application that is set to use pysnmp to obtain sysDescription and system names from devices on our network. Currently, we are using python 2.6.2, due to the limitations of the box (solaris), and it works fine. However, our new environment uses pyt