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