|
0
|
1 # whitelist file required by DCC server |
|
|
2 # Unless you are running a DCC server, this file will not be used. Even |
|
|
3 # if you are running a DCC server, it is almost always better to put entries |
|
|
4 # in the client whiteclnt files. |
|
|
5 |
|
|
6 # See the dcc man page for the format of DCC white and blacklists. |
|
|
7 # Each line must be in one of the forms |
|
|
8 #count [hex] type value |
|
|
9 # [hex] type value |
|
|
10 #include pathname |
|
|
11 |
|
|
12 # Whitelists for DCC servers are usually not a good idea. It is usually |
|
|
13 # better to use whitelists only with DCC clients such as dccproc, dccifd, |
|
|
14 # and dccm. |
|
|
15 |
|
|
16 #Changes to this file or the files it includes have no effect until dbclean |
|
|
17 # is run, perhaps by /var/dcc/libexec/cron-dccd |
|
|
18 |
|
|
19 # See http://www.rhyolite.com/dcc/ about the DCC. |
|
|
20 |
|
|
21 # 2007/09/21 20:03:38 |
|
|
22 |
|
|
23 |
|
|
24 # the whitecommon file is commonly included in client DCC whitelists |
|
|
25 #include whitecommon |
