Philippe Guibert <philippe.guib...@6wind.com> writes: > Thanks for letting me know if that approach should be considered or > not,
Personally, I'll have to think a lot about it. But in general, agentx was designed (and if you haven't read the RFC for it, you probably should to get a better understanding of the protocol's design). Specifically, there needs to be locking issues in the subagent to consider when attached to multiple upstream parent agents. SNMP SETs, in particular, go through a multi-phase transition to ensure you can safely perform and/or undo a SET. Right now, that handling is done in the parent agent to ensure that only one SET is handled at a time. I suspect there are some other issues to think about too. -- Wes Hardaker Please mail all replies to net-snmp-coders@lists.sourceforge.net _______________________________________________ Net-snmp-coders mailing list Net-snmp-coders@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/net-snmp-coders
