[Michael Higgins]: > I did a little digging and it looks like the problem is in > agent/mibgroup/utilities/execute.c in run_exec_command(). I don"t know > a whole lot about how this is architected, but it appears that two > threads are responsible for making this happen. One gets the trap > handler process running and the other writes to its stdin and waits for > any output.
Hm, this answers my earlier question, I think, regarding python and trap-handling scripts querying the agent. Looking in execute.c I see that the external script is calle synchronously and I guess that the thread which calls this code is the same that serves up information to clients. I also found in the FAQ (which I hadn't read fully - ack!) notes about how the agent runs within a single thread and that "Adding full multi-thread support directly to the agent would be nice.". Yep, nice. Since I've forgotten how to write in C and I'm short on cash, I wonder if the SNMP agent could be "decorated" by a wrapper process, which queues requests and delivers them to the real agent....? The wrapper would have to be able to parse the snmpd.conf file, and it could farm out pass requests itself. The approach I've taken to solve my original problem is a different one, but it would be handy, I think, to have a re-entrant snmp agent... Comments? dave Send instant messages to your online friends http://uk.messenger.yahoo.com ------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click _______________________________________________ Net-snmp-users mailing list Net-snmp-users@lists.sourceforge.net Please see the following page to unsubscribe or change other options: https://lists.sourceforge.net/lists/listinfo/net-snmp-users
