C. Andrews Lavarre wanted us to know: >Fajar hi, thanks. >> My guess is you have both /usr/bin/clamscan ( from RPM) and >> /usr/local/bin/clamscan (from manual build). The same goes for libs also. >mmmm. You are correct, thanks: >/usr/bin/ contains May 18, 2005 versions of > clamav-config > clamdscan > clamscan > freshclam >/usr/loca/bin contains December 12, 2005 versions of the same files...
The reason it worked manually but not in cron, is probably going to be patently obvious (now at least :-) in your /etc/crontab. Look for a line that sets the path. I'll be willing to bet that it looks like this: PATH=/sbin:/bin:/usr/sbin:/usr/bin cron limits itself to those directories and does not use user defined PATH setting. So the system finds the rpm versions and not your source build. -- Regards... Todd There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order. --Ed Howdershelt Linux kernel 2.6.12-12mdksmp 3 users, load average: 0.04, 0.09, 0.04 _______________________________________________ http://lurker.clamav.net/list/clamav-users.html
