Matt wrote:

Daniel S. Cohen wrote:



ERROR: Clamd was NOT notified: Can't connect to clamd through
/var/run/clamav/clamd.sock

The /var/run/clamav is within the chrooted environment.  I've checked,
double checked, and triple checked the permissions (since they are the
same user, it should not be a problem).  I've checked /proc/<pid> of
both freshclam and clamd to make sure they are in the same root.  I've
tried running freshclam from the cron (chrooting in the cron) and as a
daemon.




Check in your freshclam.conf for:

# Send the RELOAD command to clamd.
NotifyClamd /path/to/clamav.conf


Whats the setting?

Matt



-------------------------------------------------------
This SF.Net email is sponsored by: thawte's Crypto Challenge Vl
Crack the code and win a Sony DCRHC40 MiniDV Digital Handycam
Camcorder. More prizes in the weekly Lunch Hour Challenge.
Sign up NOW http://ad.doubleclick.net/clk;10740251;10262165;m
_______________________________________________
Clamav-users mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/clamav-users




This is very strange. I'm using Debian Sid and Sarge, and freshclam works fine in several boxs.
You can try:
#apt-get --reinstall install clamav clamav-daemon clamav-base clamav-freshclam clamav-getfiles


By default everything is ok.

JP



-------------------------------------------------------
This SF.Net email is sponsored by: thawte's Crypto Challenge Vl
Crack the code and win a Sony DCRHC40 MiniDV Digital Handycam
Camcorder. More prizes in the weekly Lunch Hour Challenge.
Sign up NOW http://ad.doubleclick.net/clk;10740251;10262165;m
_______________________________________________
Clamav-users mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/clamav-users

Reply via email to