dccifd stabilty issues with 1.2.74

Daniel V Klein dvk@lonewolf.com
Tue Mar 29 13:56:34 UTC 2005

With that many spams being processed, change your dcc LOGDIR to look
something like "'D?logdir'", "'H?logdir'", "'M?logdir'"

That'll separate your logs into daily, hourly, or minute-ly subdirectories,
and makes a lot of operations a lot faster :-)  See the dccm man page - I
stumbled across it a while ago, and even with my small ssystem, it helps a


> Vernon Schryver wrote:
> > Another thing to check is for tmp.* files in /tmp or the
> > DCC log directory, often /var/dcc/log.
> Hrmph. Thats not pretty. I have millions of files in
> there and doing anything in that directory takes an
> extremely long time. Is there any chance DCC can start
> displaying the name of the tmp file its about to start
> working with? (when running in DEBUG mode). We process
> over 5 million mails per day and dcc keeps the logs for
> up to 14 days :/
> > Some or all of messages that dccifd was working on when it crashed
> > (assuming it crashed) will be left in tmp.* files.
> > 
> > I've seen some evidence that version 1.2.71 and older versions of dccm
> > are bothered by an odd combination of HTML, MIME, and I don't know
> > what else.  Spam causing such problems involving "Ruena Manufacturing
> > Industial" would be quite interesting.
> Well.. Older versions of dcc were actually quite stable (around 1.2.5x).
> Cami
> _______________________________________________
> DCC mailing list      DCC@rhyolite.com
> http://www.rhyolite.com/mailman/listinfo/dcc

More information about the DCC mailing list

Contact vjs@rhyolite.com by mail or use the form.