[$] In search of an appropriate RLIMIT_MEMLOCK default

One does not normally expect a lot of disagreement over a 13-line patch
that effectively tweaks a single line of code. Occasionally, though, such
a patch can expose a disagreement over how the behavior of the kernel
should be managed. This patch
from Drew DeVault, who is evidently taking a break from stirring up
the npm community, is a case in point. It brings to light the question
of how the kernel community should pick default values for configurable
parameters like resource limits.