On Mon, 14 Sep 1998, Jonathan Stone wrote:

: Uh, no, the point here is the sysadmin who _didn't_ set a limit via
: sysctl. Or for someone who starts a daemon from single-user.  
: 
: We need a sane upper bound at all times, and INT_MAX isn't a sane as a
: _default_ upper bound.

Let me rehash so there's no confusion about what I've been saying:

- SOMAXCONN = INT_MAX to request the highest value the kernel allows
  (listen(2) will shrink to fit WITHOUT error)
- the limit in-kernel, before changing by sysctl, defaults to 128
  (or a compile-time option, if specified)
- admin can change the in-kernel limit via sysctl to anything up to INT_MAX

If the admin shoots himself in the foot in the third part above, he shoots
himself in the foot; we shouldn't try to figure out a "sane" value there.

-- 
-- Todd Vierling (Personal tv@pobox.com; Bus. todd_vierling@xn.xerox.com)