On 12/6/2012 11:25 AM, franckm wrote:
Bowie Bailey wrote:
On 12/6/2012 10:43 AM, franckm wrote:
Ok I've done that. LogTimes are shown (in a weird datetime format) but
the
file that I've just scanned is not listed at all:
clamdscan /tmp/clamscan-franck-test/clamscan-franck-testclamscan-man.txt
/tmp/clamscan-franck-test/clamscan-franck-testclamscan-man.txt: OK
----------- SCAN SUMMARY -----------
Infected files: 0
Time: 0.003 sec (0 m 0 s)
By default, clamd does not log clean files. There is an option for that
in clamd.conf...
# Also log clean files. Useful in debugging but drastically increases the
# log size.
# Default: disabled
#LogClean 1
Thanks it works now but I am not getting the log line when a new file is
getting scanned. I only get the result (OK line)
With clamscan in verbose mode I used to get:
clamscan --verbose
/tmp/clamscan-franck-test/clamscan-franck-testclamscan-man.txt
Scanning /tmp/clamscan-franck-test/clamscan-franck-testclamscan-man.txt
/tmp/clamscan-franck-test/clamscan-franck-testclamscan-man.txt: OK
----------- SCAN SUMMARY -----------
Known viruses: 315745
Engine version: 0.93
Scanned directories: 0
Scanned files: 1
Infected files: 0
Data scanned: 0.01 MB
Time: 2.001 sec (0 m 2 s)
With clamdscan in verbose mode (LogVerbose yes) I get only the OK line
Thu Dec 6 16:16:17 2012 ->
/tmp/clamscan-franck-test/clamscan-franck-testclamscan-man.txt: OK
I don't think there is any way to replicate the verbose command line
behavior in the log file. The log file will only log one line per file
scanned indicating whether it is clean or has a virus.
Is there really any value in logging that a file is being scanned and
then 2 seconds later logging that the file is clean?
--
Bowie
_______________________________________________
Help us build a comprehensive ClamAV guide: visit http://wiki.clamav.net
http://www.clamav.net/support/ml
