Page 1 of 1

Installing ClamAV for file system

Posted: Tue Nov 05, 2013 3:17 pm
by laughingbuddha
Hi,

I'm running a Digital Ocean VPS for a client, all is going well and I would like to install ClamAV for file system checks.

There's no emails or email server on this install, nor Plesk (it has been an interesting experience working without Plesk), but I've installed RKHunter and Fail2Ban to help protect the server. Plus IP Tables are very much locked down with only 4 ports open at most.

My idea is to have clamAV available and running, but after doing a yum install (I'm running the ART repo channel), it's coming up with this error:-

Code: Select all

[root@dev /]# service clamd start
Starting Clam AntiVirus Daemon: ERROR: Please edit the example config file /etc/clamd.conf
ERROR: Can't open/parse the config file /etc/clamd.conf
                                                           [FAILED]
and...

Code: Select all

[root@dev /]# freshclam
ERROR: Please edit the example config file /etc/freshclam.conf
ERROR: Can't open/parse the config file /etc/freshclam.conf
Help!

Re: Installing ClamAV for file system

Posted: Tue Nov 05, 2013 7:27 pm
by scott
Is that clam package from atomic or another repo?

Re: Installing ClamAV for file system

Posted: Tue Nov 05, 2013 9:13 pm
by laughingbuddha
Er rum, not sure. I had the ART repo added to YUM when I installed it, but not sure. Is there a way to tell, or to remove it and force the install from ART.

Re: Installing ClamAV for file system

Posted: Wed Nov 06, 2013 10:51 am
by scott
If memory serves the clam config files are set to disable by default if "Example" is not commented out.

Re: Installing ClamAV for file system

Posted: Sat Feb 07, 2015 1:31 pm
by AntiochInteractive
Last few times I've installed the art distro of clamd, they needed configuring and did not run out of the box.

Re: Installing ClamAV for file system

Posted: Sat Feb 07, 2015 8:39 pm
by laughingbuddha
Yes that seemed to be the case when I last did it.

Re: Installing ClamAV for file system

Posted: Mon Feb 09, 2015 12:13 pm
by scott
We moved the configuration out from those packages (which was never very good) into an ASL module.