[HN Gopher] Background of Linux's "file-max" and "nr_open" limit...
___________________________________________________________________
Background of Linux's "file-max" and "nr_open" limits on file
descriptors (2021)
Author : cloudripper
Score : 25 points
Date : 2024-07-03 14:54 UTC (2 days ago)
(HTM) web link (utcc.utoronto.ca)
(TXT) w3m dump (utcc.utoronto.ca)
| pixl97 wrote:
| >Specifically on Linux there are two system-wide sysctls:
| fs.nr_open and fs.file-max. (Don't ask me why one uses a dash and
| the other an underscore, or why there are two of them...)
|
| Somewhere it should be lore that the person that named these
| syscalls went on to name functions in PHP.
| quectophoton wrote:
| The creat(3) tradition lives on.
| AdamJacobMuller wrote:
| That extra "e" would represent a 20% bloat in the functions
| name, bytes aren't free you know.
| hermitdev wrote:
| And yet people will die on a hill defending using X number
| of spaces instead of a single tab for indentation (where X
| is some positive integer, usually 2, 3, 4, or 8), with zero
| regard for the bytes wasted.
| TeMPOraL wrote:
| This is what happens when you reject S-expressions as the
| only true form of syntax. People will keep arguing all
| kinds of nonsense, for the same reason that in logic,
| falsehood can be followed by anything you want.
| cassepipe wrote:
| What doe NR stand for ?
| rotifer wrote:
| Probably NumbeR.
| foresto wrote:
| I've seen it used for (the local equivalent of) "number" in
| various countries.
___________________________________________________________________
(page generated 2024-07-05 23:01 UTC)