|
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>cdcc.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="cdcc.html">cdcc(8)</A></B> Distributed Checksum Clearinghouse <B><A HREF="cdcc.html">cdcc(8)</A></B> |
|
|
17 |
|
|
18 |
|
|
19 </PRE> |
|
|
20 <H2><A NAME="NAME">NAME</A></H2><PRE> |
|
|
21 <B>cdcc</B> -- Control Distributed Checksum Clearinghouse |
|
|
22 |
|
|
23 |
|
|
24 </PRE> |
|
|
25 <H2><A NAME="SYNOPSIS">SYNOPSIS</A></H2><PRE> |
|
|
26 <B>cdcc</B> [<B>-Vdq</B>] [<B>-h</B> <I>homedir</I>] [<B>-c</B> <I>ids</I>] [<I>op1</I> <I>op2</I> <I>...</I> [<I>-</I>]] |
|
|
27 |
|
|
28 |
|
|
29 </PRE> |
|
|
30 <H2><A NAME="DESCRIPTION">DESCRIPTION</A></H2><PRE> |
|
|
31 <B>Cdcc</B> is used to clear, control, and query the control file used by Dis- |
|
|
32 tributed Checksum Clearinghouse clients such as <B><A HREF="dccm.html">dccm(8)</A></B>. The host names, |
|
|
33 UDP port numbers, IDs, and passwords local clients use to talk to servers |
|
|
34 as well as IP addresses, round trip times, and other information are con- |
|
|
35 tained in the <I>map</I> file. While <B>cdcc</B> is set-UID, it uses the real UID only |
|
|
36 when accessing the <I>map</I> file. It refuses to display sensitive information |
|
|
37 such as passwords unless the real UID is the same as the effective UID. |
|
|
38 Note that <B>cdcc</B> needs to be set to a UID that can read and write the <I>map</I> |
|
|
39 file, but that UID need not be 0. |
|
|
40 |
|
|
41 <B>Cdcc</B> is also used to send commands to DCC servers to tell them to stop, |
|
|
42 reload their lists of DCC IDs, turn on tracing, and so forth. |
|
|
43 |
|
|
44 Many commands sent to DCC servers require a numeric DCC ID and a password |
|
|
45 recognized by the server. A DCC password is a 1-32 character string that |
|
|
46 does not contain blank, tab, newline or carriage return characters. The |
|
|
47 ID is specified with the <B>id</B> operation. If <B>cdcc</B> is run with a real UID |
|
|
48 that can read the <I>ids</I> file and a password is not specified (see the |
|
|
49 <B>password</B> operation), then the current password for the specified ID in |
|
|
50 the <I>ids</I> file will be used. If no <I>ids</I> file is available and a password |
|
|
51 and DCC ID are not specified, <B>cdcc</B> uses the anonymous DCC client-ID. DCC |
|
|
52 servers do not expect a password from clients using the anonymous client- |
|
|
53 ID, but they also won't honor control requests. |
|
|
54 |
|
|
55 Operations that modify the <I>map</I> file can only be performed when the real |
|
|
56 UID is sufficient to modify the file directly. Trying to perform an |
|
|
57 operation that requires a password without specifying a server-ID or |
|
|
58 without using a UID that can access the <I>ids</I> file produces an error mes- |
|
|
59 sage complaining about a "privileged operation." |
|
|
60 |
|
|
61 Commands and operations are read from the command line or from stdin. A |
|
|
62 series of <I>op1</I> <I>op2</I> <I>...</I> operations followed a <I>-</I> (a dash) causes operations |
|
|
63 to be read from stdin after the command line operations are processed. |
|
|
64 Semi-colons or newlines separate commands in UNIX command-line "words," |
|
|
65 as well as when commands are read from stdin. Since each command line |
|
|
66 operation must be a shell "word," quotes are often required as in |
|
|
67 |
|
|
68 % cdcc "load map.txt" |
|
|
69 or |
|
|
70 |
|
|
71 % cdcc "host localhost;info" stats |
|
|
72 |
|
|
73 <A NAME="OPTIONS"><B>OPTIONS</B></A> |
|
|
74 The following options are available: |
|
|
75 |
|
|
76 <A NAME="OPTION-V"><B>-V</B></A> displays the version of the DCC controller. |
|
|
77 |
|
|
78 <A NAME="OPTION-d"><B>-d</B></A> enables debugging output from the DCC client software. Additional |
|
|
79 <B>-d</B> options increase the number of messages. See the <B>debug</B> command. |
|
|
80 |
|
|
81 <A NAME="OPTION-q"><B>-q</B></A> quiets initial complaints about the map file and some messages about |
|
|
82 successful commands. See the <B>quiet</B> command. |
|
|
83 |
|
|
84 <A NAME="OPTION-h"><B>-h</B></A> <I>homedir</I> |
|
|
85 overrides the default DCC home directory, <I>@prefix@</I>. See the <B>homedir</B> |
|
|
86 operation. |
|
|
87 |
|
|
88 <A NAME="OPTION-c"><B>-c</B></A> <I>ids</I> |
|
|
89 specifies file containing DCC IDs and passwords known by the local |
|
|
90 DCC server. An <I>ids</I> file that can be read by others cannot be used. |
|
|
91 The format of the <I>ids</I> file is described in <B><A HREF="dccd.html">dccd(8)</A></B>. |
|
|
92 |
|
|
93 <I>op1</I> <I>op2</I> <I>...</I> |
|
|
94 are operations or commands such as "id 100; stop". Commands or |
|
|
95 operations specified on the command line are performed before the |
|
|
96 first interactive request. The last command can be <I>-</I> to specify |
|
|
97 that additional commands should be read from stdin. |
|
|
98 |
|
|
99 <A NAME="OPERATIONS"><B>OPERATIONS</B></A> |
|
|
100 Local operations include the following: |
|
|
101 |
|
|
102 <A NAME="OPERATION-help"><B>help</B></A> [<I>command</I>] |
|
|
103 lists information about one or all available commands and opera- |
|
|
104 tions. |
|
|
105 |
|
|
106 <A NAME="OPERATION-exit"><B>exit</B></A> stops <B>cdcc</B> |
|
|
107 |
|
|
108 <A NAME="OPERATION-grey"><B>grey</B></A> [<I>on</I> | <I>off</I>] |
|
|
109 switches between DCC and greylist servers. |
|
|
110 |
|
|
111 <A NAME="OPERATION-homedir"><B>homedir</B></A> [<I>path</I>] |
|
|
112 displays or specifies the DCC home directory. |
|
|
113 |
|
|
114 <A NAME="OPERATION-file"><B>file</B></A> [<I>map</I>] |
|
|
115 displays or specifies the name or path of the map file. The string |
|
|
116 "-" specifies the default file <I>map</I> in the DCC home directory. |
|
|
117 |
|
|
118 <A NAME="OPERATION-new-map"><B>new map</B></A> [<I>map</I>] |
|
|
119 creates a new, empty file for DCC server host names, port numbers, |
|
|
120 passwords, and so forth. There must not already be a file of the |
|
|
121 same name. The default is <I>map</I> in the DCC home directory. |
|
|
122 |
|
|
123 <A NAME="OPERATION-delete"><B>delete</B></A> <I>host</I>[,<I>port</I>] |
|
|
124 deletes the entry in the <I>map</I> file for <I>host</I> and UDP <I>port.</I> If |
|
|
125 greylist mode has been set with the <B>grey on</B> command, the entry for |
|
|
126 the grelist server at <I>host</I> is deleted. |
|
|
127 |
|
|
128 <A NAME="OPERATION-add"><B>add</B></A> <I>host</I>[,<I>port</I>] [<I>RTT+adj</I>|<I>RTT-adj</I>] [<I>Greylist</I>] [<I>client-ID</I> [password]] |
|
|
129 adds an entry to the <I>map</I> file. The <I>port</I> can be "-" to specify the |
|
|
130 default DCC server port number. |
|
|
131 |
|
|
132 An adjustment to the round trip time is a multiple of 10 millisec- |
|
|
133 onds between -4000 and +4000 following the string <I>RTT</I>. The adjust- |
|
|
134 ment is added to the average measured round trip time when the DCC |
|
|
135 client software picks the "nearest" DCC server, or the server with |
|
|
136 the smallest RTT. If an IP address is mentioned more than once in |
|
|
137 the list of servers, for example because it is among the addresses |
|
|
138 for more than one server name, conflicts among RTT adjustments are |
|
|
139 resolved by picking the adjustment with the largest absolute value. |
|
|
140 |
|
|
141 <I>Greylist</I> marks an entry for a greylist servers. <I>Greylist</I> is |
|
|
142 assumed if greylist mode has been set with the <B>grey on</B> command, See |
|
|
143 <B><A HREF="dccd.html">dccd(8)</A></B>. |
|
|
144 |
|
|
145 If both the client-ID and the password are absent, the anonymous |
|
|
146 client-ID, 1, is used. The string <I>anon</I> is equivalent to the anony- |
|
|
147 mous client-ID. A null password string is assumed if the password |
|
|
148 is missing and the client-ID is 1 or also missing. |
|
|
149 |
|
|
150 <A NAME="OPERATION-load"><B>load</B></A> <I>info-file</I> |
|
|
151 loads the current parameter file with the host names, port numbers, |
|
|
152 IDs, and passwords in <I>info-file</I>. Standard input is understood if |
|
|
153 <I>info-file</I> is "-". |
|
|
154 |
|
|
155 A suitable file can be created with the <B>info</B> operation. It con- |
|
|
156 sists of ignored blank or comment lines starting with '#' and other |
|
|
157 lines in the same format as the arguments to the <B>add</B> operation. |
|
|
158 Note that output of the <B>info</B> command will lack passwords unless it |
|
|
159 is run by a privileged user. |
|
|
160 |
|
|
161 <A NAME="OPERATION-host"><B>host</B></A> [<I>hostname</I>] |
|
|
162 specifies the host name of the DCC server to which commands should |
|
|
163 be sent. If <I>hostname</I> is "-", the current default DCC server is |
|
|
164 chosen. |
|
|
165 |
|
|
166 <A NAME="OPERATION-port"><B>port</B></A> [<I>port</I>] |
|
|
167 specifies the UDP port number of the DCC server to which commands |
|
|
168 should be sent. The default is 6277 or 6276 depending on the set- |
|
|
169 ting of the greylist mode controlled with the <B>grey</B> command. |
|
|
170 |
|
|
171 <A NAME="OPERATION-password"><B>password</B></A> <I>secret</I> |
|
|
172 specifies the password with which to sign commands sent to the DCC |
|
|
173 server specified with the <B>server</B> and <B>port</B> operations. |
|
|
174 |
|
|
175 <A NAME="OPERATION-id"><B>id</B></A> [<I>ID</I>] |
|
|
176 specifies or displays the numeric DCC ID for commands sent to the |
|
|
177 DCC server specified with the <B>server</B> and <B>port</B> operations. If no |
|
|
178 password is specified with the <B>password</B> command, the password is |
|
|
179 sought in the local <I>ids</I>. |
|
|
180 |
|
|
181 <A NAME="OPERATION-info"><B>info</B></A> [<B>-N</B>] |
|
|
182 displays information about the connections to DCC servers. It |
|
|
183 starts with the current date and name of the current <I>map</I> file or |
|
|
184 says that <B>cdcc</B> is using the implicit file created with the <B>server</B> |
|
|
185 and <B>port</B> operations. It then says when host names will next be |
|
|
186 resolved into IP addresses, the smallest round trip time to the IP |
|
|
187 addresses of known DCC servers. The host name, UDP port number (or |
|
|
188 dash if it is the default), DCC client-ID, and password (if <B>cdcc</B> is |
|
|
189 used by a privileged user) are shown in one line per configured DCC |
|
|
190 server. |
|
|
191 |
|
|
192 The currently preferred IP address is indicated by an asterisk. |
|
|
193 The "brand" of the server, its DCC ID, and its IP address are dis- |
|
|
194 played in one line per IP address. The performance of the server |
|
|
195 at each IP address in the most recent 32 operations is displayed in |
|
|
196 a second line. The second line ends with the measured delay |
|
|
197 imposed by the server on requests with this client's ID. |
|
|
198 |
|
|
199 <B>-N</B> displays the reverse DNS name of each server. |
|
|
200 |
|
|
201 <A NAME="OPERATION-RTT"><B>RTT</B></A> [<B>-N</B>] |
|
|
202 measures the round trip time to the DCC servers. It does this by |
|
|
203 discarding accumulated information and forcing a probe of all |
|
|
204 listed server IP addresses. |
|
|
205 |
|
|
206 <I>Beware</I> that when run with sufficient privilege, the <B>RTT</B> operation |
|
|
207 is like the <B>info</B> and <B>load</B> operations and displays cleartext pass- |
|
|
208 words. |
|
|
209 |
|
|
210 <B>-N</B> displays the reverse DNS name of each server. |
|
|
211 |
|
|
212 <A NAME="OPERATION-debug"><B>debug</B></A> Op Ar on | off | TTL=x |
|
|
213 increases or decreases debugging information from the DCC client |
|
|
214 software or sets the IP TTL on queries to the server. See <B>-d</B>. |
|
|
215 |
|
|
216 Some operating systems do not include the functions required to |
|
|
217 change the IP TTL. Others include the required functions but have |
|
|
218 no apparent effect. |
|
|
219 |
|
|
220 <A NAME="OPERATION-quiet"><B>quiet</B></A> [<I>on</I> | <I>off</I>] |
|
|
221 makes commands more quiet or more verbose. |
|
|
222 |
|
|
223 <A NAME="OPERATION-IPv6"><B>IPv6</B></A> [<I>on</I> | <I>off</I>] |
|
|
224 sets a switch to cause clients using the map file to try to use |
|
|
225 IPv6. |
|
|
226 |
|
|
227 <A NAME="OPERATION-SOCKS"><B>SOCKS</B></A> [<I>on</I> <I>off</I>] |
|
|
228 sets a switch to cause DCC clients using the map to use the SOCKS5 |
|
|
229 protocol, if they have been built with a SOCKS library. The socks |
|
|
230 library linked with the DCC client must be configured appropri- |
|
|
231 ately, often including knowing which DCC servers must be connected |
|
|
232 via the SOCKS proxy and which can be reached directly. DCC clients |
|
|
233 use SOCKS functions such as Rsendto() with all or no servers |
|
|
234 depending on the setting of this switch. |
|
|
235 |
|
|
236 <A NAME="OPERATION-src"><B>src</B></A> [<I>-</I> | <I>IPaddress</I>] |
|
|
237 displays or configures the source address of DCC client requests. |
|
|
238 <I>-</I> removes the explicit configuration of the source, while <I>IPaddress</I> |
|
|
239 sets it. This makes sense only on multi-homed hosts. It can be |
|
|
240 useful for passing firewalls. |
|
|
241 |
|
|
242 <A NAME="DCC-SERVER-COMMANDS"><B>DCC SERVER COMMANDS</B></A> |
|
|
243 Commands that can be sent to a DCC server include the following. Most of |
|
|
244 the commands must be used with the server's <I>ID</I> specified with the <B>id</B> com- |
|
|
245 mand. The specified ID is included in the commands sent to the server |
|
|
246 The command itself is digitally signed with the first password associated |
|
|
247 with the ID in the <I>ids</I> file. The server requires that the signature |
|
|
248 match one of the passwords associated with the ID in its <I>ids</I> file. |
|
|
249 |
|
|
250 <A NAME="OPERATION-delck-type-hex1-hex2-hex3-hex4"><B>delck type hex1 hex2 hex3 hex4</B></A> |
|
|
251 asks the server to delete the <I>type</I> checksum with value <I>hex1</I> <I>hex2</I> |
|
|
252 <I>hex3</I> <I>hex4</I>. The type and checksum values can be found in <B><A HREF="dccproc.html">dccproc(8)</A></B> |
|
|
253 and <B><A HREF="dccm.html">dccm(8)</A></B> log files or computed with <I>dccproc</I> <B>-QC</B>. |
|
|
254 |
|
|
255 There are very few situations where it makes sense to bother to |
|
|
256 delete checksums. For example, mail that was accidentally reported |
|
|
257 with a target count of "MANY" is either private and so will not be |
|
|
258 seen by other people and so will not be affected, or it is bulk and |
|
|
259 its source so must have already been whitelisted by recipients. |
|
|
260 |
|
|
261 <A NAME="OPERATION-stats"><B>stats</B></A> [<I>all</I> | <I>clear</I>] |
|
|
262 displays current status and statistics from the current DCC server |
|
|
263 or for <I>all</I> known DCC servers. The server's counters will be cleared |
|
|
264 after they are displayed when the server's ID has been specified |
|
|
265 with the <B>id</B> <I>ID</I> operation. |
|
|
266 |
|
|
267 <A NAME="OPERATION-clients"><B>clients</B></A> [<B>-nsiaVAK</B>] [<I>max</I> [<I>thold</I>]] [<I>addr</I>[<I>/prefix</I>]] |
|
|
268 displays some of the clients recently seen by the server. |
|
|
269 <B>-n</B> displays only the IP addresses and not the names of clients. |
|
|
270 <B>-s</B> sorts the clients by the number of requests they have made. |
|
|
271 <B>-i</B> counts clients with the same client-ID as single entities. |
|
|
272 <B>-a</B> produces 24 hour average numbers of requests. |
|
|
273 <B>-A</B> displays only anonymous clients. |
|
|
274 <B>-K</B> displays only clients using client-IDs. |
|
|
275 <B>-V</B> includes the DCC protocol versions used by clients. |
|
|
276 <I>max</I> displays only the <I>max</I> most recent clients. |
|
|
277 <I>max</I> <I>thold</I> displays the most recent <I>max</I> clients that have made at |
|
|
278 least <I>thold</I> requests. |
|
|
279 <I>addr</I>[<I>/prefix</I>] restricts the results to the DCC client with that IP |
|
|
280 address or clients with addresses in that CIDR block. |
|
|
281 |
|
|
282 The mechanism that implements this command involves asking the DCC |
|
|
283 server for the first approximately 100 clients, then the second |
|
|
284 about 100, and so on, If entries change position in the complete |
|
|
285 list maintained by the server between requests, the displayed list |
|
|
286 will have duplicate or missing entries. Only clients heard from |
|
|
287 since <B>stats clear</B> was last used are displayed. |
|
|
288 |
|
|
289 <A NAME="OPERATION-stop"><B>stop</B></A> |
|
|
290 tells the DCC server to exit. |
|
|
291 |
|
|
292 <A NAME="OPERATION-system-stop"><B>system stop</B></A> |
|
|
293 tells the DCC server to exit so that the operating system can be |
|
|
294 shut down. This tells the DCC server on some systems to delete the |
|
|
295 dcc_db.hash file to speed system shut down. The file will be |
|
|
296 rebuilt automatically by <B>dbclean</B> when the DCC server is restarted. |
|
|
297 |
|
|
298 <A NAME="OPERATION-clean-stop"><B>clean stop</B></A> |
|
|
299 tells the DCC server to exit after applying fsync() to the database. |
|
|
300 |
|
|
301 <A NAME="OPERATION-reload-IDs"><B>reload IDs</B></A> |
|
|
302 tells the local DCC server to reload its DCC <I>ids</I> file immediately. |
|
|
303 This command is not strictly needed. Every several minutes, the DCC |
|
|
304 server notices if the file has been changed and automatically reads |
|
|
305 it. |
|
|
306 |
|
|
307 <A NAME="OPERATION-flood-check"><B>flood check</B></A> |
|
|
308 tells the DCC server to check for changes in the <I>flod</I> file and try |
|
|
309 to restart any of the streams to peers that are broken. |
|
|
310 |
|
|
311 <A NAME="OPERATION-flood-shutdown"><B>flood shutdown</B></A> |
|
|
312 tells the DCC server to cleanly stop flooding checksums to and from |
|
|
313 peers. The server will wait for sending and receiving peers to |
|
|
314 agree to stop. Each <B>flood shutdown</B> or <B>flood halt</B> request increases |
|
|
315 a count of reasons why the server should not flood checksums. |
|
|
316 |
|
|
317 <A NAME="OPERATION-flood-halt"><B>flood halt</B></A> |
|
|
318 tells the DCC server to abruptly stop flooding checksums to and from |
|
|
319 peers. |
|
|
320 |
|
|
321 <A NAME="OPERATION-flood-rewind"><B>flood rewind</B></A> <I>server-ID</I> |
|
|
322 tells the DCC server to ask its peer with <I>server-ID</I> to rewind and |
|
|
323 resend its stream of checksums. |
|
|
324 |
|
|
325 <A NAME="OPERATION-flood-ffwd-in"><B>flood ffwd in</B></A> <I>server-ID</I> |
|
|
326 tells the DCC server to ask its peer to "fast forward" or skip to |
|
|
327 the end of the incoming flood. |
|
|
328 |
|
|
329 <A NAME="OPERATION-flood-ffwd-out"><B>flood ffwd out</B></A> <I>server-ID</I> |
|
|
330 tells the DCC server to "fast forward" or skip to the current end of |
|
|
331 the flood to its peer. |
|
|
332 |
|
|
333 <A NAME="OPERATION-flood-resume"><B>flood resume</B></A> |
|
|
334 tells the DCC server to reduce the number of reasons to not flood |
|
|
335 checksums increased by <B>flood shutdown</B> and <B>flood halt.</B> When the num- |
|
|
336 ber of reasons reaches zero, the server tries to resume flooding. |
|
|
337 |
|
|
338 <A NAME="OPERATION-flood-list"><B>flood list</B></A> |
|
|
339 displays the list of current incoming and outgoing floods. Each |
|
|
340 line contains the server-ID of the peer, the IP address and port |
|
|
341 used for the outgoing flood, the address for the incoming flood if |
|
|
342 different, and the host name. Only the server-IDs of flooding peers |
|
|
343 are disclosed with the server's ID. |
|
|
344 |
|
|
345 <A NAME="OPERATION-flood-stats"><B>flood stats</B></A> [<B>clear</B>] { <I>server-ID</I> | <I>all</I> } |
|
|
346 displays counts of checksum reports sent and received by the current |
|
|
347 flooding connections to and from <I>server-ID</I> or <I>all</I> flooding connec- |
|
|
348 tions and then optionally clears the counts. |
|
|
349 |
|
|
350 <A NAME="OPERATION-DB-clean"><B>DB clean</B></A> |
|
|
351 is used by <B>dbclean</B> to tell the server that the database expiration |
|
|
352 has begun. |
|
|
353 |
|
|
354 <A NAME="OPERATION-DB-new"><B>DB new</B></A> |
|
|
355 is used by <B>dbclean</B> to tell the server that the database cleaning is |
|
|
356 complete. |
|
|
357 |
|
|
358 <A NAME="OPERATION-flush-cache"><B>flush cache</B></A> |
|
|
359 tells the server to flush its cache and to keep it clean. |
|
|
360 |
|
|
361 <A NAME="OPERATION-cache-ok"><B>cache ok</B></A> |
|
|
362 tells the server to resume normal operations after <B>flush cache</B>. |
|
|
363 |
|
|
364 <A NAME="OPERATION-clock-check"><B>clock check</B></A> |
|
|
365 asks the DCC server to say how much its clock differs from the local |
|
|
366 clock. |
|
|
367 |
|
|
368 <B>clock kludge +/-seconds</B> |
|
|
369 adjusts the timestamps in server commands to make it possible to |
|
|
370 control servers with inaccurate clocks. |
|
|
371 |
|
|
372 <A NAME="OPERATION-trace"><B>trace</B></A> <I>default</I> |
|
|
373 turns on <I>ANON</I> and <I>CLNT</I> tracing and turns off all others. |
|
|
374 |
|
|
375 <A NAME="OPERATION-trace"><B>trace</B></A> <I>mode</I> <I>{on|off}</I> |
|
|
376 turns the server's tracing <I>mode</I> on or off. <I>Mode</I> must be one of: |
|
|
377 <I>ADMN</I> administrative requests from <B>cdcc</B> |
|
|
378 <I>ANON</I> errors by anonymous clients |
|
|
379 <I>CLNT</I> errors by authenticated clients |
|
|
380 <I>RLIM</I> rate-limited messages |
|
|
381 <I>QUERY</I> all queries and reports |
|
|
382 <I>RIDC</I> messages concerning the report-ID cache that is used to |
|
|
383 detect duplicate reports from clients |
|
|
384 <I>FLOOD</I> messages about inter-server flooding connections |
|
|
385 <I>FLOOD2</I> messages about flooded reports |
|
|
386 <I>IDS</I> unknown server-IDs in flooded reports |
|
|
387 <I>BL</I> blacklisted clients |
|
|
388 <I>DB</I> odd database events |
|
|
389 <I>WLIST</I> reports of whitelisted checksums from authenticated, not |
|
|
390 anonymous DCC clients |
|
|
391 |
|
|
392 <A NAME="OPERATION-cdcc"><B>cdcc</B></A> exits with 0 on success, and >0 if an error occurs in operations |
|
|
393 specified on the command line. |
|
|
394 |
|
|
395 |
|
|
396 </PRE> |
|
|
397 <H2><A NAME="FILES">FILES</A></H2><PRE> |
|
|
398 <A NAME="FILE-@prefix@">@prefix@</A> DCC home directory |
|
|
399 <A NAME="FILE-map">map</A> memory mapped file in the home DCC home directory of server |
|
|
400 host names, port numbers, passwords, measured round trip times |
|
|
401 (RTT), and so forth. |
|
|
402 <A NAME="FILE-ids">ids</A> list of IDs and passwords, as described in <B><A HREF="dccd.html">dccd(8)</A></B>. It is only |
|
|
403 required by systems running the DCC server, but is used by <B>cdcc</B> |
|
|
404 if available. |
|
|
405 |
|
|
406 |
|
|
407 </PRE> |
|
|
408 <H2><A NAME="SEE-ALSO">SEE ALSO</A></H2><PRE> |
|
|
409 <B><A HREF="dbclean.html">dbclean(8)</A></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>, <B><A HREF="dccproc.html">dccproc(8)</A></B>, |
|
|
410 <B><A HREF="dccsight.html">dccsight(8)</A></B>. |
|
|
411 |
|
|
412 |
|
|
413 </PRE> |
|
|
414 <H2><A NAME="HISTORY">HISTORY</A></H2><PRE> |
|
|
415 Implementation of <B>cdcc</B> was started at Rhyolite Software in 2000. This |
|
|
416 document describes version 1.3.103. |
|
|
417 |
|
|
418 February 26, 2009 |
|
|
419 </PRE> |
|
|
420 <HR> |
|
|
421 <ADDRESS> |
|
|
422 Man(1) output converted with |
|
|
423 <a href="http://www.oac.uci.edu/indiv/ehood/man2html.html">man2html</a> |
|
|
424 modified for the DCC $Date 2001/04/29 03:22:18 $ |
|
|
425 <BR> |
|
|
426 <A HREF="http://www.dcc-servers.net/dcc/"> |
|
|
427 <IMG SRC="http://logos.dcc-servers.net/border.png" |
|
|
428 class=logo ALT="DCC logo"> |
|
|
429 </A> |
|
|
430 <A HREF="http://validator.w3.org/check?uri=referer"> |
|
|
431 <IMG class=logo ALT="Valid HTML 4.01 Strict" |
|
|
432 SRC="http://www.w3.org/Icons/valid-html401"> |
|
|
433 </A> |
|
|
434 </ADDRESS> |
|
|
435 </BODY> |
|
|
436 </HTML> |
