On Sun, 2009-03-22 at 12:27 +0100, Tomasz Kojm wrote: > On Sun Mar 22 2009 02:31:56 GMT+0100 (CET) > Chris <[email protected]> wrote: > > > [r...@localhost ~]# freshclam -V > > ClamAV 0.95rc2/9148/Sat Mar 21 16:17:14 2009 > > > > [r...@localhost ~]# clamd -V > > ClamAV 0.95rc2/9148/Sat Mar 21 16:17:14 2009 > > > > Am I missing something? > > Please post the output from 'clamconf -n' > Found the problem. Apparently the freshclam.conf file that is read by freshclam has to be in /usr/local/etc whereas I've always put it in the same place as clamd.conf, /etc. The startup script for freshclam in /etc/rc.d/init.d states:
start)
gprintf "Starting Clam AntiVirus Update Daemon: "
touch ${LOGFILE}; chown ${USER}:${USER} ${LOGFILE}
daemon /usr/sbin/freshclam \
--config-file=/etc/freshclam.conf \
--user ${USER} \
--quiet \
But since I'm using freshclamcron to call freshclam the freshclam
service is not active.
I'm using freshclamcron with this line
/usr/sbin/freshclam --quiet --log=/var/log/clamav/freshclam.log
--daemon-notify=/etc/clamd.conf
I guess freshclam still looks for the config file in /usr/local/etc. I
probably need to add --config-file=/usr/local/etc to the freshclamcron
script. Does that make sense?
Chris
--
KeyID 0xE372A7DA98E6705C
signature.asc
Description: This is a digitally signed message part
_______________________________________________ Help us build a comprehensive ClamAV guide: visit http://wiki.clamav.net http://www.clamav.net/support/ml
