>Todd Vierling writes:
>> : > (This will become the value of SOMAXCONN such that programs using the
>> : > macro will gain the higher limits without recompiling.)
>>                ^^^^^^^^^^^^^^^^^^^^^^^===================
>> : Leave SOMAXCONN at 128, I say.
>> 
>> Then what use is SOMAXCONN as it is defined in <sys/socket.h>?

>On ordinary machines in ordinary circumstances it will be ordinarily
>useful.

No.  On such machines, for ordinary extant code, it stops a larger
value of, e.g., Matt's somaxconn knob from having any effect at all.
The app asks for a backlog of SOMAXCONN (128), so

	MAX(somxaconn, MIN(sominconn, 128))

is at most 128, regardless of how high you set somaxconn.

Unless you also set sominconn to be higher than the app-supplied
backlog (usually SOMAXCONN, or 128), which renders the app-supplied
backlog value totally pointless. No?