The upper half of the "if" statement in _next_data_point() seems to need
to end in "return idx". If I understand the operation of
netsnmp_table_iterator_helper_handler() properly, it probably wants
_next_data_point() to decide on the proper termination point, once all
indices for a row have been f
WH>Well, threading does cause concerns since the Net-SNMP agent is not
WH>thread-safe at all. But if it's run in a single thread itself, I think
WH>it should work assuming you take careful control of pointers going into
WH>and out of the Net-SNMP thread and never allowing them to be used in two
WH
> On Mon, 14 Sep 2009 10:59:31 +0530, Hemant Soundankar
> said:
HS> Error: couldn't open a master agentx socket to listen on ():
It means you don't have permission to open the default agentx socket.
If you're running it as yourself, or another user that is not root, then
you could have
> On Fri, 11 Sep 2009 16:38:58 -0600, "Leo Bredehoft"
> said:
LB> Startup code is in a main thread, after which a service thread is
LB> spawned to loop on agent_check_and_process(). The failure is
LB> solidly reproducible, too.
Well, threading does cause concerns since the Net-SNMP age
Dear Coders:
I have implemented an AgentX subagent which connects snmpd on CentOS 5.3
Linux to a C++ application. To keep the maintenance for a
frequently-changing MIB low, I have written a mib2c .conf file based on
mib2c.scalar.conf and mib2c.iterate.conf. The scalar portion of the
subagent
