From: Gavin Henry <ghenry@openldap.org>
Date: Thu, 18 Mar 2010 20:12:50 +0000 (+0000)
Subject: (ITS#6493) Broken link in online openldap administrator's guide
X-Git-Tag: MIGRATION_CVS2GIT~666
X-Git-Url: https://git.sur5r.net/?a=commitdiff_plain;h=500133bbd77635e2aa05221042b721ab7d022445;p=openldap

(ITS#6493) Broken link in online openldap administrator's guide
---

diff --git a/doc/guide/admin/schema.sdf b/doc/guide/admin/schema.sdf
index 4586875ef2..33b952724e 100644
--- a/doc/guide/admin/schema.sdf
+++ b/doc/guide/admin/schema.sdf
@@ -105,7 +105,7 @@ You are, of course, free to design a hierarchy suitable to your
 organizational needs under your organization's OID. No matter what hierarchy you choose, you should maintain a registry of assignments you make.  This can be a simple flat file or something more sophisticated such as the {{OpenLDAP OID Registry}} ({{URL:http://www.openldap.org/faq/index.cgi?file=197}}).
 
 For more information about Object Identifiers (and a listing service)
-see {{URL:http://www.alvestrand.no/harald/objectid/}}.
+see {{URL:http://www.alvestrand.no/objectid/}}.
 
 .{{Under no circumstances should you hijack OID namespace!}}