I have upgraded.  All seems well.

<p>Greetings All,</p><p>ClamAV 0.102.0 has been released.  The release notes contain the following statement:</p><p>"The On-Access Scanning feature has been migrated out of <span style="max-width: 100%;">clamd</span> and into a brand new utility named <span style="max-width: 100%;">clamonacc</span>. This utility is similar to <span style="max-width: 100%;">clamdscan</span> and <span style="max-width: 100%;">clamav-milter</span> in that it acts as a client to <span style="max-width: 100%;">clamd</span>. This separation from <span style="max-width: 100%;">clamd</span> means that <span style="max-width: 100%;">clamd</span> no longer needs to run with root privileges while scanning potentially malicious files. Instead, <span style="max-width: 100%;">clamd</span> may drop privileges to run under an account that does not have super-user."</p><p>Anyone know whether this is cause for concern?</p><p>Details of the release are here:  https://blog.clamav.net/2019/10/clamav-01020-has-been-released.html</p>

<p>Hello,</p><p>I contacted some days ago Lukas Gebauer about the compatibility of ClamAV new version and Mercury/ClamWall. Hereafter the answer : </p><p>Not tested yet, however I not see any affecting change in release notes. It can work until ClamD socket interface is the same.   Lukas Gebauer.   </p>

Those using ClamAV in Mercury don't use any 'on-access' scanning features so it should not be an issue.