Call the timeout the "packet buffer timeout" rather than the "read timeout".

That should make it clearer that the timeout does *not* guarantee that a
call that reads packets will return within N milliseconds even if no
packets arrive.

In the pcap_open_live() and pcap_set_timeout() calls, point to the
detailed description of the packet buffer timeout in pcap(3PCAP).

1 files changed, 1 insertions, 1 deletions

diff --git a/pcap-rpcap.c b/pcap-rpcap.c
index 5add0573..d8526c4c 100644
--- a/pcap-rpcap.c
+++ b/pcap-rpcap.c
@@ -219,7 +219,7 @@ static int pcap_read_nocb_remote(pcap_t *p, struct pcap_pkthdr **pkt_header, u_c
 	md = (struct pcap_md *) ((u_char*)p->priv + sizeof(struct pcap_win));
 
 	/*
-	 * Define the read timeout, to be used in the select()
+	 * Define the packet buffer timeout, to be used in the select()
 	 * 'timeout', in pcap_t, is in milliseconds; we have to convert it into sec and microsec
 	 */
 	tv.tv_sec = p->opt.timeout / 1000;