[$] In search of an appropriate RLIMIT_MEMLOCK default

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