On my system I had to chmod /var/run/clamav to 700 owned by clamav:clamav. You have that dir set to 755. I'm not sure this will work exactly the same on all distro's but on Slackware this works just fine.
It works fine at mode 755. If you're using an /etc/sysconfig/clamav-milter config file, you could be specifying it on the commandline which will override the config file settings:
[EMAIL PROTECTED] root]# ps ax | grep clamav-milter | grep -v grep
6090 ? S 4:07 clamav-milter --config-file=/etc/clamav.conf --max-children=20 --quiet -ol local:/var/clamav/clmilter.socket
So while I do have a /var/run/clamav/ directory and I have clamd's socket in there, I keep the clamav-milter socket in the /var/clamav/ directory. I think my next batch of RPM's is going to put clamd's socket in /var/clamav/ instead of /var/run/clamav/ (because I prefer to keep pid files in /var/run/* and sockets in /var/{packagename}/.
Blue skies... Todd
------------------------------------------------------- This SF.net email is sponsored by: The Robotic Monkeys at ThinkGeek For a limited time only, get FREE Ground shipping on all orders of $35 or more. Hurry up and shop folks, this offer expires April 30th! http://www.thinkgeek.com/freeshipping/?cpg=12297 _______________________________________________ Clamav-users mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/clamav-users
