On Thu, May 29, 2008 at 6:15 AM, Bowie Bailey <[EMAIL PROTECTED]> wrote: > Aldo Foot wrote: >> >> $ /usr/bin/clamdscan /scratch/mydir >> WARNING: Clamd is not configured properly. >> ----------- SCAN SUMMARY ----------- >> Infected files: 0 >> Time: 0.021 sec (0 m 0 s) >> >> So it appears the client does not need the presence of a clamav-server >> and its /etc/clamd.conf to run and scan targets. This suggest that one >> can manually scan and simply put that line in a cron job --Is this >> rationale correct? >> >> Then the clamav-server is simply to have clamd doing scans >> in real-time 24x7 -- is this correct? > > No, that's not correct. The clamav-server is needed to have clamd > running as a daemon. This allows clamdscan to scan files quickly > without having to load up the entire virus database each time. Real > time file scanning is something else entirely. > > I don't know why clamdscan appears to work despite the error. I'm not > sure if it's actually loading the database and scanning or if it's just > failing quietly (which would not be a good thing). The proper way to do > it is to use "clamscan" if you don't have clamd running. > > Bowie
Yes - clamscan runs cleanly. $ /usr/bin/clamscan -v /scr0 ----------- SCAN SUMMARY ----------- Known viruses: 301908 Engine version: 0.92.1 Scanned directories: 1 Scanned files: 0 Infected files: 0 Data scanned: 0.00 MB Time: 4.979 sec (0 m 4 s) ~af _______________________________________________ Help us build a comprehensive ClamAV guide: visit http://wiki.clamav.net http://lurker.clamav.net/list/clamav-users.html
