On Sat, May 6, 2017 at 9:07 AM, Ian Pilcher <arequipeno@xxxxxxxxx> wrote: > On 05/06/2017 12:51 AM, dieter wrote: > 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. Actually, this appears to be a false conclusion. Supporting detail for CPython 2.x and 3.x: $ strace -f python -c 'import sys' 2>&1 | egrep /proc below cmd output started 2017 Sat May 06 09:37:36 PM PDT above cmd output done 2017 Sat May 06 09:37:36 PM PDT dstromberg@dell-inspiron:~ x86_64-unknown-linux-gnu 14674 $ strace -f python3 -c 'import sys' 2>&1 | egrep /proc below cmd output started 2017 Sat May 06 09:37:53 PM PDT above cmd output done 2017 Sat May 06 09:37:53 PM PDT dstromberg@dell-inspiron:~ x86_64-unknown-linux-gnu 14674 Also, keep in mind that "python" is just the reference implementation of the language. There are several implementations of python the language now. Don't be too hard on glibc. It seems to work pretty well, and a good sort algorithm probably benefits significantly from knowing how much RAM is available when sorting very large lists. Also, don't be overly hard on SELinux. It's a relatively young technology and may still adapt to such needs better in the future. HTH
