The verbiage of the warning may be a little misleading. It doesn't tell you
how much has been scanned prior to the call into cli_scanxz(). It is likely
that it scanned additional data prior to the call to cli_scanxz(), which counts
towards the scan limit.
If you re-scan with the --debug flag s
There is something I don't get
this my clamd.conf
user@debian:~/Downloads/clamav-0.101.0$ cat /etc/clamav/clamd.conf
#Automatically Generated by clamav-daemon postinst
#To reconfigure clamd run #dpkg-reconfigure clamav-daemon
#Please read /usr/share/doc/clamav-daemon/README.Debian.gz for details
L
On 2018-12-03 at 09:58 -0800, Dennis Peterson wrote:
> If it is a big concern you can use the split command to create
> "splits" of the suspect file. Split accepts various size arguments
> (bytes, lines...) and will create as many files as it takes to split
> the entire large file. These can be sca
If it is a big concern you can use the split command to create "splits" of the
suspect file. Split accepts various size arguments (bytes, lines...) and will
create as many files as it takes to split the entire large file. These can be
scanned individually and discarded when done. There is a ris
Well I just want to be sure that the big files which can't be scanned don't
contain viruses...
BTW thanks everyone for helping me out
On Mon, Dec 3, 2018, 17:21 Noel Jones What kind of giant files are you scanning? Many big files, such as
> hard drive/DVD images or "raw" database files, are like
What kind of giant files are you scanning? Many big files, such as
hard drive/DVD images or "raw" database files, are likely to
generate random false positives.
-- Noel Jones
On 12/3/2018 3:59 AM, Albert o wrote:
> Alright thank you. Is there a way to make clamscan do the same?
>
> On Mon
Alright thank you. Is there a way to make clamscan do the same?
On Mon, Dec 3, 2018, 09:18 Al Varnell MaxFileSize 0 disables limiting, but that only applies to clamdscan
> scanning.
>
> Sent from my iPad
>
> -Al-
>
> On Dec 2, 2018, at 23:18, Albert o rote:
>
> What do I need to use in clamd.conf
MaxFileSize 0 disables limiting, but that only applies to clamdscan scanning.
Sent from my iPad
-Al-
On Dec 2, 2018, at 23:18, Albert o rote:
>
> What do I need to use in clamd.conf to scan the maximum possible size?
> MaxFileSize 3M
> MaxFileSize 3999M
> Is this syntax correct?
>
>> On Mo
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
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
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 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
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 regarding false positives
(not that any scanner would have). Are you sure you'd want --remove=yes to
remove some critical system files/libraries?
_
Damn it, I thought there was a way to somehow stream those big files
in xMB chuncks.
Thanks anyway.
On Wed, Nov 28, 2018 at 12:47 AM Brent Clark wrote:
>
> What Albert said!
>
> Regards
> Brent
>
> On 2018/11/28 02:27, Al Varnell wrote:
> > If it were possible to scan any size, it would eventually
Hiya
Im sorry to have to tell you, what ever it is you are trying to do and
are thinking, you are doing it wrong.
I can only imagine how long it will take to scan a massive file. The
poor CPU is gonna crap it self.
Please do not do this. The default it is plenty.
HTH
Regards
Brent
On 201
What Albert said!
Regards
Brent
On 2018/11/28 02:27, Al Varnell wrote:
If it were possible to scan any size, it would eventually crash your system and
might even cause permanent damage to it. You don't have unlimited RAM, so you
cannot do unlimited scans.
Sent from my iPad
-Al-
On Nov 27,
If it were possible to scan any size, it would eventually crash your system and
might even cause permanent damage to it. You don't have unlimited RAM, so you
cannot do unlimited scans.
Sent from my iPad
-Al-
On Nov 27, 2018, at 14:01, Albert o wrote:
> Can you guys please tell me the right wa
Can you guys please tell me the right way to disable MaxFileSize?
In my clamd.conf I'm using
MaxScanSize 10M
MaxFileSize 10M
Would placing a # in front of the parameters make it scan any file not
depending on its size?
What about using
MaxScanSize 0
MaxFileSize 0
or even deleting the parame
18 matches
Mail list logo
