[clamav-users] clamonacc behaviour - update 2

G.W. Haywood clamav at jubileegroup.co.uk
Tue Oct 15 16:08:35 EDT 2019

Hi there,

On Tue, 15 Oct 2019, Frans de Boer wrote:

> ... separating the on-access code from clamd might look good, but generates 
> all kind of unwanted messages. Short of altering the source code itself, it 
> might be helpful to allow some user control over the generated messages. In 
> fact, I want to see only messages dealing with malware or serious software 
> errors in the log files.

Search for 'legend:' in shared/output.c for a very brief description of the
logging facility in ClamAV.

Can I suggest that you also look at syslog-ng?



More information about the clamav-users mailing list