RE: Excessive threads in opendkim-2.2.2 on Solaris 10

From: Murray S. Kucherawy <msk_at_cloudmark.com>
Date: Fri, 28 Jan 2011 10:16:48 -0800

> -----Original Message-----
> From: Gary Mills [mailto:mills_at_cc.umanitoba.ca]
> Sent: Friday, January 28, 2011 6:15 AM
> To: Murray S. Kucherawy
> Cc: opendkim-dev_at_lists.opendkim.org
> Subject: Re: Excessive threads in opendkim-2.2.2 on Solaris 10
>
> > Again, this is odd. I don't know why you're seeing two different
> > threads in select() inside ar_dispatcher() when opendkim only
> > creates one instance.
> >
> > Versions prior to to 2.1.3 could instantiate libar twice, once in
> > TCP mode and once in UDP mode. But if this is from 2.2.2, that
> > doesn't seem to be possible.
>
> It does seem to be the case. opendkim-2.2.2 has been running on my
> test server since 16 December, always under very light load. It has
> only five threads, but two of them are ar_dispatcher threads:
> [...]

Are you compiling with "--enable-vbr"? In v2.2.2 and prior, libvbr created its own libar instance rather than sharing one with the filter, and that would explain how you get to dispatchers running.
Received on Fri Jan 28 2011 - 18:16:57 PST