loelkes
commented
8 months ago A slightly related issue is that the background scan does not scan all files. This is because the number of unscanned files detected on each run is hard coded to 1000 on the CLI and 100 in the background job, regardless of the maximum value set. This value only applies to the files to be scanned, not the files to be detected.
Problem: I have an instance with > 10 million files. At an interval of 100 files (background job) every 15 minutes (hard coded), it would take almost 3 years to scan everything just once. If I run the job manually every 5min on 1000 files, it only takes a month. Still too much.
The results for unscanned files are set to a batch size (?) in line 213
which is limited to 100 in the background job and 1000 in the CLI.
Why?
I think it would make sense to add a cli command as well to scan all files.
The scanning could do the same as the backgroundjob (just scan files that are new or have been modified).
Maybe a force flag to force a rescan. If for example virus definitions are updated.