1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
|
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
<TITLE>dblist.8</TITLE>
<META http-equiv="Content-Style-Type" content="text/css">
<STYLE type="text/css">
BODY {background-color:white; color:black}
</STYLE>
</HEAD>
<BODY>
<PRE>
<!-- Manpage converted by man2html 3.0.1 -->
dblist(DCC) LOCAL dblist(DCC)
</PRE>
<H2><A NAME="NAME">NAME</A></H2><PRE>
<B>dblist</B> -- Database List Distributed Checksum Clearinghouse
</PRE>
<H2><A NAME="SYNOPSIS">SYNOPSIS</A></H2><PRE>
<B>dblist</B> [<B>-vVHD</B>] [<B>-G</B> <I>on</I> | <I>off</I>] [<B>-h</B> <I>homedir</I>] [<B>-C</B> <I>'type</I> <I>h1</I> <I>h2</I> <I>h3</I> <I>h4'</I>]
[<B>-I</B> <I>server-ID</I>] [<B>-A</B> <I>dbaddr</I>] [<B>-L</B> <I>pathlen</I>] [<B>-P</B> <I>pages</I>] [<B>-T</B> <I>timestamp</I>]
[<I>file1</I> <I>file2</I> <I>...</I>]
</PRE>
<H2><A NAME="DESCRIPTION">DESCRIPTION</A></H2><PRE>
<B>Dblist</B> lists the contents of a DCC database as it does some consistency
checking.
<A NAME="OPTION-v"><B>-v</B></A> lists more of the database. Additional information is produced with
additional <B>-v</B> arguments.
<A NAME="OPTION-V"><B>-V</B></A> displays the version of the DCC database lister.
<A NAME="OPTION-H"><B>-H</B></A> turns off the listing of the hash table as well as the analysis of
the hash table. Determining the worst case and average lengths of
chains in the hash table can take a long time for a large database
on a small computer.
<A NAME="OPTION-D"><B>-D</B></A> turns off the listing of the data or checksum records.
<A NAME="OPTION-G"><B>-G</B></A> <I>on</I>
lists a greylist database.
<A NAME="OPTION-h"><B>-h</B></A> <I>homedir</I>
overrides the default DCC home directory, which is often /var/dcc.
<A NAME="OPTION-C"><B>-C</B></A> <I>'type</I> <I>h1</I> <I>h2</I> <I>h3</I> <I>h4'</I>
limits the listing to records containing that checksum or one of the
other checksums specified with <B>-C</B> or server-IDs specified with <B>-I.</B>
As many as 16 checksums can be specified.
<A NAME="OPTION-I"><B>-I</B></A> <I>server-ID</I>
limits the listing to records with that server-ID or one of the
other server-IDs specified with <B>-I</B> or checksums specified with <B>-C</B>.
As many as 16 server-IDs can be specified.
<A NAME="OPTION-A"><B>-A</B></A> <I>dbaddr</I>
excludes database records before <I>dbaddr</I>.
<A NAME="OPTION-L"><B>-L</B></A> <I>pathlen</I>
excludes records with path lengths shorter than <I>pathlen</I>.
<A NAME="OPTION-P"><B>-P</B></A> <I>pages</I>
ignores all but the last <I>pages</I> of the database.
<A NAME="OPTION-T"><B>-T</B></A> <I>timetamp</I>
excludes records with other timestamps. As many as 16 timestamps
can be specified.
<I>file1</I> <I>file2</I> <I>...</I>
are names of databases to be listed. The default is <I>dcc</I><B>_</B><I>db</I> and its
companion, <I>dcc</I><B>_</B><I>db.hash</I> in the DCC home directory.
By default, the sizes of the main file and the hash table as well as how
much they contain and values related to the performance of the hash are
displayed.
With a single <B>-v</B>, most of the mail database file and the contents of mem-
ory mapped server flooding positions in the <I>flod.map</I> file are listed.
The listing starts with the serial number of the database file which is
when old entries were last removed from it by <B><A HREF="dbclean.html">dbclean(8)</A></B> That is followed
by similar lines showing the oldest timestamp of checksums not expired by
dbclean and of mail that is not "spam."
The flooding positions from the <I>flod.map</I> file are record offsets or
addresses in the main database file.
A typical record in the main database file looks like:
02/07/02 20:25:12.497032 5 auth 1601 2fe5b94
path: 103<-101<-1601
Body 6 e2d3f96a c65aea01 3fece361 edff9ecf 2f21364 772d2
Fuz1 many 6ff56fe8 ffc312d7 a5fe8f13 12a537ae 2f21364 200a9
Fuz2 many fac882b8 03eea34f bd792c40 2fe6fd54 2f21364 72816
That example was received by a DCC server with server-ID <I>1601</I> at about
8:25 GMT on the evening of February 7, 2000. The report was about a mail
message set to <I>5</I> addressees. The report was from a client that presented
a client-ID and matching password that the server recognized or authenti-
cated. The report was then sent or `flooded' to the server with server-
ID <I>101</I> which in turn sent it to a server with server-ID <I>103</I>. That server
sent it to the local DCC server. The record is at the address <I>0x2fe5b94</I>
in the database. The record contains 3 checksums. The simple checksum
of the body of the message was <I>e2d3f96a</I> <I>c65aea01</I> <I>3fece361</I> <I>edff9ecf</I> The
total number of recipients of messages with this body checksum known in
the database is <I>6</I>, which implies this checksum had been previously
reported with a target count of 1. The previous report in the database
of a message with this body checksum is at <I>0x2f21364</I>. The hash table
entry for this body checksum is at <I>0x772d2</I>. This report included two
fuzzy checksums. Both have been previously reported as having been sent
to <I>many</I> targets.
An asterisk (*) before the name of the checksum would indicate that a
later record in the database makes this checksum redundant. A report of
<I>many</I> addressees makes all preceding reports redundant.
The string <I>trimmed</I> after the server-ID marks older reports that have had
uninteresting checksums removed. The string <I>compressed</I> after the server-
ID would indicate that this older report has been trimmed and compressed
with older reports.
With two <B>-v</B> arguments, records added to the database by <B><A HREF="dbclean.html">dbclean(8)</A></B> from
the server whitelist are also displayed.
Three <B>-v</B> arguments cause the hash table to be displayed. Three typical
hash table entries look like:
19b8: 19ee 19b7
19b9: 19c0 0 90120 Fuz1
19ba: 0 0 1b72300 Fuz1
The entry in slot number <I>0x19b8</I> is unused or free. Slot number <I>0x19b9</I> is
the start of a chain of collisions or entries with the same hash value of
0x19b9. The next slot in this chain is at <I>0x19c0</I>. The corresponding
<I>Fuz1</I>
checksum is at <I>0x9012</I> in the database. The third slot at <I>0x19ba</I> is also
that of a <I>Fuz1</I> checksum, but it is not part of a hash chain and its data-
base record is at <I>0x1b72300</I>.
</PRE>
<H2><A NAME="FILES">FILES</A></H2><PRE>
<A NAME="FILE-/var/dcc">/var/dcc</A> is the DCC home directory containing data and control files.
<A NAME="FILE-dcc_db">dcc_db</A> grey_dcc_db
main file of checksums.
<A NAME="FILE-dcc_db.hash">dcc_db.hash</A> grey_dcc_db.hash
database hash table.
<A NAME="FILE-flod.map">flod.map</A> grey_flod.map
memory mapped flooding positions.
</PRE>
<H2><A NAME="SEE-ALSO">SEE ALSO</A></H2><PRE>
<B><A HREF="cdcc.html">cdcc(8)</A></B>, <B><A HREF="dcc.html">dcc(8)</A></B>, <B><A HREF="dbclean.html">dbclean(8)</A></B>, <B><A HREF="dccd.html">dccd(8)</A></B>, <B><A HREF="dccifd.html">dccifd(8)</A></B>, <B><A HREF="dccm.html">dccm(8)</A></B>, <B><A HREF="dccproc.html">dccproc(8)</A></B>.
</PRE>
<H2><A NAME="HISTORY">HISTORY</A></H2><PRE>
<A NAME="FILE-Implementation">Implementation</A> of <B>dblist</B> was started at <A HREF="http://www.rhyolite.com/">Rhyolite Software</A> in 2000. This
<A NAME="FILE-describes">describes</A> version 1.2.74.
FreeBSD 4.9 March 20, 2005 FreeBSD 4.9
</PRE>
<HR>
<ADDRESS>
Man(1) output converted with
<a href="http://www.oac.uci.edu/indiv/ehood/man2html.html">man2html</a>
modified for the DCC $Date 2001/04/29 03:22:18 $
</ADDRESS>
</BODY>
</HTML>
|
