Try this: clamconf | fold -s | grep "sysconfdir=/"
That will tell you where clam expects to find your clamd.conf file. That might not be where you expect it. Also check the service script to see if clamd is started with the --config-file=FILE option. It will override your compiled sysconfigdir.
There's no shortage of standards for compiling packages from clamav and nobody seems to use any of them. Or maybe they use all of them.
dp On 6/26/15 11:05 AM, Bob Cohen wrote:
Grr. The yum update breaks my amavisd/clam installation. I’m running CentoOs 5.x. It appears to be a permissions problem: Starting Clam AntiVirus Daemon: ERROR: LOCAL: Socket file /var/run/clamav/clamd.sock could not be bound: Permission denied I’ve reviewed the CentOS Amavisd-new, ClamAV and SpamAssassin setup recipe (http://wiki.centos.org/HowTos/Amavisd) and gone over my clamd.conf and amavisd.conf. Everything seems in order. I’m stymied. I can’t remember what I did the last time this happened and I fixed it. Here’s the socket settings in my clamd.conf file: # Value below used to work until a recent yum udate LocalSocket /var/run/clamav/clamd.sock # New value as of 12/5/2013. Matches amavisd.conf #LocalSocket /var/amavis/clamd.sock Help would be appreciated. Thank you. -Bob _______________________________________________ Help us build a comprehensive ClamAV guide: https://github.com/vrtadmin/clamav-faq http://www.clamav.net/contact.html#ml
_______________________________________________ Help us build a comprehensive ClamAV guide: https://github.com/vrtadmin/clamav-faq http://www.clamav.net/contact.html#ml
