On Saturday 14 February 2009 13:35:19 Mail List wrote:
All is still not well. Freshclam still tells me
WARNING: Clamd was NOT notified: Can't connect to clamd through ~/tmp/clamd.socket
Is this relative to root, or where?
Anne
Anne,
First off you have to decide if you need clamd?
If not then all you would need to do is edit freshclam.conf and tell it not to notify clamd.
# Send the RELOAD command to clamd. # Default: no #NotifyClamd /path/to/clamd.conf
I'm using the non rpm version for MailScanner. but your version activates it automatically. Also in the cron entry "/etc/cron.daily/freshclam" is -- is another entry telling freshclam to notify clamd. If you do need clamd then you can remove your touched socket, edit clamd.conf make sure it points to the right /tmp/clamd.socket. then..
service clamd start
I hope that helps.
That might be the best answer. If I'm going to just run scans on a cron job there's probably no reason for clamd. I'll make those changes, thanks.
All the same, it's galling that this was working before the power problems :-(
Anne