dovecot - Sep 2009 - Automatic fd limit changing

I just realized that Dovecot should probably be doing something
different with how it handles fd limits. The way it currently works is:

1. It checks some settings and warns at startup if fd limit is lower
than what master process might need.

2. For login processes it calculates how many fds are needed and then
either increases or decreases it.

So it's automatically and silently increasing fd limit for some
processes, but not for others. Should it just automatically increase the
limits to all processes when necessary, or never increase and just warn
that the limit is too low?

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 197 bytes
Desc: This is a digitally signed message part
URL:
<http://dovecot.org/pipermail/dovecot/attachments/20090904/88dd7a44/attachment-0002.bin>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Fri, 4 Sep 2009, Timo Sirainen wrote:
> So it's automatically and silently increasing fd limit for some
> processes, but not for others. Should it just automatically increase the
> limits to all processes when necessary, or never increase and just warn
> that the limit is too low?
Hmm, for the "plug-and-play" and "auto-repair" notion of
Dovecot I'd say
"auto-increase". The admin in me would say: "I must be able to
limit it
and know about the problem".

How about: an new setting ;-) auto-increase = yes | no | yes-and-warn, or 
something; "no"==warn. (I know you hate new settings.)
"yes-and-warn" would be default.

Bye,

- -- 
Steffen Kaiser
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)

iQEVAwUBSrc1p3WSIuGy1ktrAQK3Ngf/WXuYOS/5XumoRQvbSY5oGaX+GBFPeQmV
I/13MLmBHd646FcQa/gPJ66+vk51zw26j3w9pEFX8J9+wqrWC31IkL++REjUx6VT
cyi2RCpDdM2nDEpjzepLEsU/I74g7EQ3x1FUD6FEGFTGVHdtxgWydvJ3R+BU6E2X
LmOVsn8g4HVrdD1X0WDNqVl7PH3AFNsYK4EgO3qZUN9WqSLfZWApB9+hx745MpdM
cxo1FKFZikdZyBTzg0Nv+bENF+PrxppB5RxHcekXZlZC+LkLvZEhlokrujrmXnDC
tuhpL81sAKjLHeZFT+9h6PmwUdONtEhKJq0b8iEilJ5kCPQ15uLU3A==i1oH
-----END PGP SIGNATURE-----