Re: Setting overcommit_memory=2 kills system

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]



On Fri, May 18, 2012 at 6:15 AM, John Stanley <john.stanley@xxxxxxxxx>wrote:

> On Thu, 2012-05-17 at 13:08 -0600, Michael Coffman wrote:
>
> > vm.overcommit_ratio = 50
>                                         ^^
>
> Try changing the commit ratio to a greater value (yes you can go over
> 100).
> Then sysctl -w vm.overcommit_memory=2
>
>
OK.


> Just because one machine fails gracefully does not mean the next will.
>

I don't even know what the above means.


> But really buy some ram for real. OR solve the real problem.
>
>

Well that's just ridiculous.  'Real problem'?.    If I run a command to
change a kernel value, I assume that my system will not be rendered useless
because it now believes all the memory is consumed.   It seems like a
problem to me no matter how much memory the machine has.



>
>
> John
>
> _______________________________________________
> CentOS mailing list
> CentOS@xxxxxxxxxx
> http://lists.centos.org/mailman/listinfo/centos
>



-- 
-MichaelC
_______________________________________________
CentOS mailing list
CentOS@xxxxxxxxxx
http://lists.centos.org/mailman/listinfo/centos


[Index of Archives]     [CentOS]     [CentOS Announce]     [CentOS Development]     [CentOS ARM Devel]     [CentOS Docs]     [CentOS Virtualization]     [Carrier Grade Linux]     [Linux Media]     [Asterisk]     [DCCP]     [Netdev]     [Xorg]     [Linux USB]
  Powered by Linux