In <list-8580612@2rosenthals.com>, on 11/26/23
at 10:16 PM, "Massimo S." <ecs-isp@2rosenthals.com> said:
Hi Massimo,
>it seems that clamscan have some difficulties scanning dirs with a lot of
>files inside:
>you can see some of these: cli_realloc(): Can't re-allocate memory to
>25952256 bytes. and these:
Unfortunately, I don't have any sure fire solutions to prevent clamscan
from running out of memory. We already know it is very memory intensive
and close to the limits of what OS/2 is capable of.
Increasing VIRTUALADDRESSLIMIT might help. Another option is to shutdown
non-essential applications while clamscan is running.
Another is to do multiple clamscan runs where each run checks a subset of
your directories ir files. The --exclude-dir=REGEX and --file-list=FILE
options may help you configure this kind of setup.
>X:/weasel/MailRoot/mydomain.com/info/O9GTJ5.MSG: Can't read file ERROR (i
>don't understand "can't read file error, since the file is there on the
>f.sys and it can be read)
You are mixing apples and oranges, as we say.
When clamscan runs out of memory, it may fail in any number of different
ways. Inability open files is one possible failure.
When clamscan runs out of memory it may or may not make the system
unstable. If it doesn't, the rest of the system will continue to operate
normally.
back to list