2009/6/22 Need Help <[email protected]>: > "snmpd.c" is the wrapper structure for the Net-SNMP standalone agent > application. > > After reading through the Wiki information I believe the "snmpd.c" code is > only used when you compile the subagent code directly into the main agent
Hmmm.... That's a somewhat confusing way of phrasing things. You don't compile "subagent code" into the main agent. You compile code to implement a particular MIB module into the main agent (or a subagent). The "subagent code" is a wrapper round one or more MIB modules, in much the same way as snmpd.c is for the standalone agent. > (ie: not using AgentX yet) for testing purposes only. That's overstating things as well. It's perfectly normal to link the code for a new MIB module into the main agent binary - either directly, or using "dlmod". These two, plus AgentX are three alternative approaches. There's nothing that makes one the Right Thing To Do, or the other "for testing purposes only". > "Compiling the > subagent directly into the master agent often makes debugging a little bit > easier and takes the AgentX protocol out of the mix just to be sure". Compiling the MIB module into the master agent has these benefits, yes. I wouldn't describe it as "compiling the subagent into the master agent". > Will someone please confirm that a "Net_SNMP standalone agent application" > is indeed an application in which the subagent is compiled into the master > agent and that this is when the "snmpd.c" file is used only. The snmpd.c file is indeed only used with the standalone agent. If you replace "subagent" with "MIB modules" in the above statement, then I'd say that this is reasonably accurate. Dave ------------------------------------------------------------------------------ _______________________________________________ Net-snmp-coders mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/net-snmp-coders
