Sorry guys,
The problem that I tough was sorted out is instead still there. Also
with the version 0.60. I noticed that there this afternoon after
freshclam updated virusdb at about 16:45 GMT with no problem at least
looking at freshclam logs:
--
Wouter
Lorenzo Conti wrote:
I'm experiencing the same trouble running a similar setup:
OpenBSD3.3,
Postfix, amavisd-new-20030314-p2 (running chrooted), spamassassin,
clamd
I notice that it always seemed to be close to an update, but I update
12 times a day. It bombs out at most once a
> > > I'm experiencing the same trouble running a similar setup:
OpenBSD3.3,
> > > Postfix, amavisd-new-20030314-p2 (running chrooted), spamassassin,
clamd
> I notice that it always seemed to be close to an update, but I update
12 times a day. It bombs out at most once a day.
>
I meant that this
Tomasz Kojm <[EMAIL PROTECTED]> wrote ..
> > I'm experiencing the same trouble running a similar setup: OpenBSD3.3,
> > Postfix, amavisd-new-20030314-p2 (running chrooted), spamassassin, clamd
> >
> > What I noticed is that the problem occurs after a db update via
> > freshclam.
I notice that it
> I'm experiencing the same trouble running a similar setup: OpenBSD3.3,
> Postfix, amavisd-new-20030314-p2 (running chrooted), spamassassin, clamd
>
> What I noticed is that the problem occurs after a db update via
> freshclam.
> Basically after a successful update clamd checks itself and the db
I'm experiencing the same trouble running a similar setup: OpenBSD3.3,
Postfix, amavisd-new-20030314-p2 (running chrooted), spamassassin, clamd
What I noticed is that the problem occurs after a db update via
freshclam.
Basically after a successful update clamd checks itself and the db for
updates
