On Tue, 7 Oct 2008 14:01:53 -0500 "John Smith" <[EMAIL PROTECTED]> wrote:
>
>
>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.
Why don't you install an application to monitor the daemon. Some can be
accessed via the web, while most will email you if something goes
wrong. Most will automatically restart the failed application.
>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 know you are not going to like this; however, if you cannot take the
time to learn the application, then maybe you should not be running it
at all. I most certainly hope you are responsible for yourself and no
other unfortunate users.
>>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.
Again, install a daemon monitor.
>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.
Define: PROBLEM -- If it is incorrectly configured, the problem can
usually be localized to the user sitting in the chair in front of the
monitor.
>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.
Seriously John if you are going to start with a new product, one that
you readily admit you have not got a working knowledge of, you have got
to RTFM. Create a jail and place your new program in it and then fire
it up. Check the logs, see what is happening under the hood. Try
different configurations until you get the desired results. Once you
have stress tested your application, then move it into your production
machine. Anything less, and you are asking for trouble. If you are the
only user, then you can pretty much only screw yourself. However, if
others depend on you, then that is a totally different story.
--
Jerry
[EMAIL PROTECTED]
Hell's broken loose.
Robert Greene
signature.asc
Description: PGP signature
_______________________________________________ Help us build a comprehensive ClamAV guide: visit http://wiki.clamav.net http://www.clamav.net/support/ml
