Any comments?
On Mar 29 22:24:41, h...@stare.cz wrote:
> The diff below fixes what seem to be errors in pcap.3,
> either in factuality or markup or grammar.
>
> Jan
>
>
>
> --- pcap.3.orig Sun Mar 29 22:06:49 2015
> +++ pcap.3 Sun Mar 29 22:16:50 2015
> @@ -169,7 +169,7 @@ at packets on the network.
> .Fa source
> is a string that specifies the network device to open.
> .Fa snaplen
> -specifies the maximum number of bytes to capture.
> +specifies the maximum number of bytes to capture from one packet.
> .Fa promisc
> specifies if the interface is to be put into promiscuous mode.
> (Note that even if this parameter is false, the interface
> @@ -209,7 +209,7 @@ for writing.
> The name
> .Ql -
> is a synonym for
> -.Dv stdin .
> +.Dv stdout .
> .Dv NULL
> is returned on failure.
> .Fa p
> @@ -229,7 +229,7 @@ can be used to get the error text.
> .Pp
> .Fn pcap_dump_fopen
> allows the use of savefile functions on the already-opened stream
> -.Dq f .
> +.Fa f .
> .Pp
> .Fn pcap_lookupdev
> returns a pointer to a network device suitable for use with
> @@ -276,7 +276,7 @@ pointer which is passed in from
> .Fn pcap_dispatch ,
> a pointer to the
> .Fa pcap_pkthdr
> -struct (which precede the actual network headers and data),
> +struct (which precedes the actual network headers and data),
> and a
> .Fa u_char
> pointer to the packet data.
> @@ -351,7 +351,7 @@ return when live read timeouts occur.
> Rather, specifying a non-zero read timeout to
> .Fn pcap_open_live
> and then calling
> -.Fn pcap_dispatch
> +.Fn pcap_loop
> allows the reception and processing of any packets that arrive when the
> timeout occurs.
> A negative
> @@ -490,10 +490,11 @@ It is typically used when just using libpcap for compi
> .Pp
> .Fn pcap_fopen_offline
> may be used to read dumped data from an existing open stream
> -.Dq fp .
> +.Fa fp .
> .Pp
> .Fn pcap_lib_version
> returns a string describing the version of libpcap.
> +.Pp
> .Fn pcap_datalink_val_to_name
> and
> .Fn pcap_datalink_val_to_description
