Subject: Re: CVS commit: pkgsrc/mail/clamsmtp
To: None <email@example.com>
From: Martti Kuparinen <firstname.lastname@example.org>
Date: 06/15/2007 13:38:33
Martti Kuparinen wrote:
> Module Name: pkgsrc
> Committed By: martti
> Date: Fri Jun 15 09:47:06 UTC 2007
> Modified Files:
> pkgsrc/mail/clamsmtp: Makefile
> pkgsrc/mail/clamsmtp/files: clamsmtpd.sh
> Log Message:
> Added clamsmtpd_maxwait (default is 600 seconds). This makes it possible
> to define how long clamsmtpd should wait for clamd.
Our server (NetBSD/amd64 4.0_BETA2) is a 2.33 GHz dual-core Intel Xeon with 4 GB
RAM and disks connected to a hardware RAID controller so it should be fast
enough for this kind of stuff. Yesterday I saw clamd taking it nice-and-slow, it
took almost 7 minutes(!) until the /tmp/clamd socket appeared. "DNS", you might
say... No, name resolution was working just fine.
So, my conclusion is that having a long default is better than having a system
which might not have a working SMTP setup after reboot. Feel free to use a
smaller/larger value in /etc/rc.conf.