[clamav-users] using clamdscan and clamd to do complete file system scan

[Al Varnell]

Quite the opposite is true.  The default is to scan up to 15 directories deep.

Questions such as these are most easily solved by reading the appropriate man, in this case clamdscan.1 which reads in part:

> EXAMPLES
> 
>        (0) To scan a one file:
>               clamdscan file
> 
>        (1) To scan a current working directory:
>               clamdscan
> 
>        (2) To scan all files in /home:
>               clamdscan /home


-Al-
-- 
Al Varnell
Mountain View, CA

On Tue, Apr 28, 2015 at 11:33AM, John McGowan wrote:
> 
> Hi,
> 
> I've been banging my head trying to figure this out on my own for the
> better part of a day now.  I'm running Amazon Linux, have got the
> proper clamav packages installed to have the following stuff working.
> 
> * clamd is running
> * clamscan runs from the command line
> * clamdscan runs from the command line
> 
> However, clamdscan doesn't recursively crawl the file system, it only
> seems to want to scan a single file.
> 
> Before i craft a "find | xargs clamdscan" type of solution for this,
> can I just get confirmation that recursive scanning with just
> clamdscan is not possible?
> 
> I suspect that most people use clamdscan to do "one off" scanning,
> (mail servers, etc)
> 
> In my use case I want to leverage clamd, so that I can take advantage
> of the SysLogging capabilities of clamd, but I'm looking for more of a
> traditional daily "scan the entire file system" solution.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 3569 bytes
Desc: not available
URL: <https://lists.clamav.net/pipermail/clamav-users/attachments/20150428/d12c6a8f/attachment.bin>