On Thu, 2018-07-19 at 19:41 +0000, Micah Snyder (micasnyd) wrote:
Sorry about a lack of response over here. the LogClean option definitely
logs files as "OK" in the log file (e.g. /tmp/clamd.log) for me. Perhaps you
have multiple copies of clamd.conf, or.... Yeah I dunno.
Thanks for the reply.
I found yesterday that if I removed the syslog setting, so the clamd.conf file
was back to just having 'LogCLean' added to it, then clamd still logged clean
files (which it should do of course). I tested this by scanning via an app and
from the command-line, and it all worked okay. So I'm not sure what happened.
It almost seemed as if clamd didn't re-read the config file initially, but once
I had added (and later removed) the syslog setting, then it did re-read it. Not
really likely, but that was what it seemed like. (And yes, I did restart the
clamd process each time.)
Anyway, I retested the 'LogClean' this morning on two servers and using two
different apps, and it is all working fine. Clean files were logged as OK.
On Jul 19, 2018, at 11:31 AM, John Horne <email@example.com> wrote:
On Thu, 2018-07-19 at 10:38 +0000, John Horne wrote:
I have found that by setting the 'LogSyslog' option to true, then clean
Has anyone got the 'LogClean' configuration option working? I have
enabled it in our config file, but scanning files and directories still
only logs found viruses.
files are logged as 'OK' in both the clamd log file and in syslog.
I've grabbed a copy of the source to see if there is anything obvious as to
why just using LogClean doesn't log clean files to the log file.
John Horne | Senior Operations Analyst | Technology and Information Services
University of Plymouth | Drake Circus | Plymouth | Devon | PL4 8AA | UK
This email and any files with it are confidential and intended solely for the use of the recipient to whom it is addressed. If you are not the intended recipient then copying, distribution or other use of the information contained is strictly prohibited and
you should not rely on it. If you have received this email in error please let the sender know immediately and delete it from your system(s). Internet emails are not necessarily secure. While we take every care, University of Plymouth accepts no responsibility
for viruses and it is your responsibility to scan emails and their attachments. University of Plymouth does not accept responsibility for any changes made after it was sent. Nothing in this email or its attachments constitutes an order for goods or services
unless accompanied by an official order form.
clamav-users mailing list
Help us build a comprehensive ClamAV guide: