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 12 Jul 2010, at 13:42, Lucas Zinato Carraro wrote:
> Exist a way to filter this log direct in cyrus imap ?
No. Open a bug here:
https://bugzilla.andrew.cmu.edu/
and request a way. There ought to be one.
:wes
Cyrus Home Page: http://cyrusimap.web.cmu.edu/
Cyrus Wiki/FAQ: http:/
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
Exactly,
I use a network balance, and this message is because
of TCP connections with IMAPs in my servers.
Exist a way to filter this log direct in cyrus imap ?
Thanks
---
On Mon, Jul 12, 2
On 05 Jul 2010, at 10:56, Gavin Gray wrote:
> Two of them have had imapd processes crash and leave core dumps in
> the past couple of days. Looking at the core dumps with dbx we see
I'm not aware of bug fixes in those code paths. Given how little
those two code paths have in common, I'd suspec
So what's NOT working? I don't suppose your network monitor is
connecting to the IMAPS port and then immediately dropping the
connection...
:wes
On 08 Jul 2010, at 19:19, Lucas Zinato Carraro wrote:
> Using Thunderbird i can use IMAPs with no apparent problem.
Cyrus Home Page: http:/
