On 01.12.18 14:20, Michael Harris wrote:
Does running clamav modify the access timestamp?
clamav does not.
However, the access timestamp is usually modified by system kernel, when
file is accessed (that's what "access timestamp" means).
On some systems (e.g. linux), you can avoid this by mounti
I removed that option.
So what is the right way to make clamAV scan the maximum possible size?
On Wed, Nov 28, 2018 at 7:31 AM Henrik K wrote:
>
> On Tue, Nov 27, 2018 at 05:01:40PM -0500, Albert o wrote:
> > "sudo clamscan -r --remove=yes /"
>
> ClamAV doesn't exactly have a perfect track record
Trial and error, depending on your setup.
Must not exceed the amount of RAM you have installed less what is needed to run
your system and whatever else you have running at the time.
Best advice would be to set it to the size of the largest file you need to scan.
-Al-
On Sun, Dec 02, 2018 at 0
I wonder how many signature writers bother to match content at the end of files.
Hopefully, none, in which case full file scanning is pointless.
dp
On 12/2/18 3:02 PM, Al Varnell wrote:
Trial and error, depending on your setup.
Must not exceed the amount of RAM you have installed less what is
What do I need to use in clamd.conf to scan the maximum possible size?
MaxFileSize 3M
MaxFileSize 3999M
Is this syntax correct?
On Mon, Dec 3, 2018, 00:06 Dennis Peterson I wonder how many signature writers bother to match content at the end of
> files. Hopefully, none, in which case full fil
