On 6/26/2015 14:55, Bob Cohen wrote: > > > Okay. Now I see what happened. The owner and group should be set to > clamav. And now it works. Thank you. I knew it was something simple. > > This makes sense. After a yum update clam sets the log file owner to > clam:clam instead of clamav:clamav and it must also change the user > name which causes the permissions error. How can I get amavisd, > spamassassin, and clam to play nicely with Yum Update? >
You may come upon a problem at reboot is that directory re-creates upon startup (I had some sort of problem like that, when I moved to CentOS 7, but I don't have the details handy). My problem was with clamav-milter, though, and I eventually changed all the run IDs to clamav instead. That seems to have worked for me. -Don _______________________________________________ Help us build a comprehensive ClamAV guide: https://github.com/vrtadmin/clamav-faq http://www.clamav.net/contact.html#ml
