Hi, I decided to implement clamav and it installed in /etc/clamd.d with a config file name of milter.conf. I received the following email from the system: ERROR: Parse error at line 12: Unknown option databaseDirectory. ERROR: Parse error at line 316: Unknown option CLAMAV_FLAGS="--local. ERROR: Can't parse the config file /etc/clamd.conf Questions: Why didn't clamav create the /etc/clamd.conf file? Why are these errors appearing since I did not change any of it's files? Thanks, Peter
Hello Falko, Well since I last wrote I have changed the file and am attaching the file for you to see. Now I am not seeing any errors coming in my email but when I tried to start the clamav-milter in background services, it does not start. The strange part is that I do not see any error messages even in the system log. Peter
Please take a look at the beginning of the file: Code: # Comment or remove the line below. Example You must comment out the Example line, so that it looks like this: Code: # Comment or remove the line below. [B][COLOR="Red"]#[/COLOR][/B]Example
Hi Falko, Duh, yes I have now done that. I set the clamav to startup using admin services and reboot the system. This time I saw a message on the screen during the boot that said, clamav.milter does not agree with sendmail. Also I noticed in /var/log that there are 2 clam log files. One I created called clamd.milter and another freshclam.log but both have nothing recorded in them. I set the line in clamd.conf for the log file as: LogFile /var/log/clamd.milter which I assume is correct since the original line showed clamd.<service> Ahhh, I just found a file in /etc/freshclam.conf that I did not see before and was not mentioned in the readme. I made some changes for the log file in freshclam but still no luck and no messages in the log files after trying to restart clamav. So which of the .conf files is clamav actually using now? I have attached this file also. Peter
/etc/clamd.conf is used by ClamAV, and /etc/freshclam.conf by Freshclam, a daemon the updates ClamAV's virus signature databases.