Sorry, forgot to attach the manpage patch to the bug report. Here it is attached.
In the meantime I've noticed that there *is* a manpage you already wrote for this package. I think that the manpage I have written is more complete and detailed and also, since it is in SGML format, it is easier to maintain. I would like to encourage you to use this new manpage instead. Regards Javier
diff -Nru daemonlogger-1.2.1.orig/debian/daemonlogger.8 daemonlogger-1.2.1/debian/daemonlogger.8 --- daemonlogger-1.2.1.orig/debian/daemonlogger.8 1970-01-01 01:00:00.000000000 +0100 +++ daemonlogger-1.2.1/debian/daemonlogger.8 2011-01-02 02:34:36.137783532 +0100 @@ -0,0 +1,134 @@ +.TH "DAEMONLOGGER" "8" +.SH "NAME" +daemonlogger \(em program capture packets from an interface and log or rewrite them +.SH "SYNOPSIS" +.PP +\fBdaemonlogger\fR [\fB-c \fIcount\fR\fP] [\fB-d\fP] [\fB-f \fIbdf file\fR\fP] [\fB-F\fP] [\fB-g \fIgroup name\fR\fP] [\fB-i \fIinterface\fR\fP] [\fB-l \fIpath\fR\fP] [\fB-m \fIcount\fR\fP] [\fB-m \fIcount\fR\fP] [\fB-M \fIpct\fR\fP] [\fB-n \fIname\fR\fP] [\fB-o \fIout interface\fR\fP] [\fB-p \fIpidfile\fR\fP] [\fB-P \fIpidpath\fR\fP] [\fB-r\fP] [\fB-R \fIpcap file\fR\fP] [\fB-s \fIbytes\fR\fP] [\fB-S \fIsnaplen\fR\fP] [\fB-t \fItime\fR\fP] [\fB-u \fIuser name\fR\fP] [\fB-T \fIchroot path\fR\fP] [\fIbdf filter\fR] +.SH "DESCRIPTION" +.PP +This manual page documents briefly the +\fBdaemonlogger\fR. +.PP +This manual page was written for the \fBDebian\fP distribution +because the original program does not have a manual page. +.PP +\fBdaemonlogger\fR is a simple packet logging and +software tapping program that can be run both in foreground or in +daemon mode. +.PP +\fBdaemonlogger\fR can be used in two different +(and mutually exclusive) ways: +.IP "Sniffing mode" 10 +In this mode, \fBdaemonlogger\fR will +read (sniff) packets from a network interace and spool them straight +to disk. It will automatically roll over the capture file when it +reaches a specific size. + +.IP "Software tap" 10 +In this mode, \fBdaemonlogger\fR will +read packets from an input interface and rewrite them to a second +(output) interface, acting as a software tap. + +.SH "OPTIONS" +.PP +You can specify packet filter commands after the command line +switches just like in tcpdump or Snort. If no filter is defined +it will capture all packets coming to the interface. +.PP +A summary of available options is included below. +.IP "\fB-h\fP " 10 +Show summary of options. +.IP "\fB-v\fP " 10 +Show version of program. +.IP "\fB-c \fIcount\fR\fP " 10 +Log \fIcount\fR packets and exit. +.IP "\fB-d\fP " 10 +Daemonize at startup. +.IP "\fB-f \fIbdf file\fR\fP" 10 +Load the BPF filter to use from \fIbdf file\fR. +.IP "\fB-F\fP" 10 +Flush the pcap buffer for each packet. As each packet is saved, +it will be written to the output file rather than being written only when the +output buffer fills. +.IP "\fB-g \fIgroup name\fR\fP" 10 +Set the group ID of the process running the program to \fIgroup name\fR. +.IP "\fB-i \fIinterface\fR\fP" 10 +Grab packets from the interface \fIinterface\fR. +.IP "\fB-l \fIpath\fR\fP" 10 +Log all the pcap log files to directory \fIpath\fR. +.IP "\fB-m \fIcount\fR\fP" 10 +Generate \fIcount\fR log files and exit. +If using Ringbufer mode then write files and delete the oldest file in +the set when you exceed log files written. The program will not exit +when in this mode. +.IP "\fB-M \fIpct\fR\fP" 10 +Used in concert with the \fB-r\fP ringbuffer switch +this option will write log files to the disk until it is at +\fIpct\fR utilization and then roll over and delete the +oldest log file. For example, "\-M 90" would write files to the disk until it +is 90% utilized and then roll over and delete the oldest file in the +logging directory. If the \fB-s\fP "size" switch is not set then the +default log file size is 2GB. +.IP "\fB-n \fIname\fR\fP" 10 +Set output filename prefix to \fIname\fR. +The default is daemonlogger.pcap. +.IP "\fB-o \fIout interface\fR\fP" 10 +Act as a software tap: disable logging and retransmit all data from +\fIinterface\fR to \fIout interface\fR. +.IP "\fB-p \fIpidfile\fR\fP" 10 +When running in daemon mode, use \fIpidfile\fR for the name of the PID file created. The default is daemonlogger.pid. +.IP "\fB-P \fIpidpath\fR\fP " 10 +When running in daemon mode, use \fIpidpath\fR as the directory where PID files will be created. The default is +/var/run. +.IP "\fB-r\fP" 10 +Activate ringbuffer mode. +.IP "\fB-R \fIpcap file\fR\fP " 10 +Read packets from \fIpcap file\fR instead +of using an input interface. +.IP "\fB-s \fIbytes\fR\fP" 10 +Rollover the log file every \fIbytes\fR bytes. By default the rollover occurs every 2 GB. The parameter +\fIbytes\fR can be appended with "k" (for KiloBytes), "m" +(for MegaBytes), "g" (for Gigabytes) and "t" (for TeraBytes). +.IP "\fB-S \fIsnaplen\fR\fP " 10 +Capture \fIsnaplen\fR bytes per packet. If not +defined, all the contents of the packets will be captured (which is equivalent +to setting \fIsnaplen\fR to 65535 bytes. +.IP "\fB-t \fItime\fR\fP" 10 +Rollover the log file on specific time intervals. The time interval +can be appended with "m" (for minutes), "h" (for hours) or "d" (for days). If no interval selector is used then the +default rollover interval is in seconds. For example, "\-t 60" rolls the log +file over every 60 seconds and "\-t 2h" rolls the log file over every two hours +at the top of the hour. In the case of minute/hour/day-based rollovers, the +will round to the next highest hour. For example, if the program is told to +rollover every 2 hours and is started 38 minutes into the current hour it will +add 2 to the current hour and rollover as scheduled at the top of the hour at ++ 2. If the program was started at 13:38 it would roll over the +logfile at 15:00. +.IP "\fB-u \fIuser name\fR\fP" 10 +When daemonized, the process' user ID will be set to +\fIuser name\fR. +.IP "\fB-T \fIchroot path\fR\fP" 10 +Chroot directory to \fIchroot path\fR. +.IP "\fB-z\fP" 10 +Select log file pruning behavior. Omitting this switch results +in the default mode being used where the oldest log file in the logging +directory is pruned. Setting the \fB-z\fP switch changes the +behavior so that daemonlogger will prune the oldest file from its current +instantiation and leave files from older runs in the same logging directory +alone. +.SH "SEE ALSO" +.PP +tcpdump (8). +.SH "AUTHOR" +.PP +This manual page was written by Javier Fernandez-Sanguino Pen~a j...@debian.org for +the \fBDebian\fP system (and may be used by others). Permission is +granted to copy, distribute and/or modify this document under +the terms of the GNU General Public License, Version 2 or any +later version published by the Free Software Foundation. + +.PP +On Debian systems, the complete text of the GNU General Public +License can be found in /usr/share/common-licenses/GPL. + +.\" created by instant / docbook-to-man, Fri 31 Dec 2010, 16:54 diff -Nru daemonlogger-1.2.1.orig/debian/daemonlogger.manpages daemonlogger-1.2.1/debian/daemonlogger.manpages --- daemonlogger-1.2.1.orig/debian/daemonlogger.manpages 1970-01-01 01:00:00.000000000 +0100 +++ daemonlogger-1.2.1/debian/daemonlogger.manpages 2011-01-02 02:34:36.137783532 +0100 @@ -0,0 +1 @@ +debian/daemonlogger.8 diff -Nru daemonlogger-1.2.1.orig/debian/daemonlogger.sgml daemonlogger-1.2.1/debian/daemonlogger.sgml --- daemonlogger-1.2.1.orig/debian/daemonlogger.sgml 1970-01-01 01:00:00.000000000 +0100 +++ daemonlogger-1.2.1/debian/daemonlogger.sgml 2011-01-02 02:34:36.137783532 +0100 @@ -0,0 +1,395 @@ +<!doctype refentry PUBLIC "-//OASIS//DTD DocBook V4.1//EN" [ + +<!-- Process this file with docbook-to-man to generate an nroff manual + page: `docbook-to-man manpage.sgml > manpage.1'. You may view + the manual page with: `docbook-to-man manpage.sgml | nroff -man | + less'. A typical entry in a Makefile or Makefile.am is: + +manpage.1: manpage.sgml + docbook-to-man $< > $@ + + + The docbook-to-man binary is found in the docbook-to-man package. + Please remember that if you create the nroff version in one of the + debian/rules file targets (such as build), you will need to include + docbook-to-man in your Build-Depends control field. + + --> + + <!ENTITY dhfirstname "<firstname>Javier</firstname>"> + <!ENTITY dhsurname "<surname>Fernandez-Sanguino</surname>"> + <!-- Please adjust the date whenever revising the manpage. --> + <!ENTITY dhdate "<date>December 31, 2010</date>"> + <!-- SECTION should be 1-8, maybe w/ subsection other parameters are + allowed: see man(7), man(1). --> + <!ENTITY dhsection "<manvolnum>8</manvolnum>"> + <!ENTITY dhemail "<email>j...@debian.org</email>"> + <!ENTITY dhusername "Javier Fernandez-Sanguino Pen~a"> + <!ENTITY dhucpackage "<refentrytitle>DAEMONLOGGER</refentrytitle>"> + <!ENTITY dhprogram "daemonlogger"> + + <!ENTITY debian "<productname>Debian</productname>"> + <!ENTITY gnu "<acronym>GNU</acronym>"> + <!ENTITY gpl "&gnu; <acronym>GPL</acronym>"> +]> + +<refentry> + <refentryinfo> + <address> + &dhemail; + </address> + <author> + &dhfirstname; + &dhsurname; + </author> + <copyright> + <year>2010</year> + <holder>&dhusername;</holder> + </copyright> + &dhdate; + </refentryinfo> + <refmeta> + &dhucpackage; + + &dhsection; + </refmeta> + <refnamediv> + <refname>&dhprogram;</refname> + + <refpurpose>program capture packets from an interface and log or rewrite them</refpurpose> + </refnamediv> + <refsynopsisdiv> + <cmdsynopsis> + <command>&dhprogram;</command> + + <arg><option>-c <replaceable>count</replaceable></option></arg> + <arg><option>-d</option></arg> + <arg><option>-f <replaceable>bdf file</replaceable></option></arg> + <arg><option>-F</option></arg> + <arg><option>-g <replaceable>group name</replaceable></option></arg> + <arg><option>-i <replaceable>interface</replaceable></option></arg> + <arg><option>-l <replaceable>path</replaceable></option></arg> + <arg><option>-m <replaceable>count</replaceable></option></arg> + <arg><option>-m <replaceable>count</replaceable></option></arg> + <arg><option>-M <replaceable>pct</replaceable></option></arg> + <arg><option>-n <replaceable>name</replaceable></option></arg> + <arg><option>-o <replaceable>out interface</replaceable></option></arg> + <arg><option>-p <replaceable>pidfile</replaceable></option></arg> + <arg><option>-P <replaceable>pidpath</replaceable></option></arg> + <arg><option>-r</option></arg> + <arg><option>-R <replaceable>pcap file</replaceable></option></arg> + <arg><option>-s <replaceable>bytes</replaceable></option></arg> + <arg><option>-S <replaceable>snaplen</replaceable></option></arg> + <arg><option>-t <replaceable>time</replaceable></option></arg> + <arg><option>-u <replaceable>user name</replaceable></option></arg> + <arg><option>-T <replaceable>chroot path</replaceable></option></arg> + + <arg><replaceable>bdf filter</replaceable></option></arg> + + </cmdsynopsis> + </refsynopsisdiv> + + <refsect1> + <title>DESCRIPTION</title> + + <para>This manual page documents briefly the + <command>&dhprogram;</command>.</para> + + <para>This manual page was written for the &debian; distribution + because the original program does not have a manual page.</para> + + <para><command>&dhprogram;</command> is a simple packet logging and + software tapping program that can be run both in foreground or in + daemon mode.</para> + + <para><command>&dhprogram;</command> can be used in two different + (and mutually exclusive) ways:</para> + + <variablelist> + <varlistentry> + <term>Sniffing mode</term> + <listitem> + <para>In this mode, <command>&dhprogram;</command> will + read (sniff) packets from a network interace and spool them straight + to disk. It will automatically roll over the capture file when it + reaches a specific size. + </listitem> + </varlistentry> + + <varlistentry> + <term>Software tap</term> + <listitem> + <para>In this mode, <command>&dhprogram;</command> will + read packets from an input interface and rewrite them to a second + (output) interface, acting as a software tap. + </listitem> + </varlistentry> + </variablelist> + + </refsect1> + <refsect1> + <title>OPTIONS</title> + + <para>You can specify packet filter commands after the command line + switches just like in tcpdump or Snort. If no filter is defined + it will capture all packets coming to the interface.</para> + + <para>A summary of available options is included below.</para> + + <variablelist> + <varlistentry> + <term><option>-h</option> + </term> + <listitem> + <para>Show summary of options.</para> + </listitem> + </varlistentry> + + <varlistentry> + <term><option>-v</option> + </term> + <listitem> + <para>Show version of program.</para> + </listitem> + </varlistentry> + + <varlistentry> + <term><option>-c <replaceable>count</replaceable></option> + </term> + <listitem> + <para>Log <replaceable>count</replaceable> packets and exit.</para> + </listitem> + </varlistentry> + + <varlistentry> + <term><option>-d</option> </term> + <listitem> + <para>Daemonize at startup.</para> + </listitem> + </varlistentry> + + <varlistentry> + <term><option>-f <replaceable>bdf file</replaceable></option></term> + <listitem> + <para>Load the BPF filter to use from <replaceable>bdf file</replaceable>.</para> + </listitem> + </varlistentry> + + <varlistentry> + <term><option>-F</option></term> + <listitem> + <para>Flush the pcap buffer for each packet. As each packet is saved, +it will be written to the output file rather than being written only when the +output buffer fills.</para> + </listitem> + </varlistentry> + + <varlistentry> + <term><option>-g <replaceable>group name</replaceable></option></term> + <listitem> + <para>Set the group ID of the process running the program to <replaceable>group name</replaceable>.</para> + </listitem> + </varlistentry> + + <varlistentry> + <term><option>-i <replaceable>interface</replaceable></option></term> + <listitem> + <para>Grab packets from the interface <replaceable>interface</replaceable>.</para> + </listitem> + </varlistentry> + + <varlistentry> + <term><option>-l <replaceable>path</replaceable></option></term> + <listitem> + <para>Log all the pcap log files to directory <replaceable>path</replaceable>.</para> + </listitem> + </varlistentry> + + <varlistentry> + <term><option>-m <replaceable>count</replaceable></option></term> + <listitem> + <para>Generate <replaceable>count</replaceable> log files and exit. +If using Ringbufer mode then write <count> files and delete the oldest file in +the set when you exceed <count> log files written. The program will not exit +when in this mode.</para> + </listitem> + </varlistentry> + + <varlistentry> + <term><option>-M <replaceable>pct</replaceable></option></term> + <listitem> + <para> Used in concert with the <option>-r</option> ringbuffer switch +this option will write log files to the disk until it is at +<replaceable>pct</replaceable> utilization and then roll over and delete the +oldest log file. For example, "-M 90" would write files to the disk until it +is 90% utilized and then roll over and delete the oldest file in the +logging directory. If the <option>-s</option> "size" switch is not set then the +default log file size is 2GB.</para> + </listitem> + </varlistentry> + + <varlistentry> + <term><option>-n <replaceable>name</replaceable></option></term> + <listitem> + <para>Set output filename prefix to <replaceable>name</replaceable>. +The default is <file>daemonlogger.pcap</file>. +</para> + </listitem> + </varlistentry> + + <varlistentry> + <term><option>-o <replaceable>out interface</replaceable></option></term> + <listitem> + <para>Act as a software tap: disable logging and retransmit all data from +<replaceable>interface</replaceable> to <replaceable>out interface</replaceable>.</para> + </listitem> + </varlistentry> + + <varlistentry> + <term><option>-p <replaceable>pidfile</replaceable></option></term> + <listitem> + <para>When running in daemon mode, use <replaceable>pidfile</replaceable> +for the name of the PID file created. The default is <file>daemonlogger.pid</file>. +</para> + </listitem> + </varlistentry> + + <varlistentry> + <term><option>-P <replaceable>pidpath</replaceable></option> + </term> + <listitem> + <para>When running in daemon mode, use <replaceable>pidpath</replaceable> +as the directory where PID files will be created. The default is +<file>/var/run</file>.</para> + </listitem> + </varlistentry> + + + <varlistentry> + <term><option>-r</option></term> + <listitem> + <para>Activate ringbuffer mode.</para> + </listitem> + </varlistentry> + + <varlistentry> + <term><option>-R <replaceable>pcap file</replaceable></option> + </term> + <listitem> + <para>Read packets from <replaceable>pcap file</replaceable> instead + of using an input interface.</para> + </listitem> + </varlistentry> + + <varlistentry> + <term><option>-s <replaceable>bytes</replaceable></option></term> + <listitem> + <para>Rollover the log file every <replaceable>bytes</replaceable> +bytes. By default the rollover occurs every 2 GB. The parameter +<replaceable>bytes</replaceable> can be appended with "k" (for KiloBytes), "m" +(for MegaBytes), "g" (for Gigabytes) and "t" (for TeraBytes). +</para> + </listitem> + </varlistentry> + + <varlistentry> + <term><option>-S <replaceable>snaplen</replaceable></option> + </term> + <listitem> + <para>Capture <replaceable>snaplen</replaceable> bytes per packet. If not +defined, all the contents of the packets will be captured (which is equivalent +to setting <replaceable>snaplen</replaceable> to 65535 bytes.</para> + </listitem> + </varlistentry> + + <varlistentry> + <term><option>-t <replaceable>time</replaceable></option></term> + <listitem> + <para>Rollover the log file on specific time intervals. The time interval +can be appended with "m" (for minutes), "h" (for hours) or "d" (for days). If no interval selector is used then the +default rollover interval is in seconds. For example, "-t 60" rolls the log +file over every 60 seconds and "-t 2h" rolls the log file over every two hours +at the top of the hour. In the case of minute/hour/day-based rollovers, the +will round to the next highest hour. For example, if the program is told to +rollover every 2 hours and is started 38 minutes into the current hour it will +add 2 to the current hour and rollover as scheduled at the top of the hour at +<current hour> + 2. If the program was started at 13:38 it would roll over the +logfile at 15:00.</para> + </listitem> + </varlistentry> + + <varlistentry> + <term><option>-u <replaceable>user name</replaceable></option></term> + <listitem> + <para>When daemonized, the process' user ID will be set to +<replaceable>user name</replaceable>. </para> + </listitem> + </varlistentry> + + </variablelist> + + <varlistentry> + <term><option>-T <replaceable>chroot path</replaceable></option></term> + <listitem> + <para>Chroot directory to <replaceable>chroot path</replaceable>. </para> + </listitem> + </varlistentry> + + <varlistentry> + <term><option>-z</option></term> + <listitem> + <para>Select log file pruning behavior. Omitting this switch results +in the default mode being used where the oldest log file in the logging +directory is pruned. Setting the <option>-z</option> switch changes the +behavior so that &dhprogram; will prune the oldest file from its current +instantiation and leave files from older runs in the same logging directory +alone.</para> + </listitem> + </varlistentry> + + </variablelist> + + + + </refsect1> + + + <refsect1> + <title>SEE ALSO</title> + + <para>tcpdump (8).</para> + + </refsect1> + <refsect1> + <title>AUTHOR</title> + + <para>This manual page was written by &dhusername; &dhemail; for + the &debian; system (and may be used by others). Permission is + granted to copy, distribute and/or modify this document under + the terms of the &gnu; General Public License, Version 2 or any + later version published by the Free Software Foundation. + </para> + <para> + On Debian systems, the complete text of the GNU General Public + License can be found in /usr/share/common-licenses/GPL. + </para> + + </refsect1> +</refentry> + +<!-- Keep this comment at the end of the file +Local variables: +mode: sgml +sgml-omittag:t +sgml-shorttag:t +sgml-minimize-attributes:nil +sgml-always-quote-attributes:t +sgml-indent-step:2 +sgml-indent-data:t +sgml-parent-document:nil +sgml-default-dtd-file:nil +sgml-exposed-tags:nil +sgml-local-catalogs:nil +sgml-local-ecat-files:nil +End: +--> diff -Nru daemonlogger-1.2.1.orig/debian/rules daemonlogger-1.2.1/debian/rules --- daemonlogger-1.2.1.orig/debian/rules 2011-01-02 02:34:10.997786644 +0100 +++ daemonlogger-1.2.1/debian/rules 2011-01-02 02:35:10.910784996 +0100 @@ -13,6 +13,12 @@ dh_auto_clean rm -rf autom4te.cache rm -f config.sub config.guess configure config.log aclocal.m4 config.h.in Makefile.in + rm -f debian/daemonlogger.8 override_dh_install: dh_install + +override_dh_auto_build: + dh_auto_build + docbook-to-man debian/daemonlogger.sgml > debian/daemonlogger.8 +
diff -Nru daemonlogger-1.2.1.orig/debian/daemonlogger.8 daemonlogger-1.2.1/debian/daemonlogger.8 --- daemonlogger-1.2.1.orig/debian/daemonlogger.8 1970-01-01 01:00:00.000000000 +0100 +++ daemonlogger-1.2.1/debian/daemonlogger.8 2011-01-02 02:34:36.137783532 +0100 @@ -0,0 +1,134 @@ +.TH "DAEMONLOGGER" "8" +.SH "NAME" +daemonlogger \(em program capture packets from an interface and log or rewrite them +.SH "SYNOPSIS" +.PP +\fBdaemonlogger\fR [\fB-c \fIcount\fR\fP] [\fB-d\fP] [\fB-f \fIbdf file\fR\fP] [\fB-F\fP] [\fB-g \fIgroup name\fR\fP] [\fB-i \fIinterface\fR\fP] [\fB-l \fIpath\fR\fP] [\fB-m \fIcount\fR\fP] [\fB-m \fIcount\fR\fP] [\fB-M \fIpct\fR\fP] [\fB-n \fIname\fR\fP] [\fB-o \fIout interface\fR\fP] [\fB-p \fIpidfile\fR\fP] [\fB-P \fIpidpath\fR\fP] [\fB-r\fP] [\fB-R \fIpcap file\fR\fP] [\fB-s \fIbytes\fR\fP] [\fB-S \fIsnaplen\fR\fP] [\fB-t \fItime\fR\fP] [\fB-u \fIuser name\fR\fP] [\fB-T \fIchroot path\fR\fP] [\fIbdf filter\fR] +.SH "DESCRIPTION" +.PP +This manual page documents briefly the +\fBdaemonlogger\fR. +.PP +This manual page was written for the \fBDebian\fP distribution +because the original program does not have a manual page. +.PP +\fBdaemonlogger\fR is a simple packet logging and +software tapping program that can be run both in foreground or in +daemon mode. +.PP +\fBdaemonlogger\fR can be used in two different +(and mutually exclusive) ways: +.IP "Sniffing mode" 10 +In this mode, \fBdaemonlogger\fR will +read (sniff) packets from a network interace and spool them straight +to disk. It will automatically roll over the capture file when it +reaches a specific size. + +.IP "Software tap" 10 +In this mode, \fBdaemonlogger\fR will +read packets from an input interface and rewrite them to a second +(output) interface, acting as a software tap. + +.SH "OPTIONS" +.PP +You can specify packet filter commands after the command line +switches just like in tcpdump or Snort. If no filter is defined +it will capture all packets coming to the interface. +.PP +A summary of available options is included below. +.IP "\fB-h\fP " 10 +Show summary of options. +.IP "\fB-v\fP " 10 +Show version of program. +.IP "\fB-c \fIcount\fR\fP " 10 +Log \fIcount\fR packets and exit. +.IP "\fB-d\fP " 10 +Daemonize at startup. +.IP "\fB-f \fIbdf file\fR\fP" 10 +Load the BPF filter to use from \fIbdf file\fR. +.IP "\fB-F\fP" 10 +Flush the pcap buffer for each packet. As each packet is saved, +it will be written to the output file rather than being written only when the +output buffer fills. +.IP "\fB-g \fIgroup name\fR\fP" 10 +Set the group ID of the process running the program to \fIgroup name\fR. +.IP "\fB-i \fIinterface\fR\fP" 10 +Grab packets from the interface \fIinterface\fR. +.IP "\fB-l \fIpath\fR\fP" 10 +Log all the pcap log files to directory \fIpath\fR. +.IP "\fB-m \fIcount\fR\fP" 10 +Generate \fIcount\fR log files and exit. +If using Ringbufer mode then write files and delete the oldest file in +the set when you exceed log files written. The program will not exit +when in this mode. +.IP "\fB-M \fIpct\fR\fP" 10 +Used in concert with the \fB-r\fP ringbuffer switch +this option will write log files to the disk until it is at +\fIpct\fR utilization and then roll over and delete the +oldest log file. For example, "\-M 90" would write files to the disk until it +is 90% utilized and then roll over and delete the oldest file in the +logging directory. If the \fB-s\fP "size" switch is not set then the +default log file size is 2GB. +.IP "\fB-n \fIname\fR\fP" 10 +Set output filename prefix to \fIname\fR. +The default is daemonlogger.pcap. +.IP "\fB-o \fIout interface\fR\fP" 10 +Act as a software tap: disable logging and retransmit all data from +\fIinterface\fR to \fIout interface\fR. +.IP "\fB-p \fIpidfile\fR\fP" 10 +When running in daemon mode, use \fIpidfile\fR for the name of the PID file created. The default is daemonlogger.pid. +.IP "\fB-P \fIpidpath\fR\fP " 10 +When running in daemon mode, use \fIpidpath\fR as the directory where PID files will be created. The default is +/var/run. +.IP "\fB-r\fP" 10 +Activate ringbuffer mode. +.IP "\fB-R \fIpcap file\fR\fP " 10 +Read packets from \fIpcap file\fR instead +of using an input interface. +.IP "\fB-s \fIbytes\fR\fP" 10 +Rollover the log file every \fIbytes\fR bytes. By default the rollover occurs every 2 GB. The parameter +\fIbytes\fR can be appended with "k" (for KiloBytes), "m" +(for MegaBytes), "g" (for Gigabytes) and "t" (for TeraBytes). +.IP "\fB-S \fIsnaplen\fR\fP " 10 +Capture \fIsnaplen\fR bytes per packet. If not +defined, all the contents of the packets will be captured (which is equivalent +to setting \fIsnaplen\fR to 65535 bytes. +.IP "\fB-t \fItime\fR\fP" 10 +Rollover the log file on specific time intervals. The time interval +can be appended with "m" (for minutes), "h" (for hours) or "d" (for days). If no interval selector is used then the +default rollover interval is in seconds. For example, "\-t 60" rolls the log +file over every 60 seconds and "\-t 2h" rolls the log file over every two hours +at the top of the hour. In the case of minute/hour/day-based rollovers, the +will round to the next highest hour. For example, if the program is told to +rollover every 2 hours and is started 38 minutes into the current hour it will +add 2 to the current hour and rollover as scheduled at the top of the hour at ++ 2. If the program was started at 13:38 it would roll over the +logfile at 15:00. +.IP "\fB-u \fIuser name\fR\fP" 10 +When daemonized, the process' user ID will be set to +\fIuser name\fR. +.IP "\fB-T \fIchroot path\fR\fP" 10 +Chroot directory to \fIchroot path\fR. +.IP "\fB-z\fP" 10 +Select log file pruning behavior. Omitting this switch results +in the default mode being used where the oldest log file in the logging +directory is pruned. Setting the \fB-z\fP switch changes the +behavior so that daemonlogger will prune the oldest file from its current +instantiation and leave files from older runs in the same logging directory +alone. +.SH "SEE ALSO" +.PP +tcpdump (8). +.SH "AUTHOR" +.PP +This manual page was written by Javier Fernandez-Sanguino Pen~a j...@debian.org for +the \fBDebian\fP system (and may be used by others). Permission is +granted to copy, distribute and/or modify this document under +the terms of the GNU General Public License, Version 2 or any +later version published by the Free Software Foundation. + +.PP +On Debian systems, the complete text of the GNU General Public +License can be found in /usr/share/common-licenses/GPL. + +.\" created by instant / docbook-to-man, Fri 31 Dec 2010, 16:54 diff -Nru daemonlogger-1.2.1.orig/debian/daemonlogger.manpages daemonlogger-1.2.1/debian/daemonlogger.manpages --- daemonlogger-1.2.1.orig/debian/daemonlogger.manpages 1970-01-01 01:00:00.000000000 +0100 +++ daemonlogger-1.2.1/debian/daemonlogger.manpages 2011-01-02 02:34:36.137783532 +0100 @@ -0,0 +1 @@ +debian/daemonlogger.8 diff -Nru daemonlogger-1.2.1.orig/debian/daemonlogger.sgml daemonlogger-1.2.1/debian/daemonlogger.sgml --- daemonlogger-1.2.1.orig/debian/daemonlogger.sgml 1970-01-01 01:00:00.000000000 +0100 +++ daemonlogger-1.2.1/debian/daemonlogger.sgml 2011-01-02 02:34:36.137783532 +0100 @@ -0,0 +1,395 @@ +<!doctype refentry PUBLIC "-//OASIS//DTD DocBook V4.1//EN" [ + +<!-- Process this file with docbook-to-man to generate an nroff manual + page: `docbook-to-man manpage.sgml > manpage.1'. You may view + the manual page with: `docbook-to-man manpage.sgml | nroff -man | + less'. A typical entry in a Makefile or Makefile.am is: + +manpage.1: manpage.sgml + docbook-to-man $< > $@ + + + The docbook-to-man binary is found in the docbook-to-man package. + Please remember that if you create the nroff version in one of the + debian/rules file targets (such as build), you will need to include + docbook-to-man in your Build-Depends control field. + + --> + + <!ENTITY dhfirstname "<firstname>Javier</firstname>"> + <!ENTITY dhsurname "<surname>Fernandez-Sanguino</surname>"> + <!-- Please adjust the date whenever revising the manpage. --> + <!ENTITY dhdate "<date>December 31, 2010</date>"> + <!-- SECTION should be 1-8, maybe w/ subsection other parameters are + allowed: see man(7), man(1). --> + <!ENTITY dhsection "<manvolnum>8</manvolnum>"> + <!ENTITY dhemail "<email>j...@debian.org</email>"> + <!ENTITY dhusername "Javier Fernandez-Sanguino Pen~a"> + <!ENTITY dhucpackage "<refentrytitle>DAEMONLOGGER</refentrytitle>"> + <!ENTITY dhprogram "daemonlogger"> + + <!ENTITY debian "<productname>Debian</productname>"> + <!ENTITY gnu "<acronym>GNU</acronym>"> + <!ENTITY gpl "&gnu; <acronym>GPL</acronym>"> +]> + +<refentry> + <refentryinfo> + <address> + &dhemail; + </address> + <author> + &dhfirstname; + &dhsurname; + </author> + <copyright> + <year>2010</year> + <holder>&dhusername;</holder> + </copyright> + &dhdate; + </refentryinfo> + <refmeta> + &dhucpackage; + + &dhsection; + </refmeta> + <refnamediv> + <refname>&dhprogram;</refname> + + <refpurpose>program capture packets from an interface and log or rewrite them</refpurpose> + </refnamediv> + <refsynopsisdiv> + <cmdsynopsis> + <command>&dhprogram;</command> + + <arg><option>-c <replaceable>count</replaceable></option></arg> + <arg><option>-d</option></arg> + <arg><option>-f <replaceable>bdf file</replaceable></option></arg> + <arg><option>-F</option></arg> + <arg><option>-g <replaceable>group name</replaceable></option></arg> + <arg><option>-i <replaceable>interface</replaceable></option></arg> + <arg><option>-l <replaceable>path</replaceable></option></arg> + <arg><option>-m <replaceable>count</replaceable></option></arg> + <arg><option>-m <replaceable>count</replaceable></option></arg> + <arg><option>-M <replaceable>pct</replaceable></option></arg> + <arg><option>-n <replaceable>name</replaceable></option></arg> + <arg><option>-o <replaceable>out interface</replaceable></option></arg> + <arg><option>-p <replaceable>pidfile</replaceable></option></arg> + <arg><option>-P <replaceable>pidpath</replaceable></option></arg> + <arg><option>-r</option></arg> + <arg><option>-R <replaceable>pcap file</replaceable></option></arg> + <arg><option>-s <replaceable>bytes</replaceable></option></arg> + <arg><option>-S <replaceable>snaplen</replaceable></option></arg> + <arg><option>-t <replaceable>time</replaceable></option></arg> + <arg><option>-u <replaceable>user name</replaceable></option></arg> + <arg><option>-T <replaceable>chroot path</replaceable></option></arg> + + <arg><replaceable>bdf filter</replaceable></option></arg> + + </cmdsynopsis> + </refsynopsisdiv> + + <refsect1> + <title>DESCRIPTION</title> + + <para>This manual page documents briefly the + <command>&dhprogram;</command>.</para> + + <para>This manual page was written for the &debian; distribution + because the original program does not have a manual page.</para> + + <para><command>&dhprogram;</command> is a simple packet logging and + software tapping program that can be run both in foreground or in + daemon mode.</para> + + <para><command>&dhprogram;</command> can be used in two different + (and mutually exclusive) ways:</para> + + <variablelist> + <varlistentry> + <term>Sniffing mode</term> + <listitem> + <para>In this mode, <command>&dhprogram;</command> will + read (sniff) packets from a network interace and spool them straight + to disk. It will automatically roll over the capture file when it + reaches a specific size. + </listitem> + </varlistentry> + + <varlistentry> + <term>Software tap</term> + <listitem> + <para>In this mode, <command>&dhprogram;</command> will + read packets from an input interface and rewrite them to a second + (output) interface, acting as a software tap. + </listitem> + </varlistentry> + </variablelist> + + </refsect1> + <refsect1> + <title>OPTIONS</title> + + <para>You can specify packet filter commands after the command line + switches just like in tcpdump or Snort. If no filter is defined + it will capture all packets coming to the interface.</para> + + <para>A summary of available options is included below.</para> + + <variablelist> + <varlistentry> + <term><option>-h</option> + </term> + <listitem> + <para>Show summary of options.</para> + </listitem> + </varlistentry> + + <varlistentry> + <term><option>-v</option> + </term> + <listitem> + <para>Show version of program.</para> + </listitem> + </varlistentry> + + <varlistentry> + <term><option>-c <replaceable>count</replaceable></option> + </term> + <listitem> + <para>Log <replaceable>count</replaceable> packets and exit.</para> + </listitem> + </varlistentry> + + <varlistentry> + <term><option>-d</option> </term> + <listitem> + <para>Daemonize at startup.</para> + </listitem> + </varlistentry> + + <varlistentry> + <term><option>-f <replaceable>bdf file</replaceable></option></term> + <listitem> + <para>Load the BPF filter to use from <replaceable>bdf file</replaceable>.</para> + </listitem> + </varlistentry> + + <varlistentry> + <term><option>-F</option></term> + <listitem> + <para>Flush the pcap buffer for each packet. As each packet is saved, +it will be written to the output file rather than being written only when the +output buffer fills.</para> + </listitem> + </varlistentry> + + <varlistentry> + <term><option>-g <replaceable>group name</replaceable></option></term> + <listitem> + <para>Set the group ID of the process running the program to <replaceable>group name</replaceable>.</para> + </listitem> + </varlistentry> + + <varlistentry> + <term><option>-i <replaceable>interface</replaceable></option></term> + <listitem> + <para>Grab packets from the interface <replaceable>interface</replaceable>.</para> + </listitem> + </varlistentry> + + <varlistentry> + <term><option>-l <replaceable>path</replaceable></option></term> + <listitem> + <para>Log all the pcap log files to directory <replaceable>path</replaceable>.</para> + </listitem> + </varlistentry> + + <varlistentry> + <term><option>-m <replaceable>count</replaceable></option></term> + <listitem> + <para>Generate <replaceable>count</replaceable> log files and exit. +If using Ringbufer mode then write <count> files and delete the oldest file in +the set when you exceed <count> log files written. The program will not exit +when in this mode.</para> + </listitem> + </varlistentry> + + <varlistentry> + <term><option>-M <replaceable>pct</replaceable></option></term> + <listitem> + <para> Used in concert with the <option>-r</option> ringbuffer switch +this option will write log files to the disk until it is at +<replaceable>pct</replaceable> utilization and then roll over and delete the +oldest log file. For example, "-M 90" would write files to the disk until it +is 90% utilized and then roll over and delete the oldest file in the +logging directory. If the <option>-s</option> "size" switch is not set then the +default log file size is 2GB.</para> + </listitem> + </varlistentry> + + <varlistentry> + <term><option>-n <replaceable>name</replaceable></option></term> + <listitem> + <para>Set output filename prefix to <replaceable>name</replaceable>. +The default is <file>daemonlogger.pcap</file>. +</para> + </listitem> + </varlistentry> + + <varlistentry> + <term><option>-o <replaceable>out interface</replaceable></option></term> + <listitem> + <para>Act as a software tap: disable logging and retransmit all data from +<replaceable>interface</replaceable> to <replaceable>out interface</replaceable>.</para> + </listitem> + </varlistentry> + + <varlistentry> + <term><option>-p <replaceable>pidfile</replaceable></option></term> + <listitem> + <para>When running in daemon mode, use <replaceable>pidfile</replaceable> +for the name of the PID file created. The default is <file>daemonlogger.pid</file>. +</para> + </listitem> + </varlistentry> + + <varlistentry> + <term><option>-P <replaceable>pidpath</replaceable></option> + </term> + <listitem> + <para>When running in daemon mode, use <replaceable>pidpath</replaceable> +as the directory where PID files will be created. The default is +<file>/var/run</file>.</para> + </listitem> + </varlistentry> + + + <varlistentry> + <term><option>-r</option></term> + <listitem> + <para>Activate ringbuffer mode.</para> + </listitem> + </varlistentry> + + <varlistentry> + <term><option>-R <replaceable>pcap file</replaceable></option> + </term> + <listitem> + <para>Read packets from <replaceable>pcap file</replaceable> instead + of using an input interface.</para> + </listitem> + </varlistentry> + + <varlistentry> + <term><option>-s <replaceable>bytes</replaceable></option></term> + <listitem> + <para>Rollover the log file every <replaceable>bytes</replaceable> +bytes. By default the rollover occurs every 2 GB. The parameter +<replaceable>bytes</replaceable> can be appended with "k" (for KiloBytes), "m" +(for MegaBytes), "g" (for Gigabytes) and "t" (for TeraBytes). +</para> + </listitem> + </varlistentry> + + <varlistentry> + <term><option>-S <replaceable>snaplen</replaceable></option> + </term> + <listitem> + <para>Capture <replaceable>snaplen</replaceable> bytes per packet. If not +defined, all the contents of the packets will be captured (which is equivalent +to setting <replaceable>snaplen</replaceable> to 65535 bytes.</para> + </listitem> + </varlistentry> + + <varlistentry> + <term><option>-t <replaceable>time</replaceable></option></term> + <listitem> + <para>Rollover the log file on specific time intervals. The time interval +can be appended with "m" (for minutes), "h" (for hours) or "d" (for days). If no interval selector is used then the +default rollover interval is in seconds. For example, "-t 60" rolls the log +file over every 60 seconds and "-t 2h" rolls the log file over every two hours +at the top of the hour. In the case of minute/hour/day-based rollovers, the +will round to the next highest hour. For example, if the program is told to +rollover every 2 hours and is started 38 minutes into the current hour it will +add 2 to the current hour and rollover as scheduled at the top of the hour at +<current hour> + 2. If the program was started at 13:38 it would roll over the +logfile at 15:00.</para> + </listitem> + </varlistentry> + + <varlistentry> + <term><option>-u <replaceable>user name</replaceable></option></term> + <listitem> + <para>When daemonized, the process' user ID will be set to +<replaceable>user name</replaceable>. </para> + </listitem> + </varlistentry> + + </variablelist> + + <varlistentry> + <term><option>-T <replaceable>chroot path</replaceable></option></term> + <listitem> + <para>Chroot directory to <replaceable>chroot path</replaceable>. </para> + </listitem> + </varlistentry> + + <varlistentry> + <term><option>-z</option></term> + <listitem> + <para>Select log file pruning behavior. Omitting this switch results +in the default mode being used where the oldest log file in the logging +directory is pruned. Setting the <option>-z</option> switch changes the +behavior so that &dhprogram; will prune the oldest file from its current +instantiation and leave files from older runs in the same logging directory +alone.</para> + </listitem> + </varlistentry> + + </variablelist> + + + + </refsect1> + + + <refsect1> + <title>SEE ALSO</title> + + <para>tcpdump (8).</para> + + </refsect1> + <refsect1> + <title>AUTHOR</title> + + <para>This manual page was written by &dhusername; &dhemail; for + the &debian; system (and may be used by others). Permission is + granted to copy, distribute and/or modify this document under + the terms of the &gnu; General Public License, Version 2 or any + later version published by the Free Software Foundation. + </para> + <para> + On Debian systems, the complete text of the GNU General Public + License can be found in /usr/share/common-licenses/GPL. + </para> + + </refsect1> +</refentry> + +<!-- Keep this comment at the end of the file +Local variables: +mode: sgml +sgml-omittag:t +sgml-shorttag:t +sgml-minimize-attributes:nil +sgml-always-quote-attributes:t +sgml-indent-step:2 +sgml-indent-data:t +sgml-parent-document:nil +sgml-default-dtd-file:nil +sgml-exposed-tags:nil +sgml-local-catalogs:nil +sgml-local-ecat-files:nil +End: +--> diff -Nru daemonlogger-1.2.1.orig/debian/rules daemonlogger-1.2.1/debian/rules --- daemonlogger-1.2.1.orig/debian/rules 2011-01-02 02:34:10.997786644 +0100 +++ daemonlogger-1.2.1/debian/rules 2011-01-02 02:35:10.910784996 +0100 @@ -13,6 +13,12 @@ dh_auto_clean rm -rf autom4te.cache rm -f config.sub config.guess configure config.log aclocal.m4 config.h.in Makefile.in + rm -f debian/daemonlogger.8 override_dh_install: dh_install + +override_dh_auto_build: + dh_auto_build + docbook-to-man debian/daemonlogger.sgml > debian/daemonlogger.8 +
signature.asc
Description: Digital signature
