Re: [eCS-ISP] clamscan issue - directories with a lot of files
Datum:
Mon, 04 Nov 2024 13:55:28 -0800
Aan:
"eCS ISP Mailing List" <ecs-isp@2rosenthals.com>
In <list-11205781@2rosenthals.com>, on 11/04/24
at 10:36 PM, "Massimo S." <ecs-isp@2rosenthals.com> said:
Hi Massimo,
>i run this command for each domain
Can I conclude you pasted a partially wrong command line? When you are
running for a domain, you will need to use --recurse.
>and i also run it "divided" on some single recipient directories for the
>small ones eg.
>X:\weasel\MailRoot\mydomain.com\mail1
>X:\weasel\MailRoot\mydomain.com\mail2
>etc..
For the large mailstores, you may have to use --include and --exclude to
subdivide the directory contents into smaller chunks.
Another option you have is to limit clamscan to checking only the recently
modified files. Use your favorite file manager to build a list of the
recenly modified files and run clamscan with the --file-list=FILE switch
option.
Given what we know about clamscan's memory usage and your mailstores, I
probably would use the --file-list option for all runs. With 4OS2 and
some easily accessible utilities, this is easy. To check all files
changed in the last 5 days, it's
dir /[d-5,%_DATE] /a:-d /f /s maildir... >5days.lst
clamscan ... --file-lst=5days.lst
where ... are your current switch options, excluding --recurse of course.
If the resulting list is still too large for clamscan to handle without
errors, we can use split to break the list into smaller lists that
clamscan can handle. For 200 lines per file, it's
split -l200 5days.lst
The resulting split files will be named xaa, aab etc. We can adjust 200
upward until clamscan start to fail due to memory issues. Then it's
for %XX in ( x* ) clamscan ... --file-list=%XX
To use the above technique to check all files, we use
dir /a:-d /f /s maildir... >allfiles.lst
>Y: and Z: are both ramdisk filesystems
>but also i believe this is not important
I agree. This does not appear to be related to your problems.
terug naar list