From 149024002da7e6699ff9a49723c15ef7c173a3cb Mon Sep 17 00:00:00 2001
From: "https://me.yahoo.com/a/g3Ccalpj0NhN566pHbUl6i9QF0QEkrhlfPM-#b1c14"
 <diana@web>
Date: Mon, 16 Feb 2015 20:08:30 +0100
Subject: update for rename of open_issues/gnumach_memory_management.mdwn to
 service_solahart_jakarta_selatan__082122541663/gnumach_memory_management.mdwn

---
 .../resource_management_problems/zalloc_panics.mdwn                     | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/service_solahart_jakarta_selatan__082122541663/resource_management_problems/zalloc_panics.mdwn b/service_solahart_jakarta_selatan__082122541663/resource_management_problems/zalloc_panics.mdwn
index 9c29b07c..3a994ce2 100644
--- a/service_solahart_jakarta_selatan__082122541663/resource_management_problems/zalloc_panics.mdwn
+++ b/service_solahart_jakarta_selatan__082122541663/resource_management_problems/zalloc_panics.mdwn
@@ -65,7 +65,7 @@ While most of these Observations clearly show an exhaustion of kernel memory whi
     <mcsim> mel__: gnumach has no more zalloc allocator, so I doubt if it could
       be a problem.
 
-[[gnumach_memory_management]].
+[[service_solahart_jakarta_selatan__082122541663/gnumach_memory_management]].
 
     <youpi> mcsim: but it still has an allocator
     <youpi> which can run out of resources
-- 
cgit v1.3.1