Hi Sandy, Sandy Drobic wrote:
Hylton Conacher (ZR1HPC) wrote about an amavisd failure:
Now you get off you lazy butt and see for yourself how clam-av and amavisd-new are configured. (^-^)
np except I gotta be on my butt to type :)
egrep -v "^#" /etc/clamd.conf | egrep -v "^$" LogTime yes LogSyslog yes LogFacility LOG_MAIL PidFile /var/lib/clamav/clamd.pid # Same localSocket as in /etc/amavisd.conf! LocalSocket /var/run/clamav/clamd FixStaleSocket yes TCPSocket 3310 TCPAddr 127.0.0.1 User vscan Foreground no ScanOLE2 yes ScanPDF yes ScanMail yes PhishingSignatures yes PhishingScanURLs yes
I ran the above command and retrieved: hylton@Umalusi:~> egrep -v "^#" /etc/clamd.conf | egrep -v "^$" LogSyslog yes LogFacility LOG_MAIL PidFile /var/lib/clamav/clamd.pid LocalSocket /var/lib/clamav/clamd-socket TCPSocket 3310 TCPAddr 127.0.0.1 User vscan To me I should add the lines of: Foreground no ScanOLE2 yes ScanPDF yes ScanMail yes PhishingSignatures yes PhishingScanURLs yes ...into the file, althought I do not know. My /etc/antivisd.conf does not have ClamAV listed under @av_scanners but it is listed under @av_scanners_backup
Check that clamd actually is running: rcclamd status and is set to start at boot: chkconfig clamd on
Above three are all OK
and finally, that you call fresh-clam from cron.
How, as 'crontab -l' inder user and root showed nothing? Tnks for the help. Delay was due to mismatched memory. Hylton -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org