On 12 Jul 2010, at 15:49, John Madden wrote:
> ...Meaning the error is nothing to worry about? This is on RHEL
> 5.5 if that helps.
The "error" is a debug statement. The CPU usage reflects poorly on
the pthreads implementation.
> Can any of this be tweaked to, for example, wait longer befor
On 07/12/2010 02:01 PM, Wesley Craig wrote:
> On 02 Jul 2010, at 09:29, John Madden wrote:
>> I'm concerned about the listener_lock timeouts.
>
> The listener_lock timeout means that the thread waited around for 60
> seconds to see if a connection was going to arrive. Since it didn't,
> it timed o
On 02 Jul 2010, at 09:29, John Madden wrote:
> I'm concerned about the listener_lock timeouts.
The listener_lock timeout means that the thread waited around for 60
seconds to see if a connection was going to arrive. Since it didn't,
it timed out and that thread went away. The pthread routine
>> Jul 1 15:16:51 imap mupdate[18204]: Thread timed out waiting for
>> listener_lock
>> Jul 1 15:16:51 imap mupdate[18204]: Worker thread finished, for a
>> total
>> of 2 (2 spare)
>> Jul 1 15:16:52 imap mupdate[18206]: New worker thread started, for a
>> total of 3
>> Jul 1 15:16:52 imap mupda
On 01 Jul 2010, at 15:25, John Madden wrote:
> Lately, I've been seeing a lot of this from imap frontends, repeating
> over and over:
These:
> Jul 1 15:16:51 imap mupdate[18204]: Thread timed out waiting for
> listener_lock
> Jul 1 15:16:51 imap mupdate[18204]: Worker thread finished, for a
>
