> From: Dean Maluski <[EMAIL PROTECTED]> > Running CentOS 5.1. > Last night I installed and hopefully correctly configured > dccm and dccd.
I trust dccd is only running for greylisting, because I don't recall assigning a DCC server-ID for n1ety.com. > Seems that there is a problem with cron_dccd as my maillog is > continually filling with > "work around broken cron job;" > I have it setup to run as one of roots cron jobs as follows, > 15 2 * * * /var/dcc/libexec/cron-dccd > Below is a section of my maillog > > dccm and dccd > Feb 5 15:45:38 punk dccd grey[19568]: work around broken cron job; > starting `/var/dcc/libexec/dbclean -Pq4Rcron -Gon -i 32702` > Feb 5 15:45:38 punk dbclean grey[19568]: 1.3.80 work around missing > cron job for grey_db > Feb 5 15:45:38 punk dccd grey[2789]: database cleaning begun > Feb 5 15:45:38 punk dbclean grey[19568]: expired 1 records and 3 > checksums in grey_db > Feb 5 15:45:38 punk dbclean grey[19568]: hashed 485 records containing > 1383 checksums, compressed 0 records > Feb 5 15:45:38 punk dbclean grey[19568]: 12280 hash entries total, 1295 > or 10% used > Feb 5 15:45:38 punk dccd grey[2789]: 1.3.80 database grey_db reopened > with window=10,752KB real=1,944,052KB max RSS=949MB DB max=949MB Does the cron log say that cron-dccd was started at 02:15? What happens when you run /var/dcc/libexec/cron-dccd as root? Does it run `dbclean -Gon`? If not, is GREY_ENABLE=on in /var/dcc/dcc ? `/var/dcc/libexec/cron-dccd -x` will show all that the script does. Vernon Schryver [EMAIL PROTECTED] _______________________________________________ DCC mailing list [email protected] http://www.rhyolite.com/mailman/listinfo/dcc
