Re^4: Problem using threads and snmp

Hello BrowserUK, Thank you for your reply. The error that states is a timeout. What i'm going to try to do is a unique method for all threads . This method will create the snmpsession and do the snmpget. Of course i will have to lock the access to this method. I will keep you posted. Cheers.

Comment on Re^4: Problem using threads and snmp

Replies are listed 'Best First'.
Re^5: Problem using threads and snmp by NetWallah (Canon) on Apr 16, 2008 at 16:51 UTC
... . Of course i will have to lock the access to this method .. Wouldn't that defeat the purpose of running the threads in parallel ? I'm uncomfortable with your implementation of the locking to obtain and send data. Subtle bugs in this type code are notoriously difficult to notice/find/fix. My preference would be to use Thread::Queue, which will do all that for you, and probably simplify your main loop considerably. (The sample code, again). "How many times do I have to tell you again and again .. not to be repetitive?"	[reply]
Re^5: Problem using threads and snmp by BrowserUk (Patriarch) on Apr 16, 2008 at 15:33 UTC
I'd love to see the output when full trace is enabled. Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error. "Science is about questioning the status quo. Questioning authority". In the absence of evidence, opinion is indistinguishable from prejudice. "Too many [] have been sedated by an oppressive environment of political correctness and risk aversion."	[reply]