Also, don't forget to run cron-dccd every day. It is recommended to
place a link to it in your path, and place it in your crontab.

Your link might be something like this:
ln -s /usr/local/dcc/libexec/cron-dccd /usr/local/bin/cron-dccd

and your crontab entry:
43 11 * * * /usr/local/bin/cron-dccd

If you don't do this, your dcc log files may grow forever (dccifd
produces log files, but dccproc does not). I also change the number of
days the logs are kept from the default of 14, to:
DBCLEAN_LOGDAYS=2

Another option is to remove the log directory so dcc will not log at
all (but it will now produce harmless error messages). Yours might be:
/usr/local/dcc/log

Gary V



-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642
_______________________________________________
AMaViS-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/amavis-user
AMaViS-FAQ:http://www.amavis.org/amavis-faq.php3
AMaViS-HowTos:http://www.amavis.org/howto/

Reply via email to