|
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>dbclean.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="dbclean.html">dbclean(8)</A></B> Distributed Checksum Clearinghouse <B><A HREF="dbclean.html">dbclean(8)</A></B> |
|
|
17 |
|
|
18 |
|
|
19 </PRE> |
|
|
20 <H2><A NAME="NAME">NAME</A></H2><PRE> |
|
|
21 <B>dbclean</B> -- Clean Distributed Checksum Clearinghouse Database |
|
|
22 |
|
|
23 |
|
|
24 </PRE> |
|
|
25 <H2><A NAME="SYNOPSIS">SYNOPSIS</A></H2><PRE> |
|
|
26 <B>dbclean</B> [<B>-dfFNPSVq</B>] [<B>-i</B> <I>id</I>] [<B>-a</B> [<I>server-addr</I>][<I>,port</I>]] [<B>-h</B> <I>homedir</I>] |
|
|
27 [<B>-G</B> <I>on</I>] [<B>-R</B> <I>mode</I>] [<B>-s</B> <I>hash-size</I>] [<B>-e</B> <I>seconds</I>] [<B>-E</B> <I>spamsecs</I>] |
|
|
28 [<B>-L</B> <I>ltype,facility.level</I>] |
|
|
29 |
|
|
30 |
|
|
31 </PRE> |
|
|
32 <H2><A NAME="DESCRIPTION">DESCRIPTION</A></H2><PRE> |
|
|
33 <B>Dbclean</B> creates empty, rebuilds corrupted, and deletes or expires old |
|
|
34 reports of checksums from DCC databases. It should be installed where it |
|
|
35 will be found with the path given the DCC server daemon when the daemon |
|
|
36 needs to expand the hash table. See <B><A HREF="dccd.html">dccd(8)</A></B>. It should also be run by |
|
|
37 <B>cron(8)</B> approximately daily. |
|
|
38 |
|
|
39 If the hash table in the database has been damaged, <B>dbclean</B> tries to |
|
|
40 repair the database. |
|
|
41 |
|
|
42 The contents of the <I>whitelist</I> file are built into the DCC server's data- |
|
|
43 base. Changes to the whitelist are not effective until dbclean is run to |
|
|
44 expire reports. White or blacklists can also be used by DCC clients, and |
|
|
45 generally work better there. |
|
|
46 |
|
|
47 <A NAME="OPTIONS"><B>OPTIONS</B></A> |
|
|
48 The following options are available: |
|
|
49 |
|
|
50 <A NAME="OPTION-d"><B>-d</B></A> enables debugging output. Additional <B>-d</B> options increase the number |
|
|
51 of messages. |
|
|
52 |
|
|
53 <A NAME="OPTION-F"><B>-F</B></A> uses write() instead of mmap() in some cases to modify the DCC data- |
|
|
54 base. This works better on some versions of Solaris provided the |
|
|
55 entire DCC database fits in RAM and provided the file system has not |
|
|
56 been tuned for the large, random accesses of a DCC database. It is |
|
|
57 the default on Solaris. |
|
|
58 |
|
|
59 <A NAME="OPTION-f"><B>-f</B></A> turns off <B>-F</B>. |
|
|
60 |
|
|
61 <A NAME="OPTION-N"><B>-N</B></A> creates a new, empty database. There must not be an existing data- |
|
|
62 base and the DCC server, <B><A HREF="dccd.html">dccd(8)</A></B>, must not be running. |
|
|
63 |
|
|
64 <A NAME="OPTION-P"><B>-P</B></A> expires old checksums from a database using the <B>-e -and -E</B> values |
|
|
65 from the preceding use of <B>dbclean</B>. <B>-P</B> cannot be used with <B>-e</B> or <B>-E</B>. |
|
|
66 Note also that using <B>-P</B> differs from not using <B>-e</B> or <B>-E</B>, because in |
|
|
67 the absence of all four, their default values are used. |
|
|
68 |
|
|
69 <A NAME="OPTION-S"><B>-S</B></A> says that the DCC server, <B><A HREF="dccd.html">dccd(8)</A></B>, is not running and so <B>dbclean</B> |
|
|
70 should run stand-alone and not try to tell the DCC server about |
|
|
71 changes to the database. <B>-i</B> is not needed when <B>-S</B> is present. |
|
|
72 |
|
|
73 <A NAME="OPTION-V"><B>-V</B></A> displays the version of the DCC database cleaner. |
|
|
74 |
|
|
75 <A NAME="OPTION-q"><B>-q</B></A> quiets the announcement of results at the end. |
|
|
76 |
|
|
77 <A NAME="OPTION-i"><B>-i</B></A> <I>id</I> |
|
|
78 specifies the DCC ID recognized by the local DCC server as its own. |
|
|
79 This ID allows the DCC server to recognize commands from <B>dbclean</B> to |
|
|
80 stop using the database while it is being cleaned. |
|
|
81 |
|
|
82 <A NAME="OPTION-a"><B>-a</B></A> [<I>server-addr</I>][<I>,port</I>] |
|
|
83 is commonly used to specify a UDP port or IP address of the local |
|
|
84 server other than the default. |
|
|
85 |
|
|
86 <A NAME="OPTION-h"><B>-h</B></A> <I>homedir</I> |
|
|
87 overrides the default DCC home directory, <I>@prefix@</I>. |
|
|
88 |
|
|
89 <A NAME="OPTION-G"><B>-G</B></A> <I>on</I> |
|
|
90 cleans a greylist database. |
|
|
91 |
|
|
92 <A NAME="OPTION-R"><B>-R</B></A> <I>mode</I> |
|
|
93 repairs a database or does a quick cleaning. <I>Mode</I> must be one of |
|
|
94 the following: |
|
|
95 <I>bad</I> to repair a broken database. |
|
|
96 <I>quick</I> for a quick, superficial cleaning during the day. |
|
|
97 <I>hash</I> to rebuild a hash not sent to disk before the system was |
|
|
98 recently restarted. |
|
|
99 <I>cron</I> for the nightly cleaning by the <B>cron(8)</B> job |
|
|
100 <I>@libexecdir@/cron-dccd</I> |
|
|
101 <I>del</I> to finish processing a delete command received by <B><A HREF="dccd.html">dccd(8)</A></B>. |
|
|
102 |
|
|
103 <A NAME="OPTION-s"><B>-s</B></A> <I>hash-size</I> |
|
|
104 specifies a size for the hash table. By default the hash table is |
|
|
105 rebuilt to be approximately 80% full based on an estimate of the |
|
|
106 number of distinct checksums in the main file. |
|
|
107 |
|
|
108 <A NAME="OPTION-e"><B>-e</B></A> <I>seconds</I> |
|
|
109 specifies that reports older than <I>seconds</I> and with totals below 10 |
|
|
110 targets should be deleted. Reports older than <I>seconds</I> of checksums |
|
|
111 that have been reported more recently are summarized in the data- |
|
|
112 base. The default value is 1DAY or the value of <B>-E</B>, whichever is |
|
|
113 smaller. The 1 day default is reduced if the system does not appear |
|
|
114 to have enough RAM to hold the database. The minimum is 1 hour. |
|
|
115 <I>Seconds</I> can also be <I>NEVER</I> or a number of hours, days, or weeks fol- |
|
|
116 lowed by <I>HOURS</I>, <I>H</I>, <I>DAYS</I>, <I>D</I>, <I>WEEKS</I> or <I>W</I>. |
|
|
117 |
|
|
118 DCC servers that are not very busy and are isolated or do not |
|
|
119 receive "floods" of checksums from busy servers should use longer |
|
|
120 values to increase their chances of recognizing bulk mail. |
|
|
121 |
|
|
122 <A NAME="OPTION-E"><B>-E</B></A> <I>spamsecs</I> |
|
|
123 changes the expiration of checksums with more than 10 targets from |
|
|
124 the default of 30DAYS or the explicit value of <B>-e</B>, whichever is |
|
|
125 larger. The default is reduced if the system does not have enough |
|
|
126 RAM to hold the database. <I>Spamsecs</I> can also be <I>NEVER</I> or a number of |
|
|
127 hours, days, or weeks followed by <I>HOURS</I>, <I>H</I>, <I>DAYS</I>, <I>D</I>, <I>WEEKS</I> or <I>W</I>. |
|
|
128 |
|
|
129 <A NAME="OPTION-L"><B>-L</B></A> <I>ltype,facility.level</I> |
|
|
130 specifies how messages should be logged. <I>Ltype</I> must be <I>error</I>, <I>info</I>, |
|
|
131 or <I>off</I> to indicate which of the two types of messages are being con- |
|
|
132 trolled or to turn off all <B>syslog(3)</B> messages from <B>dbclean</B>. <I>Level</I> |
|
|
133 must be a <B>syslog(3)</B> level among <I>EMERG</I>, <I>ALERT</I>, <I>CRIT</I>, <I>ERR</I>, <I>WARNING</I>, |
|
|
134 <I>NOTICE</I>, <I>INFO</I>, and <I>DEBUG</I>. <I>Facility</I> must be among <I>AUTH</I>, <I>AUTHPRIV</I>, |
|
|
135 <I>CRON</I>, <I>DAEMON</I>, <I>FTP</I>, <I>KERN</I>, <I>LPR</I>, <I>MAIL</I>, <I>NEWS</I>, <I>USER</I>, <I>UUCP</I>, and <I>LOCAL0</I> |
|
|
136 through <I>LOCAL7</I>. The default is equivalent to |
|
|
137 <B>-L</B> <I>info,MAIL.NOTICE</I> <B>-L</B> <I>error,MAIL.ERR</I> |
|
|
138 |
|
|
139 <B>dbclean</B> exits 0 on success, and > 0 if an error occurs. |
|
|
140 |
|
|
141 |
|
|
142 </PRE> |
|
|
143 <H2><A NAME="FILES">FILES</A></H2><PRE> |
|
|
144 <A NAME="FILE-@prefix@">@prefix@</A> is the DCC home directory containing data and control |
|
|
145 files. |
|
|
146 <A NAME="FILE-dcc_db">dcc_db</A> is the main file containing mail checksums. |
|
|
147 <A NAME="FILE-dcc_db.hash">dcc_db.hash</A> mail checksum database hash table. |
|
|
148 <A NAME="FILE-grey_db">grey_db</A> is the database of greylist checksums. |
|
|
149 <A NAME="FILE-grey_db.hash">grey_db.hash</A> is the greylist database hash table. |
|
|
150 <A NAME="FILE-dcc_db">dcc_db</A>-new, dcc_db-new.hash, grey_db-new, grey_db-new.hash |
|
|
151 new database and hash files until they are renamed. |
|
|
152 <A NAME="FILE-dcc_db">dcc_db</A>-old, grey_db-old |
|
|
153 previous database files. |
|
|
154 <A NAME="FILE-ids">ids</A> list of IDs and passwords, as described in <B><A HREF="dccd.html">dccd(8)</A></B>. |
|
|
155 <A NAME="FILE-whitelist">whitelist</A> contains the DCC server whitelist in the format described |
|
|
156 in <B><A HREF="dcc.html">dcc(8)</A></B>. |
|
|
157 <A NAME="FILE-grey_whitelist">grey_whitelist</A> |
|
|
158 contains the greylist server whitelist. |
|
|
159 |
|
|
160 |
|
|
161 </PRE> |
|
|
162 <H2><A NAME="SEE-ALSO">SEE ALSO</A></H2><PRE> |
|
|
163 <B><A HREF="cdcc.html">cdcc(8)</A></B>, <B>cron(8)</B>, <B><A HREF="dcc.html">dcc(8)</A></B>, <B><A HREF="dccd.html">dccd(8)</A></B>, <B><A HREF="dblist.html">dblist(8)</A></B>, <B><A HREF="dccifd.html">dccifd(8)</A></B>, <B><A HREF="dccm.html">dccm(8)</A></B>, |
|
|
164 <B><A HREF="dccproc.html">dccproc(8)</A></B>. |
|
|
165 |
|
|
166 |
|
|
167 </PRE> |
|
|
168 <H2><A NAME="HISTORY">HISTORY</A></H2><PRE> |
|
|
169 Implementation of <B>dbclean</B> was started at Rhyolite Software, in 2000. |
|
|
170 This document describes version 1.3.103. |
|
|
171 |
|
|
172 February 26, 2009 |
|
|
173 </PRE> |
|
|
174 <HR> |
|
|
175 <ADDRESS> |
|
|
176 Man(1) output converted with |
|
|
177 <a href="http://www.oac.uci.edu/indiv/ehood/man2html.html">man2html</a> |
|
|
178 modified for the DCC $Date 2001/04/29 03:22:18 $ |
|
|
179 <BR> |
|
|
180 <A HREF="http://www.dcc-servers.net/dcc/"> |
|
|
181 <IMG SRC="http://logos.dcc-servers.net/border.png" |
|
|
182 class=logo ALT="DCC logo"> |
|
|
183 </A> |
|
|
184 <A HREF="http://validator.w3.org/check?uri=referer"> |
|
|
185 <IMG class=logo ALT="Valid HTML 4.01 Strict" |
|
|
186 SRC="http://www.w3.org/Icons/valid-html401"> |
|
|
187 </A> |
|
|
188 </ADDRESS> |
|
|
189 </BODY> |
|
|
190 </HTML> |
