From dfb426b8a0dd712fbebd7f5de963eb0acb7eb498 Mon Sep 17 00:00:00 2001
From: Samuel Thibault <samuel.thibault@ens-lyon.org>
Date: Wed, 18 Feb 2015 00:58:28 +0100
Subject: Revert "update for rename of
 open_issues/gnumach_memory_management.mdwn to
 service_solahart_jakarta_selatan__082122541663/gnumach_memory_management.mdwn"

This reverts commit 149024002da7e6699ff9a49723c15ef7c173a3cb.
---
 .../resource_management_problems/zalloc_panics.mdwn                     | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

(limited to 'service_solahart_jakarta_selatan__082122541663/resource_management_problems')

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 3a994ce2..9c29b07c 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.
 
-[[service_solahart_jakarta_selatan__082122541663/gnumach_memory_management]].
+[[gnumach_memory_management]].
 
     <youpi> mcsim: but it still has an allocator
     <youpi> which can run out of resources
-- 
cgit v1.2.3