Hi Kaspars,

Kaspars Bankovskis wrote on Fri, Dec 12, 2014 at 03:22:16PM +0200:

> Function arguments in synopsis for pcap_inject and pcap_sendpacket are
> a bit messed up by comma. Types updated from actual code.
> And some .An and .In macro fixes while there.

Committed, thanks.

Some more argument names are missing, and i wouldn't be surprised
if more argument types were wrong.  If someone knowledgeable in
this area could clean it up, that might be welcome.

It's one of these pages that are kind of a mess in the first place,
somewhat like rpc(3), excessively huge and suspiciously terse at
the same time, quite possibly lacking relevant details in spite of
all that bulk...  :-(

Yours,
  Ingo


> Index: pcap.3
> ===================================================================
> RCS file: /cvs/src/lib/libpcap/pcap.3,v
> retrieving revision 1.35
> diff -u -p -r1.35 pcap.3
> --- pcap.3    25 Jun 2013 16:49:39 -0000      1.35
> +++ pcap.3    11 Dec 2014 23:13:38 -0000
> @@ -26,7 +26,7 @@
>  .Nm pcap
>  .Nd Packet Capture library
>  .Sh SYNOPSIS
> -.Fd #include <pcap.h>
> +.In pcap.h
>  .Ft "pcap_t *"
>  .Fn pcap_open_live "char *device" "int snaplen" "int promisc" "int to_ms" 
> "char *errbuf"
>  .Ft "pcap_t *"
> @@ -46,9 +46,9 @@
>  .Ft void
>  .Fn pcap_dump "u_char *user" "struct pcap_pkthdr *h" "u_char *sp"
>  .Ft int
> -.Fn pcap_inject "pcap_t *p" "void *, size_t"
> +.Fn pcap_inject "pcap_t *p" "const void *buf" "size_t len"
>  .Ft int
> -.Fn pcap_sendpacket "pcap_t *p" "void *, int"
> +.Fn pcap_sendpacket "pcap_t *p" "const u_char *buf" "int size"
>  .Ft int
>  .Fn pcap_compile "pcap_t *p" "struct bpf_program *fp" "char *str" "int 
> optimize" "bpf_u_int32 netmask"
>  .Ft int
> @@ -562,7 +562,10 @@ routine to an error string.
>  .Xr tcpdump 8
>  .\" , tcpslice(1)
>  .Sh AUTHORS
> -Van Jacobson,
> -Craig Leres and
> -Steven McCanne, all of the
> +.An -nosplit
> +.An Van Jacobson ,
> +.An Craig Leres
> +and
> +.An Steven McCanne ,
> +all of the
>  Lawrence Berkeley National Laboratory, University of California, Berkeley, 
> CA.

Reply via email to