On 15-May-2015 10:29 pm, "Bart Van Assche" <bvanass...@acm.org> wrote: > > On 05/15/15 16:42, Dixon Xavier wrote: >> >> This is the output collected by running: >> ./snmptrapd -f -Dall -Lo >> ... >> trace: snmp_sess_select_info2_flags(): snmp_api.c, 6046: >> sess_select: for all sessions: 7 5 3 >> sess_select: next alarm at 1431718589.066441 sec >> verbose:sess_select: timer due in 4.483267 sec >> verbose:sess_select: setting timer to 4.483267 sec, clear block (was 0) >> trace: snmptrapd_main_loop(): snmptrapd.c, 593: >> snmptrapd/main_loop: after snmp_select_info numfds: 8. >> trace: snmptrapd_main_loop(): snmptrapd.c, 596: >> snmptrapd/main_loop: fd 35 is set. trace: snmptrapd_main_loop(): >> snmptrapd.c, 596: >> snmptrapd/main_loop: fd 37 is set. trace: snmptrapd_main_loop(): >> snmptrapd.c, 596: >> snmptrapd/main_loop: fd 39 is set. trace: snmptrapd_main_loop(): >> snmptrapd.c, 599: >> snmptrapd/main_loop: >> ... >> >> : >>> >>> From sess_select sockets found are 7 5 3. >> >> But those are interpreted by hp-ux system's FD_ macros as fd 35, 37, 39 are >> set. >> This causes issue and select is not able to know when trap arrives. > > > Would it be possible to test the attached patch on top of the latest v5.7 git > code ? > > Thanks, > > Bart.
Hello Bart, Thanks for the patch. I tested it and it works fine ! ./snmptrapd -f -Dall -Lo ... snmptrapd/large_fd_set: nfdbits: 64, NFDBITS: 32 ... trace: snmp_sess_select_info2_flags(): snmp_api.c, 6046: sess_select: for all sessions: 7 5 3 sess_select: next alarm at 1431945387.843953 sec verbose:sess_select: timer due in 10.000777 sec trace: snmptrapd_main_loop(): snmptrapd.c, 593: snmptrapd/main_loop: after snmp_select_info numfds: 8. trace: snmptrapd_main_loop(): snmptrapd.c, 596: snmptrapd/main_loop: fd 3 is set. trace: snmptrapd_main_loop(): snmptrapd.c, 596: snmptrapd/main_loop: fd 5 is set. trace: snmptrapd_main_loop(): snmptrapd.c, 596: snmptrapd/main_loop: fd 7 is set. trace: snmptrapd_main_loop(): snmptrapd.c, 599: snmptrapd/main_loop: ... Now snmp_select_info returns corrects fds and snmptrapd works normally ! So, when this patch will appear on net-snmp git ? Also, what would be recommended way to consume this proposed patch ? I should be able to apply this patch on top of the 5.7.3 release code, right ? Regards, Dixon Xavier ------------------------------------------------------------------------------ One dashboard for servers and applications across Physical-Virtual-Cloud Widest out-of-the-box monitoring support with 50+ applications Performance metrics, stats and reports that give you Actionable Insights Deep dive visibility with transaction tracing using APM Insight. http://ad.doubleclick.net/ddm/clk/290420510;117567292;y _______________________________________________ Net-snmp-coders mailing list Net-snmp-coders@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/net-snmp-coders
