summaryrefslogtreecommitdiff
path: root/pcap_breakloop.3pcap
Commit message (Collapse)AuthorAgeFilesLines
* Get fonts right in pcap_breakloop(3PCAP). [skip ci]Denis Ovsienko2023-03-101-1/+1
| | | | | | Move one "use regular font" macro such that every "note that" block switches between bold and regular font explicitly. This way HTML output has the same style as console man.
* Remove a trailing spaceFrancois-Xavier Le Bail2022-12-191-1/+1
| | | | [skip ci]
* pcap_breakloop(3PCAP): describe behavior of versions in older libpcaps. ↵Guy Harris2022-12-081-1/+8
| | | | [skip cp]
* pcap_breakloop(3PCAP): describe the shiny new world. [skip ci]Guy Harris2022-12-071-20/+46
| | | | | | | | | | | | | | | | | | | | | | | | Note that, on Linux and Windows, pcap_breakloop() attempts to force a wakeup on the thread reading the packets. Note all the hilarity that ensues from that; this is one of the areas where capture-mechanism differences are not quite so easily papered over. (These capture mechanisms were all pretty much designed for a program that reads captures until it's told to stop, and then may or may not process packets that arrived after that point. Making it available through libpcap has opened up packet capturing to a zillion developers, many of whom are doing different types of capture programs with different requirements, and stumbling over all these problems. Perhaps it's time for a rethink. We won't even mention the use of the capture mechanisms for purposes *other* than packet capture, such as implementing various protocols atop the link-layer; libpcap's API is not the best fit for that - a corss-platform "link-layer sockets" library, possibly using a *different* OS mechanism than libpcap on some platforms, might be handy there.)
* Revert "pcap_breakloop(3PCAP): fix formatting of function names." [skip ci]Guy Harris2022-12-071-15/+7
| | | | | | | | This reverts commit 4441992020d06cd219c085f587fc9471b4f883b0. For the two paragraphs in question, the entire paragraph in which those function names appear is boldfaced, so we shouldn't tweak function name references in those paragraphs.
* pcap_breakloop(3PCAP): fix formatting of function names. [skip ci]Guy Harris2022-12-071-7/+15
|
* Style cleanup.Guy Harris2019-11-231-13/+13
| | | | | | | | 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-3/+3
| | | | | | | 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-5/+10
| | | | [skip ci]
* Refine references in some man pages, round 1.Denis Ovsienko2018-07-171-4/+4
| | | | | | | | | | | | | When a man page text for the first time refers to a libpcap function that is not a topic of the man page, make sure it points to the 3PCAP section. This way the reference becomes a hyperlink in the HTML version and the web-site cohesion improves. Make sure the SEE ALSO section does not list references already present in the main text. This way the references that appear only in SEE ALSO are much easier to notice, and cohesion remains the same. [skip ci]
* Update the timestamp in some man pages.Denis Ovsienko2018-07-111-1/+1
| | | | | | | | In the man pages that since the previous timestamp had meaningful (i.e. not typos or whitespace fixups) changes set the timestamp to the date of such last meaningful change. [skip ci]
* Breaking out of a blocking call on Windows.Guy Harris2017-11-081-2/+13
|
* Mention thread signalling as a way to break out of a blocking capture read.Guy Harris2017-11-071-1/+2
|
* update last modified date in man page(s)Denis Ovsienko2015-12-181-1/+1
|
* Delete trailing spaces/tabsFrancois-Xavier Le Bail2015-03-081-1/+1
|
* 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.
* Fix up boldfacing.Guy Harris2012-12-111-12/+7
| | | | | | | | | | | | | Different renderers (different *roffs, different -man macro packages, different man-to-HTML translators, etc.) may handle fonts and paragraph boundaries differently, or may handle font resetting in .BR and .B differently, so: reset the font at or before the end of a paragraph; don't assume that font changes persist across paragraph breaks; don't use .B or .BR inside boldfaced text.
* Document the new API's, move a bunch of information about libpcapguy2008-04-061-3/+3
| | | | | | 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/+105
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.
View Lorry Controller Status