6 reputation
2
bio website
location
age
visits member for 3 years
seen Dec 7 '11 at 18:49

Dec
6
awarded  Student
Dec
6
comment Mysterious per-session CPU limiting?
@pfo The /etc/security/*.conf files are empty (sans comments). The only thing that looks remotely related in /etc/pam.d/ is in common-session (included from sshd): "session optional pam_apparmor.so". I'm not really familiar with AppArmor, but 10 minutes of research seems to indicate that it's mostly for restricting what files a program can access. Could AppArmor be doing this?
Dec
6
revised Mysterious per-session CPU limiting?
added 209 characters in body
Dec
6
revised Mysterious per-session CPU limiting?
added 63 characters in body
Dec
6
awarded  Editor
Dec
6
comment Mysterious per-session CPU limiting?
Linked an image in the question to show you what 'top' is showing me; let me know if you need more or better evidence!
Dec
6
revised Mysterious per-session CPU limiting?
added 542 characters in body
Dec
6
comment Mysterious per-session CPU limiting?
I checked some of my running processes via 'taskset -p <pid>' and they all came back with "f", which I assume is a 4-bit hex mask that says all 4 cores are okay for that process. When I watch individual core utilization in 'top' (after pressing 1 to show all cores), I see that the process never bounces around; it always stays on the same core. I'm unsure how my application could peg itself to a core; my simple while(1) loop in C doesn't do this explicitly. This behavior applies to lots of programs I've tried to run, in many languages.
Dec
5
asked Mysterious per-session CPU limiting?