I know that the new clamav-milter is a work in progress. Is there any
chance of email notifications to an administrator when a virus is
detected being added back into clamav-milter in the future?
Thanks.
--Vincent
Disclaimer: Any references to Pipeline performance contained herein
aCaB wrote:
Turn off LogClean in clamd.conf.
While I could do that, I would prefer the feature to work correctly. Is
anyone else having this issue with 0.95? Is this a known bug that will
be fixed in a future version?
Thanks.
--Vincent
Disclaimer: Any references to Pipeline performance
Török Edwin wrote:
What is the bug here? That the filename scanned is not logged?
I think so. When LogClean = yes I get a lot of this in my log file:
Mar 24 09:26:28 emailfw3 clamd[23436]: fd[10]: OK
Mar 24 09:27:13 emailfw3 last message repeated 4 times
Mar 24 09:28:21 emailfw3 last message
Since upgrading to clamav 0.95 I am getting the log message fd[10]: OK
appearing in my clamav log file. Clamav is configured to log to syslog.
Also, I am logging clean messages.
Here is a section of my log file that shows the message appearing a
couple of times and then syslog buffering it:
After upgrading from clamav 0.70 rc to the stable release of clamav 0.70,
clamav-milter no longer starts.
When I try starting clamav-milter it immediately dies with the message
Segmentation fault (core dumped):
[EMAIL PROTECTED] init.d]# /usr/local/sbin/clamav-milter
Segmentation fault (core
I am trying to compile ClamAV 0.65 on RedHat Linux 7. When compiling the
make stops with the following error:
make[1]: Entering directory `/home/vincent/src/clamav-0.65/clamav-milter'
make[1]: *** No rule to make target `../docs/clamav-milter.8', needed by
`all-am'. Stop.
make[1]: Leaving
