Clamav-90_2 Lockup with freebsd 6.2

Chris chrcoluk at gmail.com
Sun Mar 4 13:28:54 UTC 2007


On 01/03/07, Renato Botelho <garga at freebsd.org> wrote:
> On Thu, Mar 01, 2007 at 02:04:18PM -0500, Daniel Eischen wrote:
> > On Thu, 1 Mar 2007, Alexander Shikoff wrote:
> >
> > >Hi All,
> > >
> > >On Thu, Mar 01, 2007 at 08:32:55AM -0500, Daniel Eischen wrote:
> > >>On Thu, 1 Mar 2007, Martin Blapp wrote:
> > >>
> > >>>
> > >>>Hi,
> > >>>
> > >>>Clamd is currently broken with libpthread for some threading-reason.
> > >>>You definitly need to use libthr (which is still CPU hungry, but
> > >>>works better).
> > >>
> > >>I don't think it is a problem with libpthread.
> > >
> > >FYI: https://wwws.clamav.net/bugzilla/show_bug.cgi?id=307#c8
> >
> > I have no idea what this bug report says.  This link and
> > any other link I can find to clamav bug reports is not
> > working or down.
>
> clamav's configure was wrong, using -lpthread -lc_r in freebsd, now it's
> fixed on development version.
>
> Anyway, I change it to ${PTHREAD_LIBS} on ports, to respect this var. Before
> my last change, REINPLACE_CMD was changing openbsd entry, and it was causing
> the problem.
>
> --
> Renato Botelho <garga @ FreeBSD.org>
>               <freebsd @ galle.com.br>
> GnuPG Key: http://www.FreeBSD.org/~garga/pubkey.asc
>
> Peterson's Admonition:
>        When you think you're going down for the third time --
>        just remember that you may have counted wrong.
>
so now the latest version of the port has same cpu utilisation as 0.88.7?

Chris


More information about the freebsd-stable mailing list