dect
/
libpcap
Archived
13
0
Fork 0

Document that a zero value of the timeout argument to "pcap_open_live()"

can have one of two different behaviors, depending on the OS (it means
"don't return from a read until enough data has arrived" on BSD and
Digital/Tru64 UNIX, and means "return immediately" on Solaris, for
example, at least according to the man pages on Digital/Tru64 UNIX and
Solaris and the code in BSD).
This commit is contained in:
guy 2002-09-18 18:56:57 +00:00
parent ffabca7439
commit 6782a9f4a7
1 changed files with 7 additions and 2 deletions

9
pcap.3
View File

@ -1,4 +1,4 @@
.\" @(#) $Header: /tcpdump/master/libpcap/Attic/pcap.3,v 1.36 2002-09-12 19:42:03 guy Exp $
.\" @(#) $Header: /tcpdump/master/libpcap/Attic/pcap.3,v 1.37 2002-09-18 18:56:57 guy Exp $
.\"
.\" Copyright (c) 1994, 1996, 1997
.\" The Regents of the University of California. All rights reserved.
@ -153,7 +153,12 @@ arrange that the read not necessarily return immediately when a packet
is seen, but that it wait for some amount of time to allow more packets
to arrive and to read multiple packets from the OS kernel in one
operation. Not all platforms support a read timeout; on platforms that
don't, the read timeout is ignored.
don't, the read timeout is ignored. A zero value for
.IR to_ms ,
on platforms that support a read timeout,
may cause a read to wait forever to allow enough packets to arrive or
may cause a read to complete as soon as a packet arrives, depending on
the behavior of the packet capture mechanism used by libpcap.
.I errbuf
is used to return error or warning text. It will be set to error text when
.B pcap_open_live()