Dennis Peterson wrote:
> Kris Deugau wrote:
>
>> clamscan seems to be able to read the database files just fine.
>>
>> Any suggestions on what to poke to get more detail on what's actually
>> broken?
>
> Send the result of running clamconf and ps -ef |grep [c]lam
Seems this was a SELinux issue after all. *nrgh* What's worse, I
discovered a number of other things from the upstream CentOS repos that
*also* seem to have bad SELinux permissions (or more likely, my local
procedures and policies conflict with the standard permissions), so I've
just set it to permissive (again - as I must have done shortly after
doing the current OS (re)install) and made sure that will persist across
reboots.
-kgd
_______________________________________________
Help us build a comprehensive ClamAV guide: visit http://wiki.clamav.net
http://www.clamav.net/support/ml
(text/plain)