Linux box13. 2.6.32-042stab076.5 #1 SMP Mon Mar 18 20:41:34 MSK 2013 x86_64 x86_64 x86_64 GNU/Linux even setting privvmpages to a specific setting DOES not affect "free -m" in containers. This is probably a kernel issue 23:36:29 up 159 days, 7:12, 4 users, load average: 0.42, 0.44, 0.33 [root@box13 ~]# free -m total&n........

This server was experiencing loads of up to 80 and maxing out the RAM and kmemsize on a CPanel VPS. There were literally dozens if not hundreds of exim processes. I have no idea why exim has such a design that would allow it to consume this much CPU and RAM. Any normal MTA should not be spawning so many processes, it should be processing them in sequence and if it is going to spawn hundreds of processes in response to a large volume of mail, it's better to have a delayed del........

cat /proc/user_beancounters produces the following: kmemsize 1861537 5139870 12752512 12752512 26965041 Notice the failcnt "26965041", that is for kmemsize and at first it confused me. The system had enough guaranteed and enough burst RAM available. kmemsize is a variable indepedent of that, but who cars about the explanation right, let's just make thing........

A VPS Server I had just wasn't working right, code that I migrated there just wasn't working. For example, it kept telling me the connection to the database was unsuccessful, halfway through iterating through results it already had. Then I realized it wasn't my code. Ichecked my /proc/user_beancounters and found this: cat /proc/user_beancounters Version: 2.5 uid resource held maxheld barrier limit failcnt........