clamd problems after update

[Raymond Norton]

>I have to change my /etc/clamd.conf to "LocalSocket /tmp/clamd" (or "Clamd Socket = /tmp/clamd.socket" in the MailScanner.conf) so MailScanner can find Clamd via the >socket file. Run "MailScanner --lint" before you do anything and note any clam errors. Then make the edit, restart clamd and run "MailScanner --lint" again to see if everything >is happy after the change. 


I got it working. (found this info on http://www.global-domination.org/forum/viewtopic.php?t=893) 


Here is clamd.conf: 

AllowSupplementaryGroups true 
ArchiveBlockEncrypted true 
ArchiveBlockMax true 
ArchiveMaxCompressionRatio 300 
DatabaseDirectory /usr/local/share/clamav 
DetectBrokenExecutables true 
FixStaleSocket true 
LocalSocket /tmp/clamd 
LogFacility LOG_MAIL 
LogFile /var/log/clamav/clamd.log 
LogFileMaxSize 10M 
LogSyslog true 
MaxConnectionQueueLength 30 
MaxThreads 50 
PidFile /var/run/clamav/clamd.pid 
ReadTimeout 300 
TemporaryDirectory /tmp 
User clamav 


Had to add the following to Mailscanner.conf: 

Clamd Port = 3310 
Clamd Socket = /tmp/clamd 
Clamd Lock File = # /var/lock/subsys/clamd 
Clamd Use Threads = no 




-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.mailscanner.info/pipermail/mailscanner/attachments/20080517/57062b4c/attachment.html