--On 18. Mai 2009 08:41:42 -0400 Adam Tauno Williams
wrote:
Depends on what you mean. New connections to imapd block block
indefinitely until the number of processes goes below maxchild. If
that's what you call "stall", it's to be expected.
If connections are forced into a wait-state by a
> > It might well be that I hit the maxchild limit on imap, but that shouldnt
> > stall the complete imap, should it?
> Depends on what you mean. New connections to imapd block block indefinitely
> until the number of processes goes below maxchild. If that's what you call
> "stall", it's to be ex
Hello Sebastian,
What I wanted to describe with "stalled" is, that none of the processes was
doing anything. So the problem was not that 100 instances where working and
connection #101 was waiting; it was that all 100 instances were also
hanging. At the same time, the imaps-processes where wor
On Mon, May 18, 2009 at 02:12:55PM +0200, Sebastian Hagedorn wrote:
>> imapcmd="imapd -U 50" listen="imap" prefork=0
>> maxchild=100
>> imaps cmd="imapd -s -U 50" listen="imaps" prefork=0
>> maxchild=100
>>
>>
[...]
> Depends on what you mean. New connections t
--On 18. Mai 2009 14:00:33 +0200 Gerald Nowitzky wrote:
I had a strange problem with my cyrus here. I am starting imapd with
imapcmd="imapd -U 50" listen="imap" prefork=0
maxchild=100
imaps cmd="imapd -s -U 50" listen="imaps" prefork=0
maxchild=100
Three
