Hi folks, In a recent thread, it came up that on a few OSes ( and in my case, Linux RH6.2) pcap_dispatch will block if no packets are coming in -- i.e., due to the underlying capture mechanisms in these OSes, the read timeout wont let pcap_dispatch to return in the absence of packets.
Now, in my application I need to be doing some processing regardless of the packets coming in or not. The only clean way of doing this is to use a multithreaded approach and have one thread take care of all the packet capture stuff and have another do the other regular processing. I am not a big fan of Multi threading, so my intent in this post is to confirm that no easy fix in libpcap sources (for my specific Linux6.2 case), is going to solve my pcap blocking problem and that I will have to indeed go the multi-threaded way. Can someone confirm this "feature" or is there a way to break out of pcap_dispatch? I have considered using alarms/itimers but that model doens't suit too well to my application semantics Thanks, Joe __________________________________________________ Do You Yahoo!? Find a job, post your resume. http://careers.yahoo.com - This is the TCPDUMP workers list. It is archived at http://www.tcpdump.org/lists/workers/index.html To unsubscribe use mailto:[EMAIL PROTECTED]?body=unsubscribe
