>From: Kris Deugau [mailto:kdeu...@vianet.ca]
>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 th
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. *n
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
dp
___
Help us bui
CentOS 5, Clam installed from RPMForge repo.
Was running 0.95.1 when this happened yesterday, upgrading to 0.95.2
didn't change anything.
[r...@snafu kdeugau]# /etc/init.d/clamd restart
Stopping Clam AntiVirus Daemon:[FAILED]
Starting Clam AntiVirus Daemon: LibClamAV
