You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
clamonacc will first "register" /a and all it's subdirectory (b, b/c, x).
From what I understand clamonacc will have buckets:
/a
/a/b
/a/b/c
/a/x
Since #1314 it will call onas_ht_rm_hierarchy on all "bucket" matching /a/b:
/a/b → ok, (it will also delete /a/b/c)
/a/b/c → fail (this path is already deleted)
It is possible to bypass the problem by using OnAccessExcludePath ^/a/b$.
Off-topic note: OnAccessExcludePath regexp or not isn't "dynamic", what I mean is that if the exclude path isn't present at the clamonacc start, but is created afterward → the exclusion isn't taken into account (I don't know if it's explained somewhere in the documentation)
The text was updated successfully, but these errors were encountered:
Describe the bug
Imagine the following hierarchy:
clamonacc will first "register"
/a
and all it's subdirectory (b
,b/c
,x
).From what I understand clamonacc will have buckets:
Since #1314 it will call
onas_ht_rm_hierarchy
on all "bucket" matching/a/b
:It is possible to bypass the problem by using
OnAccessExcludePath ^/a/b$
.Off-topic note:
OnAccessExcludePath
regexp or not isn't "dynamic", what I mean is that if the exclude path isn't present at the clamonacc start, but is created afterward → the exclusion isn't taken into account (I don't know if it's explained somewhere in the documentation)The text was updated successfully, but these errors were encountered: