On Sat, 2017-05-06 at 11:07 -0500, Ian Pilcher wrote: > On 05/06/2017 12:51 AM, dieter wrote: > > Personally, I doubt that you will find a reference. > > Instead, I assume that the reference comes from the C runtime > > library. > > It might hepl optimize memory management to know about "meminfo" > > details. > > You're right. Seems that it's glibc's qsort(). > > So it seems that any service written in Python (or any other program > that uses qsort) needs to be given read access to most of /proc or > deal > with the (unspecified) consequences of not allowing qsort() to > determine > the amount of memory in the system. > > Delightful. Alternatively, assign a specific type to /proc/meminfo and allow read to it without opening up access to most of /proc. That is what Android has done, for example.
