Jerry Wrote:
>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
>dif
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
On 2008/10/7 Charles Gregory wrote:
> We only 'demand' the right to have our suggestions heard in their proper
> context, and not held up against the idealistic standards of the lucky
> few.
I must say that for the disadvantaged, this has been a great debate.
However, it has missed the basic pre
I can appreciate both sides. However, the general opinion I have heard
seems to echo what I would expect, and that is that the product let me know
if there is an error. Whether that be in a log file, an GUI display, or an
email message are just ways of implementing that solution.
Yes many operat
Update Log error:
WARNING: Current functionality level = 31, recommended = 33
Please check if ClamAV tools are linked against the proper version of
libclamav
According to the FAQ, went to the update page "Download ClamWin Free
Antivirus Update " and received the text "You have the latest version
