| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
|
|
| |
In pcap_get_required_select_timeout.3pcap merge two "backward
compatibility" sections into one. In pcap-filter.manmisc.in,
pcap-config.1 and pcap_dump_open.3pcap.in make section names consistent
with other man pages.
|
| | |
|
| |
|
|
|
|
| |
Note that it does *not* append.
This is an additional fix for GitHub issue #950.
|
| |
|
|
|
|
|
|
|
| |
Document that pcap_dump_open() will overwrite an existing file.
Document that pcap_dump_open_append() will create the file if it doesn't
exist, rather than falsely claiming it won't.
This should fix GitHub issue #950.
|
| |
|
|
|
|
|
|
|
| |
For clarity, as before, the last modified date stands for changes more
substantial than trivial editorial and formatting fixups. That, for
example, would be at least a change of the described behaviour, return
value, semantics or backward compatibility.
[skip ci]
|
| |
|
|
|
|
|
|
| |
Use the BSD house style, in which, in
foobar() returns 17 on success and 137 on failure.
"foobar" is boldfaced but "()" isn't.
|
| |
|
|
|
|
|
| |
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.
|
| |
|
|
|
|
| |
Expand the BACKWARD COMPATIBILITY section to either say "sorry, you
can't get that with earlier releases of libpcap" or "if you need this,
here's what you'd have to do".
|
| |
|
|
|
|
| |
(as suggested by Daniel Miller in GH #745)
[skip ci]
|
| |
|
|
|
|
|
| |
Among other things make sure a reference to pcap(3PCAP) is in the
SEE ALSO section of every man page by default.
[skip ci]
|
| |
|
|
| |
[skip ci]
|
| | |
|
| |
|
|
|
|
|
|
| |
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]
|
| |
|
|
|
|
|
|
| |
It isn't stated in the documentation whether the FILE* passed to
pcap_dump_fopen() will be closed by a subsequent pcap_dump_close().
This lack of clarity can cause the user to close the FILE* themselves
after calling pcap_dump_close(), which leads to SIGABRT on some platforms.
|
| |
|
|
|
|
|
|
| |
In some man pages the roff processor hyphenated function names in the
"SEE ALSO" section, add markup to prevent that. Also disable line
adjustment in pcap-tstamp.manmisc to suppress the warning:
<standard input>:171: warning [p 2, 11.0i]: cannot adjust line
|
| | |
|
| |
|
|
|
|
|
|
|
| |
Sadly, there's no fopen() mode that says "create this if it doesn't
exist, *leave it alone if it does*, open the file for reading and
writing, and *don't* force all writes to append to the file"; for now,
we just go with the semantics of "r+", which means it fails if it
doesn't exist. That's what Mark Johnston's patch, from which the
earlier change was derived, did.
|
| |
|
|
| |
See GitHub issue #247.
|
| |
|
|
|
|
| |
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.
|
| | |
|
|
|
Refer to it from the pcap_open_offline() and pcap_dump_open() man pages
(so they are now generated).
Update .cvsignore.
|
