Although this setting will not prevent the OOM killer from
invoking altogether, it will lower the chances significantly and
will therefore lead to more robust system behavior. (It might also
- cause fork() to fail when the machine appears to have available
- memory.) This is done by selecting strict overcommit mode via
+ cause fork() to fail when the machine appears to have available memory
+ because of other applications with careless memory allocation.) This
+ is done by selecting strict overcommit mode via
<command>sysctl</command>:
<programlisting>
sysctl -w vm.overcommit_memory=2