aboutsummaryrefslogtreecommitdiff
path: root/pcap_setnonblock.3pcap
Commit message (Collapse)AuthorAgeFilesLines
* man: Fixup more minor formatting issues. [skip ci]Denis Ovsienko2023-03-071-1/+1
|
* Fix a typo in pcap_setnonblock(3PCAP). [skip ci]Denis Ovsienko2022-07-051-1/+1
|
* doc: document PCAP_ERROR_NOT_ACTIVATED for more routines.Guy Harris2022-03-051-2/+5
|
* man: Format more special constants bold. [skip ci]Denis Ovsienko2020-08-211-5/+11
| | | | | | | Some man pages used bold font for special meaning constants (e.g. -1 for infinity, 0 for false, 1 for true, NULL), but some didn't. Make the formatting consistently bold, but leave ordinary constants (number of packets in a buffer, a timeout, a buffer size) intact.
* doc: say what pcap_next_ex() does, clarify issues with other routines.Guy Harris2020-06-071-2/+12
| | | | | | | | | | Document that pcap_next_ex() will, in non-blocking mode, return 0 if no packets are immediately available. Document precisely why pcap_loop() and pcap_next() don't behave well in non-blocking mode. [skip ci]
* Style cleanup.Guy Harris2019-11-231-3/+3
| | | | | | | | Use the BSD house style, in which, in foobar() returns 17 on success and 137 on failure. "foobar" is boldfaced but "()" isn't.
* Fix manpage reference formatting to be consistent.Daniel Miller2018-08-241-6/+8
| | | | | | | All manpage references such as pcap_create(3PCAP) will now be formatted with the identifier (e.g. "pcap_create") in **bold** and the section name (e.g. "(3PCAP)") in roman (default) face. This is how most manpages seem to be formatted and makes things more consistent.
* Spell PCAP_ERROR and PCAP_ERROR_BREAK in the man pages.Denis Ovsienko2018-07-251-3/+7
| | | | [skip ci]
* Refine references in some man pages, round 4.Denis Ovsienko2018-07-181-6/+6
| | | | [skip ci]
* update last modified date in man page(s)Denis Ovsienko2015-12-181-1/+1
|
* Be more emphatic that a read timeout may cause no packets to be read.Guy Harris2014-10-181-0/+8
| | | | | | | | | | | | | | | | | | Note, in more places, that if you call pcap_dispatch() on a pcap_t for which there's a read timeout, it might return 0 if the read timeout expires and there are no packets to be read - but that this behavior is not guaranteed (so write your code to be able to handle it if it does happen but not to depend on it happening). Note also that a select()/poll()/etc. on the selectable descriptor for the pcap_t might report the descriptor as readable if the read timeout expires, even if there are no packets available to read - but that it might not (so write your code to be able to handle it if it does happen but not to depend on it happening). Also, note that pcap_t's start out blocking, so they don't think that a 0 return from pcap_dispatch() means it's non-blocking and that they need to call pcap_setnonblock() to put it in blocking mode.
* remove libpcap's own CVS keywordsDenis Ovsienko2014-01-031-2/+0
| | | | | | This change removes CVS keywords that express that the file belongs to libpcap repository. All such keywords represented the revision and timestamp by the end of 2008 or even older.
* Document the new API's, move a bunch of information about libpcapguy2008-04-061-7/+5
| | | | | | concepts to the pcap(3PCAP) man page, refer people to the pcap(3PCAP) man page from the man pages for libpcap functions, and clean up some errors.
* Include <pcap/pcap.h> in the SUMMARY sections - as long as we're goingguy2008-04-051-2/+2
| | | | | | | to 1.0, might as well go with the place where Red Hat stuck the header at one point and where the header "officially" resides. (We should put a "backwards compatibility" note into pcap.3pcap.)
* Split the pcap(3) man page into a bunch of individual man pages forguy2008-04-051-0/+77
functions plus an overall man page for libpcap, and put them all into section 3PCAP. That means you can actually do "man pcap_open_live" and get something meaningful, rather than having to do "man pcap" and then scroll through all the other stuff in the man page.