* Chris wrote:
> Knowing that 96.4 was coming out today I expected to see this:
>
> Your ClamAV installation is OUTDATED!
> localhost freshclam[20815]: Local version: 0.96.3 Recommended version:
> 0.96.4
>
> However, in the next hourly syslog snippet and ever since then the
> warning has disappea
On Mon, 2010-10-25 at 23:21 -0700, Al Varnell wrote:
> On 10/25/10 3:30 PM, "Chris" wrote:
>
> > Knowing that 96.4 was coming out today I expected to see this:
> >
> > Your ClamAV installation is OUTDATED!
> > localhost freshclam[20815]: Local version: 0.96.3 Recommended version:
> > 0.96.4
> >
On 10/25/10 3:30 PM, "Chris" wrote:
> Knowing that 96.4 was coming out today I expected to see this:
>
> Your ClamAV installation is OUTDATED!
> localhost freshclam[20815]: Local version: 0.96.3 Recommended version:
> 0.96.4
>
> However, in the next hourly syslog snippet and ever since then the
Knowing that 96.4 was coming out today I expected to see this:
Your ClamAV installation is OUTDATED!
localhost freshclam[20815]: Local version: 0.96.3 Recommended version:
0.96.4
However, in the next hourly syslog snippet and ever since then the
warning has disappeared. Didn't the warning used to
> Hello all,
>
> I have Freshclam cronned and I added the --on-error-execute= which runs
> a little script to send me email.
This option is broken and will be fixed in the tomorrow's version.
Best regards,
Tomasz Kojm
--
oo. [EMAIL PROTECTED]
(\/)\. http://
Hello all,
I have Freshclam cronned and I added the --on-error-execute= which runs
a little script to send me email.
At 2am, freshclam failed to connect to the first server and then got the
defs from the second. I'm guessing this produced an error because I did
*not* get an email (keep reading).
