--> jsafrane has joined #net-snmp
--> SJFriedl has joined #net-snmp
--> Linkadmin has joined #net-snmp
--> tris has joined #net-snmp
--> lievin has joined #net-snmp
--> fenestro has joined #net-snmp
--> Sammitch has joined #net-snmp
--> ne2k__ has joined #net-snmp
--> ChanServ has joined #net-snmp
--> ghoti has joined #net-snmp
--> krphop has joined #net-snmp
--> Groenleer has joined #net-snmp
--> tanders has joined #net-snmp
--> boogah has joined #net-snmp
--> glen has joined #net-snmp
--> blotchy has joined #net-snmp
--> royan has joined #net-snmp
--> darix has joined #net-snmp
[2010/08/23 01:19:30] #net-snmp <ne2k__> http://pastebin.ca/1923191 I asked a question on Friday night about how async operation works internally, but I had to leave before the answer came and I then couldn't follow up the answer. I'm trying to work out exactly how the callback function gets called
[2010/08/23 01:21:57] #net-snmp <ne2k__> is the callback called by snmp_read, then?
[2010/08/23 02:48:00] #net-snmp <ne2k__> yes, I've just answered my own question by reading the source of snmp_api.c
--> ecolitan has joined #net-snmp
--> hardaker has joined #net-snmp
--> hardaker2 has joined #net-snmp
--> rstory-work has joined #net-snmp
--> Sammitch has joined #net-snmp
--> Sangwidge has joined #net-snmp
--> blotchy has joined #net-snmp
--> hardaker2 has joined #net-snmp
--> Linkadmin has joined #net-snmp
--> hardaker2 has joined #net-snmp
--> Loginx has joined #net-snmp
--> tanders has joined #net-snmp
--> ecolitan has joined #net-snmp
--> jsafrane has joined #net-snmp
--> snmpbot has joined #net-snmp