Darren,
I had the same behavior some weeks ago.
When the server had 500 imapd processes it hanged and it didn't response until the
cyrus server was restarted...
my problem was related to the number of open files that the system was treating.
I don't know if this is the same problem, but try to increase this...
in my case, I have /proc/sys/fs/file-max setted to 100.
Try to do: echo 100 /proc/sys/fs/file-max and cross your fingers :-)
P.D: I use 100 due to the server we are using has a huge utilization... perhaps
you will need to increase /proc/sys/fs/file-max to a lower number.
In this way I'm able to have, without further problems, 1500-2000 imapd processes and
the server responds perfectly.
I hope this solves your issue.
Regards.
Enric
-Mensaje original-
De: Darren Nickerson [mailto:[EMAIL PROTECTED]]
Enviado el: martes, 05 de marzo de 2002 1:53
Para: Alain Tesio
CC: cyrus
Asunto: Re: imapd unavailable when a lot of connections are
started from
inetd
On Tue, 5 Mar 2002, Alain == Alain Tesio wrote:
Alain Hello,
Alain When I make a lot of connections with cyradm in a
row, the connection
Alain fails after processing some of them, I don't know
where this limit
Alain comes from, the problem is that the imap server is
definitely not
Alain available, see details below.
Alain Is it a known behaviour when imapd is started from
inetd, do you
Alain consider this as a vulnerability to a DOS attack ?
From the inetd man page:
The optional ``max'' suffix (separated from ``wait'' or
``nowait'' by
a dot) specifies the maximum number of server instances
that may be
spawned from inetd within an interval of 60 seconds.
When omitted, ``max''
defaults to 40.
-d
