Tilman Schmidt wrote:
> I encountered this too in April when I still ran a 0.92 release.
> According to a reply I received from Edwin Török at the time, this
> problem should be fixed in version 0.93, and indeed I haven't seen
> it reoccur with 0.93 or 0.93.1.
A quick scan of 0.93.1... yes, I thi
Aecio Neto schrieb:
Due to a network issue, freshclam was not able to connect to update site.
Then, freshclam set virus db as locked and clamd was not possible to read it
and exit.
This happened twice this week.
Is there any option to avoid this or it would be needed some code change to
avoid th
Aecio Neto wrote:
> Agree.
> Freshclam should only lock virus db when it is *really* performing updates
> it grabbed out there.
[...]
> David, is this a change I have to do in my system or is this a proposal for
> a new code?
I suspect it's a rather large change to the way freshclam works. For
On Mon, Jun 16, 2008 at 11:51 AM, David F. Skoll <[EMAIL PROTECTED]>
wrote:
> Aecio Neto wrote:
>
> > Due to a network issue, freshclam was not able to connect to update
> > site. Then, freshclam set virus db as locked and clamd was not
> > possible to read it and exit. This happened twice this
Aecio Neto wrote:
> Due to a network issue, freshclam was not able to connect to update
> site. Then, freshclam set virus db as locked and clamd was not
> possible to read it and exit. This happened twice this week.
We've been hit by this a lot. :-( It's really nasty because clamd removes
the
Due to a network issue, freshclam was not able to connect to update site.
Then, freshclam set virus db as locked and clamd was not possible to read it
and exit.
This happened twice this week.
Is there any option to avoid this or it would be needed some code change to
avoid this situation?
I can pr
