diff options
| author | Daniel Miller <dmiller@nmap.org> | 2018-08-24 23:55:03 -0500 |
|---|---|---|
| committer | Daniel Miller <dmiller@nmap.org> | 2018-08-24 23:55:03 -0500 |
| commit | abf508853752e3a79b8a99bdfeb929b94a490dce (patch) | |
| tree | 46da4bad2573c967fa515c72a7d4e45fea6c9957 /pcap_set_protocol_linux.3pcap | |
| parent | a1da610c66cf72e0b66483aabee4687a2d8c166f (diff) | |
Fix manpage reference formatting to be consistent.
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.
Diffstat (limited to 'pcap_set_protocol_linux.3pcap')
| -rw-r--r-- | pcap_set_protocol_linux.3pcap | 6 |
1 files changed, 4 insertions, 2 deletions
diff --git a/pcap_set_protocol_linux.3pcap b/pcap_set_protocol_linux.3pcap index 873017ba..9668a74d 100644 --- a/pcap_set_protocol_linux.3pcap +++ b/pcap_set_protocol_linux.3pcap @@ -48,7 +48,7 @@ other than a network interface, it will have no effect. .LP It should not be used in portable code; instead, a filter should be specified with -.BR pcap_setfilter(3PCAP) . +.BR pcap_setfilter (3PCAP). .LP If a given network interface provides a standard link-layer header, with a standard packet type, but provides some packet types with a different @@ -65,4 +65,6 @@ if called on a capture handle that has been activated. .SH BACKWARD COMPATIBILITY This function became available in libpcap release 1.9.0. .SH SEE ALSO -pcap(3PCAP), pcap_create(3PCAP), pcap_activate(3PCAP) +.BR pcap (3PCAP), +.BR pcap_create (3PCAP), +.BR pcap_activate (3PCAP) |