Dennis Peterson Wrote:
> And you've missed the point that some people here have claimed that 
> their clamd process has silently failed and was off line for days, and 
> other such claims. No amount of hand holding for creating config files 
> is going to make that problem better. That requires an interested admin.

Maybe this will shine a different light on the issue.  I personally have
ClamAV running as both a service on my firewall and as a desktop application
(ClamWinAV).  For my desktop, I have watched the update logs and seen issue.

My firewall is IPCOP and it has ClamAV as part of the system.  It updates
and does not display errors through an automated process.  

I admit that I am still learning to control this beast, but having it fail
with no notification is scary (at best) and dangerous (at worst).

I am a very good Windows admin but just learning Linx Admin via IPCOP and
the inclusion of a very good AV that has such a good community of developers
and support is critical.

That being said, it does not help me to find when and if the firewall's
ClamAV (clamd) is failed without opening the firewall daily to determine if
it is still going.

Furthermore, failures because of changes in the config file are beyond my
understanding of this installation and would require several days of
research (which I don't have) just to understand enough to make the change.


>I don't run AV tools because I have a problem - I run them because 
>others have a problem. If everyone knew what they were doing and did a 
>good job there'd be no need for any of this. That is an impossible 
>expectation as evidenced by comments in this thread.

I agree that a good AV is the reason we are here.  Automation or no, we as
both consumers and admins need to have an easy way to see that there is an
issue.

In a previous comment, it was suggested that the Wiki would be a good place
to put update information.   Most non-technical people don't go to wiki
unless they have a problem.   And since the product does not let us know
that there is a problem (until it crashes), we are not likely to go looking.

While I have learned a lot in this thread, the issue is still that the
problem (major to us or minor to you) is a silent failure that leads to
unscanned emails.

Please, let me say that I have no intention of starting a pointing contest
of this product vs. that product.  I only mentioned IPCop because I use it
and it has been very good at updating and keeping within the current version
of Clamd.

John.


_______________________________________________
Help us build a comprehensive ClamAV guide: visit http://wiki.clamav.net
http://www.clamav.net/support/ml

Reply via email to