Remove paragraph about Linux OOM killer and fork(). Instead link to

article about OOM.

diff --git a/doc/src/sgml/runtime.sgml b/doc/src/sgml/runtime.sgml
index 86555ba2bacf2cf702f4b9cd248811f2016f127e..eda35adfeab9afa57c47861471e7ff55072af347 100644 (file)
--- a/doc/src/sgml/runtime.sgml
+++ b/doc/src/sgml/runtime.sgml
@@ -1,4 +1,4 @@
-
+
 
 
  Operating System Environment
@@ -1256,14 +1256,11 @@ Out of Memory: Killed process 12345 (postgres).
    
     On Linux 2.6 and later, an additional measure is to modify the
     kernel's behavior so that it will not overcommit memory.
-    Although this setting will not prevent the OOM killer from
-    being invoked 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 but it is actually reserved
-    to other applications with careless memory allocation.) This
-    is done by selecting strict overcommit mode via
-    sysctl:
+    Although this setting will not prevent the 
+    url="http://lwn.net/Articles/104179/">OOM killer from being invoked
+    altogether, it will lower the chances significantly and will therefore
+    lead to more robust system behavior.  This is done by selecting strict
+    overcommit mode via sysctl:
 
 sysctl -w vm.overcommit_memory=2