Version 1.3.67 of the DCC source is in
http://www.dcc-servers.net/dcc/source/dcc.tar.Z and
http://www.rhyolite.com/anti-spam/dcc/source/dcc.tar.Z
Commercial version 2.3.67 of the DCC Reputation code is in the usual place.
The major change in this version is an experimental mechanism to try to
help DCC servers with what is now too little RAM. It tries to run
a quick, partial `dbclean` as often as 3 times during the day, but only
if the server is either not very busy or if DCC clients can be chased
to another DCC server by their load balancing machinery. Dbclean is run
for at most 30 minutes before it gives up.
There is a way to turn off this kludge if it causes problems, but
it should not be used unless really needed.
The CHANGES file starts with
Occassionally run a quick dbclean on the server database when the database
gets too big.
Report "connection refused" flooding problems in `cdcc "flood stats ..."`
`cdcc stats` on DCC Reputation servers report the number of client
reputation hits.
updatedcc -K does not try to download more than once per week.
-K is assumed if stdin is not a tty. Some installations seem to
have cron jobs that run updatedcc several times per day.
SOCKS flooding only doubles instead of quadruples the backoff or delay
before retrying connections.
Add more tracing of flood state changes to try to find the stickiness
with Solaris.
/var/dcc/libexec/updatedcc should automagically fetch, build, and
install the commercial or free version, depending on the .updatedcc_pfile
file, unless you have installed a version of Linux with the broken
default `sort` collating sequence since last upgrading. If so, an
easy way to get the old updatedcc script working is to delete the
entire /var/dcc/build/dcc directory before running updatedcc.
Vernon Schryver [EMAIL PROTECTED]
_______________________________________________
DCC mailing list [email protected]
http://www.rhyolite.com/mailman/listinfo/dcc
