I'm using net-snmp 5.1.1 and I have an snmpd sub-agent that dies when I stress it and
I'm trying to understand the interaction between snmpd and my program, at least in
broad strokes before I dig into the code to deeply.
I have a user interface program which makes requests of snmpd and displays values.
Some of the values that snmpd returns come from my sub-agent. With one or two UIs
running, all is well. If I get to 4-5 instances of the UI, my sub-agent begins timing
out and eventually stops. (The sub-agent normally runs as a daemon but for debugging
purposes, I run it in an interactive shell and when it gives up the ghost, I get my
prompt back but none of the normal shut-down mesasges.)
So, I've got some questions about the AgentX protocol:
1) Does snmpd establish one IPC link to the sub-agent and send each request through
that persistent connection or does it connect to the sub-agent for each request?
2) If multiple clients of snmpd ask for the same value (albeit a second or two apart),
I assume that snmpd will get the value from the sub-agent each time rather than
caching it or doing any other optimization. Is that right?
TIA for any pointers.
Chris
-------------------------------------------------------
This SF.Net email is sponsored by BEA Weblogic Workshop
FREE Java Enterprise J2EE developer tools!
Get your free copy of BEA WebLogic Workshop 8.1 today.
http://ads.osdn.com/?ad_id=4721&alloc_id=10040&op=click
_______________________________________________
Net-snmp-users mailing list
[EMAIL PROTECTED]
Please see the following page to unsubscribe or change other options:
https://lists.sourceforge.net/lists/listinfo/net-snmp-users
