Hi there,
On Thu, 17 Mar 2011 Russ Tyndall wrote:
> So I now have two tactics to minimize scan time:
> 1) Partially scan ALL files
> 2) Fully scan a set of recently modified files.
There might be another option. If you have access to something like
inotify on your OS you could feed incoming dat
On Mar 17, 2011, at 7:50 AM, G.W. Haywood wrote:
> On Thu, 17 Mar 2011 Russ Tyndall wrote:
>
>> So I now have two tactics to minimize scan time:
>> 1) Partially scan ALL files
>> 2) Fully scan a set of recently modified files.
>
> There might be another option. If you have access to something
On Mar 16, 2011, at 2:36 PM, Bryan Burke wrote:
>> find [path to directory] [path to second directory] ! -type d -mmin -60 >
>> [path to output file later read by clamav]
>
> This might not be too much of an issue, but thought I'd point it out: You
> might change
> "! -type d" to "-type f" (b
> Studying the FIND man page a little, I am wondering whether I should actually
> be using -cmin instead of -mmin. cmin (according to the man page) returns
> files that have had a "...change of file status information.." in the
> results.
>
> A little testing shows that it includes files in t
On 3/17/11 7:35 AM, "Russ Tyndall" wrote:
>
> On Mar 17, 2011, at 7:50 AM, G.W. Haywood wrote:
>
>> On Thu, 17 Mar 2011 Russ Tyndall wrote:
>>
>>> So I now have two tactics to minimize scan time:
>>> 1) Partially scan ALL files
>>> 2) Fully scan a set of recently modified files.
>>
>> There m
On 3/16/11 7:24 AM, Russ Tyndall wrote:
On Mar 15, 2011, at 4:51 PM, Chuck Swiger wrote:
One thing you might consider doing is using "find /location -mtime 1" to
generate a list of which files have been modified over the past day, and only scanning
these via clamdscan -f.
I experimented wi
