From 9e35faaac7436d29b607e5664b73c4676ec326a4 Mon Sep 17 00:00:00 2001 From: Guy Harris Date: Tue, 15 Apr 2014 13:20:14 -0700 Subject: Handle a timeout value of 0 better with TPACKET_V3. If the user specified a timeout value of 0, and we don't have any packets to return from pcap_read_linux_mmap_v3(), go back and wait for packets. Yes, this means waiting indefinitely, but that's what the documentation used to say, and what we're making it say again; if this is a problem, *don't use a timeout value of 0*. This should fix GitHub libpcap issue #350. --- pcap_set_timeout.3pcap | 3 --- 1 file changed, 3 deletions(-) (limited to 'pcap_set_timeout.3pcap') diff --git a/pcap_set_timeout.3pcap b/pcap_set_timeout.3pcap index fa3b167e..1a0641ee 100644 --- a/pcap_set_timeout.3pcap +++ b/pcap_set_timeout.3pcap @@ -36,9 +36,6 @@ sets the read timeout that will be used on a capture handle when the handle is activated to .IR to_ms , which is in units of milliseconds. -.LP -The behavior, if the timeout isn't specified, is undefined. We -recommend always setting the timeout to a non-zero value. .SH RETURN VALUE .B pcap_set_timeout() returns 0 on success or -- cgit v1.2.3