> Hi, > >> Have you checked the directory permissions: >> >> ls -ld /var/run/clamd.scan /run/clamd.scan >> >> Regards >> Mark. > > Sure, it's the third one up from this post.
Since I installed clamd a week ago, I've had to manually create the /run/clamd.scan directory and the clamd.sock file. The clamd daemon is not doing this even though it is running as root. # ps aux |grep clamd root 1963 93.0 25.5 345992 258728 ? Rs 11:34 0:02 /usr/sbin/clamd -c /etc/clamd.d/clamd.conf --foreground=yes In its config file is: LocalSocket /run/clamd.scan/clamd.sock LocalSocketGroup virusgroup LocalSocketMode 660 FixStaleSocket yes AllowSupplementaryGroups yes ... so I can't imagine why it is not creating its own socket directory and socket. I even rebooted with selinux disabled, but no improvement. When I create its socket it pretends to bind to it, but then -milter can't see clamd. Maybe the problem is with clamd after all. _______________________________________________ clamav-users mailing list clamav-users@lists.clamav.net http://lists.clamav.net/cgi-bin/mailman/listinfo/clamav-users Help us build a comprehensive ClamAV guide: https://github.com/vrtadmin/clamav-faq http://www.clamav.net/contact.html#ml
