ulimit -n (open files) increments
0
I had to increase the open file limit for a user on my system, and I was wondering how the open file limit descriptors are being kept track of and if these are stored in bit/byte increments. Imagine I configure the open file limit to 5. In binary, this is 101. This means that not all of the bit values are used (in the range 000 to 111). Does this result in wasted space because some memory locations are unused? Or does the OS not care about this? Is there a different in terms of wasted memory locations between setting the nofiles limit to 100b instead of 111b? I know the question is stated in a confusing way but I don't really know how to word the thing I'm questioning. Maybe someone can propose an edit, if they understand what I am asking. It's somewhat comparable with a 32-bit register not be...
