On 11/12/2024 12:03 AM, Matus UHLAR - fantomas via clamav-users wrote:
On 11/7/2024 3:27 AM, Virgo Pärna via clamav-users wrote:
On Wed, 6 Nov 2024 18:42:33 -0800, Eddie via clamav-users
<clamav-users@lists.clamav.net> wrote:
Nope, there's nothing like that running.
What about database updates happening at that time? For us even
with ConcurrentDatabaseReload true Exim sometimes times out scanning
e-mails, when databse update is happening.
On 11/7/2024 3:33 PM, Eddie via clamav-users wrote:
Nope, not that either. The database update happens about 15 minutes
before this particular mail arrives.
On 11.11.24 11:02, Eddie via clamav-users wrote:
A thought. Even though freshclam finished before this mail was
received and the clamav log shows the database loaded and activated
would the next scan still incur the overhead for the clamd daemon to
reload the signatures. If so, is there any way to force the reload
as part of the freshclam process.
freshclam should notify clamd or new database
The only pattern I've seen is when the next scan occurs 10 -> 15 minutes
after freshclam does an update to the DB. I would hope the reload of
the signatures wouldn't have taken that long.
Don't you use third party signature downloader?
No, just freshclam.
_______________________________________________
Manage your clamav-users mailing list subscription / unsubscribe:
https://lists.clamav.net/mailman/listinfo/clamav-users
Help us build a comprehensive ClamAV guide:
https://github.com/Cisco-Talos/clamav-documentation
https://docs.clamav.net/#mailing-lists-and-chat
