Re: [clamav-users] clamscan produces output to --log=FILE when --quiet, --no-summary and --infected are specified

2013-06-27 Thread Trevor Cooper
On 06/27/13 11:14, Trevor Cooper wrote: > I'm writing an automated daily scan script and I can't seem to get NO output > from clamscan if/when nothing of interest is found. For example, executing > with... > > "$CLAMSCAN_BIN" --quiet --no-summary

[clamav-users] clamscan produces output to --log=FILE when --quiet, --no-summary and --infected are specified

2013-06-27 Thread Trevor Cooper
ILE" Produces the following in the $LOG_FILE... --- Once for 'each' invocation of clamscan. Is there way to disable this? Thanks, Trevor -- Trevor Cooper, M.Sc. Data Systems Programmer / System

[clamav-users] CentOS 5 freshclam / main.cld broken

2012-06-28 Thread Trevor Cooper
Recently we've been getting failures from freshclam of the following type reported in Logwatch... /etc/cron.daily/freshclam: ERROR: Corrupted database file /var/clamav/main.cld: Broken or not a CVD file Since we install/reinstall with a 'scorch-the-earth' script I did so on my machine and foun