Describe the bug

ClamAV has RELOAD command that over TCP allows to forcibly start reload of databases, always replied with RELOADING on success. In some clustered ClamAV deployments when freshclam deployed as a cronjob it would be much better to have alternative command which would work a bit smarter: CHECKDB. It can check if reload is needed and replay RELOADING if it triggered reload, or OK if no reload required.

How to reproduce the problem

Now there is no way to say ClamAV to checkdb and known if reload process was started or skipped as not required over TCP.

Attachments

N/A