On Wed, 22 Dec 2010, Tomasz Kojm wrote:
> >May I suggest for the future a --checkconfig option to clamd (and
> >clamav-milter) that would parse the config file, report any such
> >errors, and
> clamconf is already doing this.
Thanks for reminding me about that !
=
"Christopher X. Candreva" wrote:
>May I suggest for the future a --checkconfig option to clamd (and
>clamav-milter) that would parse the config file, report any such
>errors, and
>exit ? I'm seeing this more and more (apache and Nagios come to mind)
>and
>is a great way to find errors.
Hi,
On Wed, 22 Dec 2010, Tomasz Kojm wrote:
> > It said these were deprecated so I commented the two lines out and now
> > no more warnings. However, was this a wise thing to do or have I
> > misinterpreted the deprecating message? What would those who are more
> > familiar with clamav advocating?
>
On Wed, 22 Dec 2010 18:07:44 +1100 Judi Dey wrote:
> After upgrading to 0.96.5 I notice on start up of clamd that there are
> two warnings about line 301 ArchiveMaxCompressionRatio = 300 and
> ArchiveBlockMax =no.
>
> It said these were deprecated so I commented the two lines out and now
> no mor
