Limit on number of sockets

[Edgar Fuß]

Is there any kernel-imposed limit on the number of concurrently open sockets other than available memory and kern.maxfiles?

--
Posted automagically by a mail2news gateway at muc.de e.V.
Please direct questions, flames, donations, etc. to news-***@muc.de

[Matthew Mondor]

On Wed, 23 Jun 2010 11:45:17 +0200

Post by Edgar Fuß
Is there any kernel-imposed limit on the number of concurrently open sockets other than available memory and kern.maxfiles?

It's also possible to increase kern.mbuf.nmbclusters, if I recall
correctly, but you should normally be getting ``mclpool limit reached''
messages in dmesg if that is needed.

See also the RLIMIT_NOFILE for that process (or alternatively the
process-specific sysctl nodes for it, proc.<pid>.rlimit.descriptors.*).

[Matthew Mondor]

On Wed, 23 Jun 2010 08:04:58 -0400

Post by Matthew Mondor
On Wed, 23 Jun 2010 11:45:17 +0200

Post by Edgar Fuß
Is there any kernel-imposed limit on the number of concurrently open sockets other than available memory and kern.maxfiles?

It's also possible to increase kern.mbuf.nmbclusters, if I recall
correctly, but you should normally be getting ``mclpool limit reached''
messages in dmesg if that is needed.
See also the RLIMIT_NOFILE for that process (or alternatively the
process-specific sysctl nodes for it, proc.<pid>.rlimit.descriptors.*).

Oh, and I forgot to mention that it's possible to configure a login
class's default limits for RLIMIT_NOFILE via the "openfiles" capability.