1
Index: darkstat-3.0.708/Makefile.in
2
===================================================================
3
--- darkstat-3.0.708.orig/Makefile.in 2008-06-04 23:41:39.000000000 -0600
4
+++ darkstat-3.0.708/Makefile.in 2008-06-04 23:41:44.000000000 -0600
7
$(INSTALL) -d $(DESTDIR)$(sbindir)
8
$(INSTALL) -m 555 darkstat $(DESTDIR)$(sbindir)
9
- $(INSTALL) -d $(DESTDIR)$(mandir)/man1
10
- $(INSTALL) -m 444 darkstat.1 $(DESTDIR)$(mandir)/man1
12
# Automatically generated dependencies
13
acct.o: acct.c darkstat.h config.h acct.h decode.h conv.h daylog.h \
14
Index: darkstat-3.0.708/darkstat.1
15
===================================================================
16
--- darkstat-3.0.708.orig/darkstat.1 2008-06-04 23:41:39.000000000 -0600
17
+++ darkstat-3.0.708/darkstat.1 2008-06-04 23:42:35.000000000 -0600
19
.\" You may use, modify and redistribute this file under the terms of the
20
.\" GNU General Public License version 2. (see COPYING.GPL)
22
-.TH darkstat 1 "May 2008" darkstat "User Manuals"
24
-darkstat v3 \- network statistics gatherer
25
+.TH "darkstat" "8" "May 2008" darkstat "User Manuals"
27
+darkstat \- network statistics gatherer
56
-.BI \-l " network/netmask"
57
+.BI -l " network/netmask"
59
-.BI \-\-chroot " dir"
62
-.BI \-\-user " username"
63
+.BI --user " username"
65
-.BI \-\-daylog " filename"
66
+.BI --daylog " filename"
68
-.BI \-\-import " filename"
69
+.BI --import " filename"
71
-.BI \-\-export " filename"
72
+.BI --export " filename"
74
-.BI \-\-pidfile " filename"
75
+.BI --pidfile " filename"
77
-.BI \-\-hosts\-max " count"
78
+.BI --hosts-max " count"
80
-.BI \-\-hosts\-keep " count"
81
+.BI --hosts-keep " count"
83
-.BI \-\-ports\-max " count"
84
+.BI --ports-max " count"
86
-.BI \-\-ports\-keep " count"
87
+.BI --ports-keep " count"
89
-.BI \-\-highest\-port " port"
90
+.BI --highest-port " port"
100
Capture traffic on the specified network interface.
101
This is the only mandatory commandline argument.
106
Instead of capturing live traffic, read it from a
109
This is only useful for development and benchmarking.
116
arguments are mutually exclusive.
121
Debugging mode: do not detach from the controlling terminal,
122
stay in the foreground instead.
127
Do not use promiscuous mode to capture.
128
Note that an interface may already be in promiscuous mode.
129
If this is a problem, use an appropriate
136
Do not resolve IPs to host names.
141
Bind the web interface to the specified port.
147
Bind the web interface to the specified address.
148
The default is to listen on all interfaces.
153
Use the specified filter expression when capturing traffic.
154
The filter syntax is beyond the scope of this manual page;
160
-.BI \-l " network/netmask"
161
+.BI -l " network/netmask"
162
Define a "local network" according to the network and netmask addresses.
163
All traffic entering or leaving this network will be graphed, as opposed
164
to the default behaviour of only graphing traffic to and from the local
169
-.BI \-\-chroot " dir"
171
Force \fIdarkstat\fR to \fBchroot()\fR into the specified directory.
172
Without this argument, a default directory will be used, which is
173
determined at build time.
174
@@ -139,14 +139,14 @@
175
For security reasons, this directory should be empty, and the user that
176
\fIdarkstat\fR is running as should not have write access to it.
178
-However, if you wish to use \fB\-\-daylog\fR or \fB\-\-export\fR,
179
+However, if you wish to use \fB--daylog\fR or \fB--export\fR,
180
\fIdarkstat\fR will need write access to the chroot.
181
If you are uncomfortable with the security implications, don't
182
use any functionality that requires write access.
186
-.BI \-\-user " username"
187
+.BI --user " username"
188
Force \fIdarkstat\fR to drop privileges to the \fBuid\fR and \fBgid\fR of
190
Without this argument, a default value will be used, which is set at
191
@@ -158,15 +158,15 @@
195
-.BI \-\-daylog " filename"
196
+.BI --daylog " filename"
198
Log daily traffic statistics into the named file, relative to the
200
-If you wish to use \fB\-\-daylog\fR, you must first specify a
201
-\fB\-\-chroot\fR directory, and it must be writeable by the
202
+If you wish to use \fB--daylog\fR, you must first specify a
203
+\fB--chroot\fR directory, and it must be writeable by the
205
A writeable chroot has security implications; if you are uncomfortable
206
-with this, do not use the \fB\-\-daylog\fR functionality.
207
+with this, do not use the \fB--daylog\fR functionality.
209
If the daylog argument is not specified, no logging is performed.
211
@@ -179,26 +179,26 @@
215
-.BI \-\-import " filename"
216
+.BI --import " filename"
217
Upon starting, import a \fIdarkstat\fR database from the named file,
218
relative to the chroot directory.
219
-If you wish to use \fB\-\-import\fR, you must first specify a
220
-\fB\-\-chroot\fR directory.
221
+If you wish to use \fB--import\fR, you must first specify a
222
+\fB--chroot\fR directory.
223
If the import is unsuccessful, \fIdarkstat\fR will start with an empty
227
-.BI \-\-export " filename"
228
+.BI --export " filename"
229
On shutdown, and upon receiving SIGUSR1, export the in-memory database
230
to the named file, relative to the chroot directory.
231
-If you wish to use \fB\-\-export\fR, you must first specify a
232
-\fB\-\-chroot\fR directory, and it must be writeable by the
233
+If you wish to use \fB--export\fR, you must first specify a
234
+\fB--chroot\fR directory, and it must be writeable by the
236
A writeable chroot has security implications - if you are uncomfortable
237
-with this, do not use the \fB\-\-export\fR functionality.
238
+with this, do not use the \fB--export\fR functionality.
241
-.BI \-\-pidfile " filename"
242
+.BI --pidfile " filename"
244
Creates a file containing the process ID of \fIdarkstat\fR.
245
This file will be unlinked upon clean shutdown.
248
For example, start \fIdarkstat\fR with:
250
-darkstat -i fxp0 --chroot /var/run/darkstat --pidfile darkstat.pid
251
+darkstat \-i fxp0 \-\-chroot /var/run/darkstat \-\-pidfile darkstat.pid
255
@@ -219,31 +219,31 @@
259
-.BI \-\-hosts\-max " count"
260
+.BI --hosts-max " count"
261
The maximum number of hosts that will be kept in the hosts table.
262
This is used to limit how much accounting data will be kept in memory.
265
-.BI \-\-hosts\-keep " count"
266
+.BI --hosts-keep " count"
267
When the hosts table hits
270
and traffic is seen from a new host, we clean out the hosts table,
274
number of hosts, sorted by total traffic.
277
-.BI \-\-ports\-max " count"
278
+.BI --ports-max " count"
279
The maximum number of ports that will be tracked for each host.
280
This is used to limit how much accounting data will be kept in memory.
283
-.BI \-\-ports\-keep " count"
284
+.BI --ports-keep " count"
285
When a ports table fills up, this many ports are kept and the rest are
289
-.BI \-\-highest\-port " port"
290
+.BI --highest-port " port"
291
Ports that are numerically higher than this will not appear in the
292
per-host ports tables, although their traffic will still be accounted
294
@@ -256,30 +256,30 @@
302
We want to account for traffic on the Internet-facing interface,
303
but only serve web pages to our private local network where we have the
304
IP address 192.168.0.1:
306
-darkstat -i fxp0 -b 192.168.0.1
307
+darkstat \-i fxp0 \-b 192.168.0.1
310
We want to serve web pages on the standard HTTP port:
312
-darkstat -i fxp0 -p 80
313
+darkstat \-i fxp0 \-p 80
316
We are on Optus (cable) and don't want to account for the constant ARP
317
traffic we are receiving:
319
-darkstat -i fxp0 -f "not arp"
320
+darkstat \-i fxp0 \-f "not arp"
323
We only want to account for SSH traffic:
325
-darkstat -i fxp0 -f "port 22"
326
+darkstat \-i fxp0 \-f "port 22"
329
(For a full reference on filter syntax, refer to the
331
traffic entering and leaving the local network, not just the gateway
332
server (which is running \fIdarkstat\fR):
334
-darkstat -i fxp0 -l 192.168.1.0/255.255.255.0
335
+darkstat \-i fxp0 \-l 192.168.1.0/255.255.255.0
338
If you are using PPPoE (for example, on ADSL), and sniffing on
339
@@ -304,13 +304,13 @@
340
interface that your PPPoE software provides.
346
Or, on \fIOpenBSD\fR or \fINetBSD\fR, sniff on the
357
Sending the SIGUSR1 signal will cause \fIdarkstat\fR to empty out its
359
-If an \fB\-\-export\fR file was set, it will first save the database to
360
+If an \fB--export\fR file was set, it will first save the database to