Re: [clamav-users] Could not watch path /var/lib/docker/overlay2 error

I’m going to continue this via clamav-devel: https://lists.gt.net/clamav/devel/77346 . ___ clamav-users mailing list clamav-users@lists.clamav.net https://lists.clamav.net/mailman/listinfo/clamav-users Help us

Re: [clamav-users] Could not watch path /var/lib/docker/overlay2 error

After more testing this seems better: --- a/clamd/onaccess_hash.c 2019-10-10 19:19:06.0 -0500 +++ b/clamd/onaccess_hash.c2019-10-10 19:14:23.0 -0500 @@ -33,6 +33,7 @@ #include #include #include +#include #include @@ -589,6 +590,22 @@ struct onas_hnode *hnod

Re: [clamav-users] Could not watch path /var/lib/docker/overlay2 error

I have a fix for this issue. It seems to root of the problem is the use of fts which doesn’t traverse across file systems. Here’s a patch against 1.101.4: --- a/clamd/onaccess_hash.c +++ b/clamd/onaccess_hash.c @@ -33,6 +33,7 @@ #include #include #include +#include #include @@ -622

Re: [clamav-users] Error in testing clamav and no fanotify

On 09-10-2019 22:58, Frans de Boer wrote: On 04-10-2019 20:36, Frans de Boer wrote: On 04-10-2019 00:10, Micah Snyder (micasnyd) via clamav-users wrote: Frans, Can you provide some more details about your system?  What version of Linux are you testing on? -Micah On 10/3/19, 5:05 PM, "clam

Re: [clamav-users] Continuous increase of startup time (is daily.cld broken?)

Hi, You are forgetting things like embedded systems in hospitals that can't reasonably be updated. The NHS got stung by this with XP and Microsoft had to produce a post EOL fix. Outside of the computer industry, software and hardware move forward at a snails pace. Many systems still use Wi