Hi, > I added the command to build the binaries to debian/rules, that is > probably easier for upstream. I am okay with that.
> Is it possible that you write man pages for those binaries to that I > don't end up with "binary without manpage" lintian warnings? Those > manpages could also go upstream. I wrote two manpages for the two simple tools dnswasher and dnsscope. As they are my first pages I wrote in nroff/groff format let me know if anything is messed up with the layout. best regards -- Joerg Jungermann borkum.NET - ideas, linux, networks, typo3, c64, 42
.TH DNSWASHER 8 "September 2012" "PowerDNS" .SH NAME dnswasher \- A PowerDNS nameserver debugging tool .SH SYNOPSIS .B dnswasher \fI[infile]\fR \fI[outfile]\fR .SH DESCRIPTION dnswasher takes an \fIinfile\fR in PCAP format and writtes out \fIoutfile\fR also in PCAP format. It copies all network traffic found in \fIinfile\fR to \fIoutfile\fR except for non DNS traffic. This might be handy when creating bug reports or test cases for DNS software e.g. PowerDNS. .SH OPTIONS None. .SH SEE ALSO pcap(3PCAP), tcpdump(8) .SH AUTHORS This manpage was written by Joerg Jungermann (jj+debian At borkum.net) for the Debian Project and the PowerDNS versatile DNS server.
.TH DNSSCOPE 8 "September 2012" "PowerDNS" .SH NAME dnsscope \- A PowerDNS nameserver debugging tool .SH SYNOPSIS .B dnsscope \fI[infile]\fR .SH DESCRIPTION dnsscope takes an \fIinfile\fR in PCAP format. It generates some simple statistics outputs these to STDOUT. .SH OPTIONS None. .SH SEE ALSO pcap(3PCAP), tcpdump(8) .SH AUTHORS This manpage was written by Joerg Jungermann (jj+debian At borkum.net) for the Debian Project and the PowerDNS versatile DNS server.
